Roles¶
There are four built-in Roles contained in Coach. These are:
- System Administrator
- Application Administrator
- Manager
- Agent
Danger
Each Role has a different purpose with correspondingly different levels of access to Coach Console and Coach QM. These levels of access are called Permissions. Multiple Roles can be assigned to the same User, the differing Permissions for differing Role being combined with one another
System Administrator¶
During the Coach installation process a User with the Role of System Administrator is created. This System Administrator can only enter Coach Console for Tenant 1000, the original host Tenant. Here they have full permissions within Coach Console for every extant Tenant and can add new Tenants as well as view, edit and delete any that have been created.
Apart from the System Administrator created during Coach’s installation Users can only be added manually to the System Administrator Role. The Role can be assigned to any User but it can only be assigned by, and is only visible to, Users who already have the Role. Due to the importance of this Role for the Coach application, a System Administrator cannot un-assign themself from the Role of System Administrator (or any other Role they may have been given) – only a fellow System Administrator can perform this action, thereby ensuring that at least one User always has the System Administrator Role in each installation. For the same reason a System Administrator can only be deactivated by another System Administrator.
Application Administrator¶
When a new Tenant is created an Application Administrator must be created. An Application Administrator can access both Coach Console and Coach QM for the Tenant they were created for. In Coach Console they have full permissions excepting the ability to add new Tenants or delete their own. In Coach QM they have full permissions except that they cannot create Evaluations or Coaching Sessions.
Apart from the Application Administrator created with a new Tenant further Users can only be added manually to the Application Administrator Role. Due to the importance of this Role for a Tenant, an Application Administrator cannot un-assign themselves from the Role of Application Administrator (or any other Role they may have been given) – only a fellow Application Administrator (or a System Administrator) can perform this action, thereby ensuring that at least one User always has the Application Administrator (or System Administrator) Role within each Tenant. For the same reason an Application Administrator can only be deactivated by another Application Administrator (or a System Administrator).