admin
and reader
.
- The
admin
role has full access to all resources and settings across the platform. - The
reader
role is read-only, intended for users who need visibility but no modification rights.
How to use them
Roles in our IAM system act as a bridge between accounts (users or service accounts) and the permissions they have in the application. Each account is assigned exactly one role at a time, which defines what they are allowed to do. For instance, if a user is given a role calledmanager
, they might be able to modify records or manage users but won’t have access to the platform’s configurations or destructive actions.

viewer
role originally allowed read-only access to records, but is later updated to include access to users, every identity with that role immediately gains that new permission. This makes it easy to scale access management, but also requires careful review before modifying role definitions.
To maintain consistency and prevent accidental access issues, the system prevents deletion of any role that is currently in use by at least one user or service account. Before a role can be deleted, it must first be unassigned from all identities. This ensures there are no dangling references or unexpected permission losses.