Constituent Security Groups

Constituent security groups enable you to “partition” constituents and restrict access to them. For example, your organization may interact with celebrities and therefore have constituent records for them in your system. If you want to limit access to those records for privacy, you could create a constituent security group for them. For most users, when you associate them with a system role, you would set constituent security to limit record access to only records with no security group assigned. For the few users who should have access to the celebrities’ constituent records, you would set constituent security to include all records or to include that particular constituent security group.

A single feature can also apply to more than one type of record level security. For a user to access the record, that user must have rights to all “pieces” of record level security, both site AND constituent security group. For example, a registrant for an event could belong to a constituent group and the event containing the registrant record could be assigned to a site, so that both types of security would apply to the registrant.