Thoughtful configuration of access requires attention to each person’s role and the capabilities given to that role. WordPress defines five roles (from most powerful, i.e., most capabilities, to least powerful):
WP Issues CRM adds one additional role ‘Constituent Manager’ which has no WordPress capabilities, but may be given WP Issues CRM capabilities.
WP Issues CRM defines four different kinds of capabilities:
- Basic WP Issues CRM (update constituents, issues and activities).
- Bulk downloads/deletes
- Read and reply to email
- Send email to lists
To give WP Issues CRM capabilities to a given role go to ‘Configure’ underneath WP Issues CRM on the WordPress Menu (formerly known as ‘Main Settings’), then select the Security tab. Then select the role which should have each capability and save settings.
Note that if you give a WP Issues CRM capability to a WordPress role, then all more capable WordPress roles also have that capability. So, if, for example, you give Contributors the WP Issues CRM download capability, then Authors, Editors and Administrators will have that capability but not Subscribers.
Sample Legislative Office Configuration
For a legislative office, one possible combination of roles and capabilities appears below.
Roles assigned in WordPress User Profiles:
- Chief of Staff: Administrator role
- Communications Director who handles email: Editor role
- Interns who enter data: Subscriber role
Access settings in the Configure/Security tab:
- Basic WP Issues CRM (give capability to Subscriber)
- Bulk downloads/deletes (give capability only to Administrator)
- Read and reply to email (give capability to Editor)
- Send email to lists (give capability to Editor)