Raito has two types of roles, namely global and local roles. A global role provides you certain permissions within Raito, a local role provides you certain permissions with regards to a specific asset.
Raito considers the following global roles:
- Admin: an admin is responsible to manage Raito for the organization. We have a full separation of concerns, which means that an admin by default does not manage access to data objects.
- Integrator: an integrator is the role used to perform a CLI sync. The integrator role is hence often assigned to a service account.
- Creator: a creator is a super-user with respect to Raito functionality. A creator can manage access for all data objects.
- Observer: an observer has access to all insights in Raito, but has no rights to perform actions in Raito.
- User: a user is the minimum level of access to Raito which provides you all functionality to request access to data and see your personal information.
Next to this global role, we have a local role, owner. An owner can own the following assets:
- Owner of a data source: an owner of the data source is the only one that can remove the data source.
- Owner of an identity store: an owner of the identity store is the only one that can remove the identity store
- Owner of a data object: an owner of a data object is the one responsible to manage the access to the data object. Both via approving in the access request workflow as via edition of access providers to the data object.
Global roles can be assigned through the user management page in the admin pane by clicking the three dots next to someones name. Local roles, like ownership of a data object, can be assigned on the assets page. This local assignment can be performed by an admin or via someone with the same local role.
|Manage Data Sources: add, delete, update metadata||✅||⛔️||⛔️||⛔️||⛔️|
|Manage Identity Stores: add, delete, update metadata||✅||⛔️||⛔️||⛔️||⛔️|
|Manage users: invite to Raito and assign roles (global and local)||✅||⛔️||⛔️||⛔️||⛔️|
|View Data Object tree||✅||✅||✅||✅||✅|
|View Access Provider name, purpose and WHAT-list||✅||✅||✅||✅||✅|
|View Access Provider WHO-list||⛔️||✅||✅||✅||⛔️|
|View existing access: Data Object and User||⛔️||⛔️||✅||✅||⛔️|
|View usage information: Data Object and User||⛔️||⛔️||✅||✅||⛔️|
|View dashboard metrics||⛔️||⛔️||✅||✅||⛔️|
|Approve an access request||⛔️||⛔️||⛔️||⛔️||⛔️|
|Manage Access Providers||⛔️||✅||✅||⛔️||⛔️|
|Permission||Data Source owner (*)||Identity Store owner||Data Object owner|
|Delete the asset you own||✅||✅||⛔️|
|View existing access: Data Object and User||Limited to the Data Source||⛔️||Limited to the Data Object|
|Approve an access request||Limited to the Data Source||⛔️||Limited to the Data Object|
|View Access Provider WHO-list||✅||⛔️||✅|
|Manage Access Providers||✅ (**)||⛔️||✅ (**)|
|Assign ownership||Limited to the Data Source||Limited to the Identity Store||Limited to the Data Object|
(*) Certain permissions arise from the fact that a Data Source owner also owns all Data Objects of the Data Source.
(**) Explained in the following section
Owners of Data Objects can manage Access Providers within the scope of the Data Objects they own. The same applies for a Data Source owner, as he or she also owns all Data Objects in the Data Source.
✅ Sees everything
☑️ Can edit everything, but cannot add Data Objects which he does not own
✅ Sees everything
☑️ Can add/remove data objects he/she owns
⛔ Cannot edit name, WHY and WHO