Consistent User Role Hierarchy for Drupal

The default five role hierarchy provided within I-ntarsia has been arrived at after working for many years with real clients and agencies running highly successful web services. We say this is the ‘default’ role hierarchy because it can be added to if your service requires more granularity at a specific level.

The role hierarchy sits within an implicit organisational hierarchy (image?):

1. I-ntarisa
2. I-ntarsia Client
3. End Customer
4. Site/Service

In an agency or vertical solutions provider situation, this hierarchy is obvious, but in a larger enterprise the difference between the I-ntarsia Client and the End Customer can be a lot less obvious. As a rule of thumb, the Client will be the person or team who look after multiple brands or End Customers.

The user roles are:

1. Platform Manager
2. Client Administrator
3. Customer Manager
4. Site Manager
5. Content Manager

The people fulfilling these roles are typically:

• Platform Manager: I-ntarsia Staff
• Client Administrator: The key contact(s) at an agency or enterprise. These people can manage multiple Customers
• Customer Manager: The key contact at the customer. A customer may have multiple sites.
• Site Manager: The key contact for a site. These people MAY be the same as the Customer Manager, but they may not. They may also work with multiple sites.
• Content Manager: A person responsible for content in part of a site. They may also work with multiple sites.

Content Manager

A Content Manager can:

1. Log into i-ntarsia and see an access list of any Customer sites they are authorised to work with which will also show the role they have assigned for that site.
2. One click SSO to the Drupal installation for their authorised sites. The destination account is set up with privileges to allow content update only.
3. Raise support requests

Site Manager

A Site Manager can:

1. Log into i-ntarsia and see an access list of any Customer sites they are authorised to work with which will also show the role they have assigned for that site.
2. One click SSO to the Drupal installation for their authorised sites. The destination account has access to some Drupal administration functions and module configuration.
3. Raise support requests
4. Respond, Close, Escalate support requests
5. Create Content Manager Users for their site.

Customer Manager

A Customer Manager can:

1. Log into i-ntarsia and see an access list of any Customer sites they are authorised to work with which will also show the role they have assigned for that site.
2. One click SSO to the Drupal installation for their authorised sites. The destination account has access to many Drupal administration functions and module configuration.
3. Raise support requests
4. Respond, Close, Escalate support requests
5. Create Site Manager Users for their Customer.

Client Administrator

A Client Administrator can:

1. Log into i-ntarsia and see an access list of all Client sites organised by Customer.
2. One click SSO to the Drupal installation for their authorised sites. The destination account is set up with ‘administrator’ level privileges in Drupal. There will be a few restrictions (such as adding modules as these will be done via the platform management processes)
3. Raise, Respond, Close, Escalate support requests
4. Create Customers and Customer Manager Users
5. Copy a site to their I-ntarsia Profiling server
6. Access the Drupal settings files on the Profiling server
7. Access the I-ntarsia GitLab server
8. Publish configuration and settings to a production server