Account and Project level security on individual users in Financial Edge

Thomas Walker
Thomas Walker Blackbaud Employee
Tenth Anniversary Kudos 2 Name Dropper Participant
in Blackbaud Financial Edge NXT® General Discussions

Good afternoon,

We are working bringing in Record Level Security into the webview and would like to understand how Record Level security is being used.

  1. What are scenarios where you would use record level of security?
  2. If you use record level security, do you use queries to allow or prevent access?
  3. If you use queries for record level security do you use attributes/custom fields to define the grouping.
  4. Would you be willing to participate in a discovery call?

Thanks for our willingness to better understand how are customers are using record level security today

Comments

  • Kevin Brazell
    Kevin Brazell Blackbaud Employee
    Tenth Anniversary Kudos 5 First Reply Name Dropper

    @Thomas Walker
    In my experience with clients, queries were usually the most used method, and usually they had specific criteria like by department, fund number etc. Normally account/project attributes were not used in the query for security purposes. Range and specific accounts is used far less, mostly because of their need to be micromanaged constantly when new accounts/projects are used. Queries allow more freedom as if the query's criteria picks up new accounts, they automatically give the user the rights to see the account ( or restrict it if they are being restricted).

  • Ed Leiter
    Ed Leiter
    Tenth Anniversary Kudos 1 Name Dropper Participant

    @Thomas Walker

    Good Morning Thomas,

    We are using Record Level Security specifically with accounts and projects in conjunction with attributes and queries to allow selected access. I have setup a budget manager and budget user account and project attribute. The values for these attributes are job position titles or names of work groups. This is what drives the groupings in query criteria for access. I am curious why the project record level security is somewhat different than the account record level security. It appears when you change or add a project attribute the project record level security does not get updated unless you follow the steps in KB Article 111508. I have not experienced this awkwardness with the account record level security. The application of this is in expense management where we have decided to allow users to code their credit card transactions with account codes and project codes. I would be open to a discovery call to discuss further.

  • Patricia Nowak
    Patricia Nowak Community All-Star
    Sixth Anniversary Kudos 1 Name Dropper Participant

    @Thomas Walker
    Hi Thomas, We use record level of security to limit which projects users can access based on which college or unit they are assigned to at OSU. We use project security queries to allow access. The queries included filtering criteria based on attributes and custom fields. If you woul d like to discuss further please let me know. Thanks, Patti Nowak - Oregon State University Foundation - site ID # 5898

Categories