Security Groups or Roles?

In Control Panel, Security, admins — at least for some of you — manage a user's access to features in the web view based on the tasks and permissions assigned to their roles. Users can have one role for each feature area, such as Fundraising or Marketing. With role-based security, you can:

  • Invite users to your organization and its Raiser's Edge NXT web view and database view with a single invitation.

  • Enable more personalized feature-based security for each user.

  • Assign default tasks to roles to grant common permissions, and add new roles with more custom granular tasks and permissions.

If you previously used security groups to manage a user's access to web view features such as Lists or Work Center, their rights now appear as the tasks and permissions of their role under Fundraising roles.

  • Most security groups with rights set for web view features now appear as identical roles, with the group's rights now its corresponding role's permissions.

    For example, Bob and Shirley were assigned to security group A with rights to features X and Y in the web view, and Jane has security group B with rights to Z in the web view; Bob and Shirley now have fundraising role A with permissions to X and Y, and Jane has fundraising role B with permissions to Z.

  • For more nuanced users, security groups with rights set for web view features may combine into a single role to capture rights that don't align with the same tasks and permissions of other roles created from security groups.

    Following the example above, Jill was assigned both security groups A and B; her new fundraising role is 'A & B' with permissions to X, Y, and Z in the web view.

Note: Only security groups with rights set for web view features appear as roles. In the database view, you can manage security groups to secure database view features and determine which data a user can access, such as to secure donor information by constituent code or gift information by fund. For more information, see Record Security.

For more information, see Role-based Security Overview.