Skip to main content
Gable provides enterprises with Role Based Access Control(RBAC) over all your data with Gable. RBAC ensures secure, scalable, and auditable access management by assigning permissions based on organizational roles instead of individuals. Each user is provided with a role that defines what actions they are able to perform within Gable. These limitations apply to UI and API based access.

Roles

There are three roles that can be attributed to any user. Only one role may be assigned to each user. You can assign any role to an user when they are invited but the default will be Viewer. The roles of an existing user can be changed at any time.

Viewer

Users with the Viewer Role are only able to read the various assets within Gable. This role should be the default role applied to all users.

Editor

Users with the Editor Role are able to read and write various assets within Gable. This role should be provided to members within your team who will be actively editing assets and creating contracts.

Admin

Users with the Admin Role are able to read, write and delete all assets within Gable. Admins are also responsible for the majority of the team setup such as SSO configuration and managing users.

Permissions Table

CategoryActionViewerEditorAdmin
AssetsReadYesYesYes
WriteNoYesYes
DeleteNoNoYes
ContractsReadYesYesYes
WriteNoYesYes
DeleteNoNoYes
ChangelogReadYesYesYes
ActionsReadYesYesYes
WriteNoYesYes
DeleteNoNoYes
LineageReadYesYesYes
Team SettingsProfile UpdatesYesYesYes
Inviting New UsersNoNoYes
Deleting Existing UsersNoNoYes
API Keys ValuesNoNoYes
Enabling or modifying SSONoNoYes
Slack ConnectionNoYesYes

Questions

If you have any questions regarding RBAC support within Gable please reach out to security@gable.ai
I