Home
/
CRM
-I-502
/
New idea
14
Vote
implement user defined constituencies permissions
At the moment permissions can only be set for system defined constituencies. Could this be extended to indvidual user defined constituencies (similar to attributes)?
Guest
Jun 29 2015
Reviewed: Voting Open
Blackbaud CRM
/
Education Information
Comments (0)
Votes (14)
Attach files
Enter a subject
Drop here to upload
+6
Log in / Sign up
Log in
Identify yourself with your email address
Email address
Subscribe
You won't be notified about changes to this idea.
Related ideas
Use global change to add system-defined constituencies to records
allow users to assign code table entry permissions for address types
Enable User Defined Constituencies to Hyperlink to the relevant tab or section like system defined constituencies do
Constituency - include navigation option to information which qualified the constituent for a system managed constituency
Allow sub-constituency value
allow users to remove or inactivate out of box constituencies
Allow constituencies to be 'active' but only added from the back end (via global change, etc.)
Restrict user rights for specific fields of constituent record
Add constituency when adding an individual and organization
Add Globals.CurrentAppUserGrantedSystemRole(systemRole) as an available field for expressions in Design Mode