Difference between revisions of "IT/DrupalRoles"
m |
|||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ==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: Read financial info | ||
| Line 21: | Line 25: | ||
YES: Export data | YES: Export data | ||
| − | Users: Marnie, | + | Users: Fundraising Contractor (Marnie), Treasurer (Jeanne), Drupal Admin |
| − | + | ===CiviCRM User=== | |
YES: Read financial info | YES: Read financial info | ||
| Line 37: | Line 41: | ||
NO: Export data | NO: Export data | ||
| − | Users: Asst Treasurer, | + | Users: Asst Treasurer, Press Secretary |
| − | + | ===CiviCRM County Admin=== | |
YES: Read financial info | YES: Read financial info | ||
| Line 55: | Line 59: | ||
Users: People designated by their county councils to be the admin. Not all County Council members. | Users: People designated by their county councils to be the admin. Not all County Council members. | ||
| − | + | ===CiviCRM County User=== | |
NO: Read financial info | NO: Read financial info | ||
| Line 70: | Line 74: | ||
Users: All trained County Council members | Users: All trained County Council members | ||
| + | |||
| + | ---- | ||
| + | [http://wiki.cagreens.org/index.php/IT Back to IT Page] | ||
| + | |||
| + | JGW110914: for convenience I have this early a.m. created a CiviCRM category with 1+ sub-categories. This page is a page "attached" to the main (parent) CiviCRM category. Let me know what changes in my first-draft tree-of-categories need doing and what stub (empty) pages in each category or sub-category need creating. I'll set them up. | ||
Latest revision as of 02:46, 14 September 2011
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: Fundraising Contractor (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
JGW110914: for convenience I have this early a.m. created a CiviCRM category with 1+ sub-categories. This page is a page "attached" to the main (parent) CiviCRM category. Let me know what changes in my first-draft tree-of-categories need doing and what stub (empty) pages in each category or sub-category need creating. I'll set them up.
