User Roles
Learn about the different roles within Tidra, including basic role-based access control (RBAC) for creating and running initiatives.
User Roles in Tidra
In Tidra, users must be assigned to a role, which determines what actions they are permitted to take. Roles include Admin, Initiatives Admin, and User.
At a high level, here's what each role can access in Tidra:
- Admin: Can modify everything within the portal
- Initiatives Admin: Can create and run initiatives
- User: Can create pull requests for repositories they own
The difference between an Admin and Initiatives Admin
Admins have full access throughout the application, while Initiatives Admins have edit access on Tidra initiatives, but not application settings.
Admins have some additional permissions compared to Users and Initiatives Admins. These permissions include:
- User management. Admins can invite, remove, and edit users and log out other users.
- Account-wide settings. Admins can edit account-wide settings. They can also view the plan and current usage for the organization and configure Single Sign-On.
- API tokens. Admins can create tokens with write access for our GraphQL API while other roles can only create tokens with read-only permissions.
The Users page shows all users' roles. It contains a list of all users in your account and their assigned roles. Admins can perform specific actions on the Users page, such as inviting new users, modifying the roles of existing users, and removing other users.
SCIM/SSO Default User Role
By default, users provisioned automatically through SCIM or SSO will receive the Team Member role. This setting can be modified on the Roles & Permissions page:
Updated 17 days ago