Difference between revisions of "IT/DrupalRoles"
Truekahuna (talk | contribs) m (moved IT/CiviCRM to IT/DrupalRoles: Expanded need for role definitions.) |
Truekahuna (talk | contribs) |
||
| Line 1: | Line 1: | ||
| + | Return to [[IT/]] | ||
| + | |||
==Drupal User Access Levels (incl CiviCRM)== | ==Drupal User Access Levels (incl CiviCRM)== | ||
Revision as of 11:23, 13 June 2011
Return to IT/
Contents
Drupal User Access Levels (incl CiviCRM)
This listing gives the requirements of Drupal roles (including special CiviCRM roles) for cagreens.org.
Drupal Admin
These people will be able to do install updates, manage security, improve back end configuration, etc. for both Drupal and the CiviCRM add-on module(s).
Users: GPCA-IT (Jim, Bert, Cameron)
CiviCRM Admin
This role allows for administration of the CiviCRM module (an add-on to the Drupal instance).
YES: Read financial info
YES: Do financial info data entry
YES: Read personal info
YES: Do personal info data entry
YES: Distribute email communications
YES: Export data
Users: Managing Director (Marnie), Treasurer (Jeanne), Drupal Admin
CiviCRM User
YES: Read financial info
YES: Do financial info data entry
YES: Read personal info
YES: Do personal info data entry
NO: Distribute email communications
NO: Export data
Users: Asst Treasurer, Press Secretary
CiviCRM County Admin
YES: Read financial info
NO: Do financial info data entry
YES: Read personal info
YES: Do personal info data entry
YES: Distribute email communications
YES: Export data
Users: People designated by their county councils to be the admin. Not all County Council members.
CiviCRM County User
NO: Read financial info
NO: Do financial info data entry
YES: Read personal info
YES: Do personal info data entry
NO: Distribute email communications
NO: Export data
Users: All trained County Council members
