User roles
The role assigned to a Qodana Cloud user defines the set of the permissions that will be granted to them. A permission means an ability to perform a specific action.
Currently, Qodana Cloud supports the Viewer, Editor, Admin and Owner roles, where each subsequent role in this list starting from the Editor inherits existing permissions from the previous role and extends with new permissions.
The Viewer, Editor, and Admin roles can be assigned on the organization and team levels. The Owner role is available only on the organization level.
Team roles
Team roles are the sets of permissions that can be assigned to users on a team level. To learn more about how to invite members to a team, see the Configure teams.
These roles are required for all organization members.
Below you can find the detailed description of all team-level roles and their permissions.
View teams, projects, reports and users associated with a team. This role is suitable for users outside a team who would like to view reports.
Permission | View |
---|---|
Teams | ✔ |
Team users | ✔ |
Projects | ✔ |
Reports | ✔ |
Manage team projects and project reports, members and tokens. This role is suitable for developers, devops and QA specialists.
Here is the explanation to the permission marking:
✓ are inherited from the Viewer role,
✔ are available starting from this role.
Permission | Create | View | Update | Delete |
---|---|---|---|---|
Teams | ✓ | |||
Team users | ✓ | |||
Projects | ✔ | ✓ | ✔ | ✔ |
Project members | ✔ | ✔ | ||
Project contributors | ✔ | |||
Project tokens | ✔ | ✔ | ✔ | |
Public keys | ✔ | ✔ | ||
Reports | ✓ | ✔ | ✔ |
Manage teams and team members. This role is suitable for team managers, team leads, and senior developers.
Here is the explanation to the permission marking:
✓ are inherited from the Editor role,
✔ are available starting from this role.
Permission | Create | View | Update | Delete |
---|---|---|---|---|
Teams | ✔ | ✓ | ✔ | ✔ |
Team users | ✓ | ✔ | ||
Membership requests | ✔ | ✔ | ✔ | |
Projects | ✓ | ✓ | ✓ | ✓ |
Project members | ✓ | ✓ | ||
Project contributors | ✓ | |||
Project tokens | ✓ | ✓ | ✓ | |
Public keys | ✓ | ✓ | ||
Reports | ✓ | ✓ | ✓ |
Organization roles
Organization roles are the sets of permissions that can be assigned to users on an organization level. To learn more about how to invite members to a Qodana Cloud organization, see the Manage organization membership section.
These roles are required for all organization members.
Below you can find the detailed description of all organization-level roles and their permissions.
View organizations, members, teams, and all everything contained in teams like projects, reports and members. This role is suitable for developers, QA specialists, support team members, and product leads.
Permission | View | Leave |
---|---|---|
Organizations | ✔ | ✔ |
Organization members | ✔ | |
Teams | ✔ |
Manage teams and team members within an organization, and view everything related to an organization. This role is suitable for team-leads and managers.
Here is the explanation to the permission marking:
✓ are inherited from the Viewer role,
✔ are available starting from this role.
Permission | Create | View | Update | Delete | Leave |
---|---|---|---|---|---|
Organizations | ✓ | ✓ | |||
Organization members | ✓ | ||||
Contributors | ✔ | ||||
Organization settings | ✔ | ||||
Organization events | ✔ | ||||
Teams | ✔ | ✓ | ✔ | ✔ | |
Team members | ✔ | ✔ |
Manage organizations and their users, projects, project tokens and reports. This role is suitable for members of IT departments.
Here is the explanation to the permission marking:
✓ are inherited from the Editor role,
✔ are available starting from this role.
Permission | Create | View | Update | Delete | Leave |
---|---|---|---|---|---|
Organizations | ✓ | ✔ | ✓ | ||
Organization members | ✓ | ✔ | |||
Contributors | ✓ | ||||
Membership requests | ✔ | ✔ | ✔ | ||
Organization settings | ✓ | ||||
Organization events | ✓ | ||||
Public keys | ✔ | ✔ | |||
Teams | ✓ | ✓ | ✓ | ✓ | |
Team members | ✓ | ✓ | |||
Projects | ✔ | ✔ | ✔ | ✔ | |
Project members | ✔ | ||||
Project contributors | ✔ | ||||
Project tokens | ✔ | ✔ | ✔ | ||
Reports | ✔ | ✔ | ✔ |
Full control over an organization and its entities including users, teams, projects and project reports. This role is suitable for IT department leads.
Here is the explanation to the permission marking:
✓ are inherited from the Admin role,
✔ are available starting from this role.
Permission | Create | View | Update | Delete | Leave |
---|---|---|---|---|---|
Organizations | ✔ | ✓ | ✓ | ✔ | ✓ |
Organization members | ✓ | ✓ | |||
Contributors | ✓ | ||||
Membership requests | ✓ | ✓ | ✓ | ||
Organization settings | ✓ | ||||
Organization events | ✓ | ||||
Organization status | ✔ | ||||
Organization owners | ✔ | ||||
Organization licenses | ✔ | ||||
Public keys | ✓ | ✓ | |||
Teams | ✓ | ✓ | ✓ | ✓ | |
Team members | ✓ | ✓ | |||
Projects | ✓ | ✓ | ✓ | ✓ | |
Project members | ✓ | ||||
Project contributors | ✓ | ||||
Project tokens | ✓ | ✓ | ✓ | ||
Reports | ✓ | ✓ | ✓ |