JetBrains CodeCanvas 2024.1 Help

Roles Comparison

The following table provides a comparison of the predefined Roles (permission sets) in CodeCanvas.

Use this information to determine whether you can use a predefined Role to grant specific permissions to members or teams, or need to edit these Roles or create a new Role with a custom set of permissions.

Global permissions

System Admin role can't be edited, create a custom role instead.

Member role is automatically granted to all organization members and can't be taken away.

check.png   – available and enabled by default

check-empty.png   – available but disabled by default

No checkbox  – not available and can't be enabled

System management

Permission\Role

System Admin

Member

Manage global dev environment settings

  • Managing global dev environment settings like IDE feeds, default IDE versions, and instance types

  • Managing dev environment templates in all namespaces

  • ote that it doesn't grant permission to connect to other users' dev environments or read any personal data from their dev environments

check.png

Create namespaces

Creating new namespaces

check.png

check-empty.png

Manage infrastructure

Managing computing platforms and cloud policies

check.png

Manage users and user personal data

  • Managing the personal data of any user in the system

  • Managing groups

check.png

Superadmin

  • Managing all system settings

  • Managing custom roles and administrative permissions

check.png

Application (legacy)

Permission/Role

System Admin

Member

View applications

check.png

Delete applications

check.png

View applications secrets

check.png

Update applications

check.png

Create applications

check.png

Namespace-specific permissions

The tables show the default permission configuration for namespace templates. Namespace templates are pre-defined Roles that come standard with every newly created namespace.

As a System Admin you can edit the role templates; however, these changes made globally will only be applied to namespaces created afterward  – existing namespaces will not be affected.

Namespace Admin can always override the initial global settings, modifying them for his or her namespace.

check.png   – available and enabled by default

check-empty.png   – available but disabled by default

No checkbox  – not available and can't be enabled

Namespace management

Permission\Role

Namespace Admin

View namespace details

Viewing namespace details, such as connected repositories, templates, and other settings

check.png

Manage all repository connections

Managing Git repository connections in the namespace

check.png

Manage all dev environment templates

  • Managing any dev environment template in the namespace

  • Managing any dev environment in the namespace and performing administrative actions (e.g., force stopping or deleting dev environments)

  • Note that it doesn't grant permission to connect to other users' dev environments or read any personal data from their dev environments

check.png

Namespace administrator

  • Managing namespace settings

  • Managing namespace administrators and custom roles

check.png

Last modified: 17 May 2024