Roles and Permissions

Roles

Insight:Center roles are used to easily assign access to functionality on a Team. When a person is added to a Team they are given a role. All i:c Teams have the same roles (listed below), however these roles don’t all have the same permissions. In i:c, roles are given permissions and these permissions correspond to modules or features of modules to complete work in i:c. The role permission setups for each Team are based on the needs for that department or client.

Below are the roles and their uses on a Team:

Account Team - Configure and manage Insight:Center
Supervisor - Monitor and manage users and programs, and view exception reporting for client program operations.
User - Schedule appointments and enter call forms based on goals defined by the Account Team.
Client - Analyze historical information about the program and User performance.
Super User - Used for Teams which need another level of management between the supervisor and user. Rarely used.

Permissions

Insight:Center permissions are used to assign functionality to roles on a Team. When functionality is added to a Team, like a Team blog, the permission to access the blog is added to the role(s) that need to use it.

Team Permissions

Team permissions are generally an on/off switch, where a person see’s, for example, a link on the Team menu or they don’t. In some cases, permissions have also been added to control specific functionality on a page or buttons on a page. Permissions are also used to make reports accessible to a Team, on the report list, from the many reports options available.

Permissions are created by the developers of i:c and linked to new functionality when it is added. IT also assigns permissions to roles when a team is created. Permission can be updated after the Team is launched to increase or remove functionality from a role.

Permission Examples:

Module Permissions

Module permissions were created to enable Account Team members to fine tune permissions on a specific portion of a module – for instance the Forum or Blog.

Using the module permission screen, an Account Team person can set which roles, individual people or client group have access to a portion of a module.

For example, document folders can be configured using the permission screen to restrict who can and cannot view a particular folder. This enables the account team to publish sensitive documents in a folder and only enable their client to view it.