The role type defines the role a user could have in your organisation.
Properties
| Name | Type | Description |
|---|---|---|
| type | string | Defines the type of the role. The possible values are described below. |
Example
"role": { "type": "admin"}Types
| Type | App Role | API Token Access | Description |
|---|---|---|---|
| admin | Administrator | Administrative | Has full access to the Staffbase Studio of the employee app or intranet. This includes management of users and groups, as well as general settings for the organisation and branding of the app. This is the system-wide administrative role. |
| editor | Managing Editor | Managing Editorial | In addition to what editors can do, can create new news channels and other plugins, edit their access rights or delete them. This is the system-wide managing editor role, usually for adding and managing news. |
| moderator | Editor | Editorial | Can access the Staffbase Studio and edit all plugins system-wide, including news and pages. Additionally, can see the dashboard and manage comments and the app’s menu. This is the system-wide editor role, usually for adding and managing news. |
| reader | User | Read-only | Only has access to the employee app or intranet, but not to the Staffbase Studio. This is the default role when creating new users. When a user is made admin of a space, user group, or editor of a plugin, they get limited access to the Staffbase Studio. In that case, they get additional content-specific roles while still retaining the User role . |
| restricted | Restricted Read-only | Can only see the public area of the app. What is the public area and why do I need one? |