Skip to main content
ℹThis page lives in the Users section and is also referenced from Deployment. If you arrived from there, your sidebar has switched to Users.

Managing Roles and Permissions

This page is for organization administrators. It covers the day-to-day tasks of managing who is in the organization and what they can do, all from the CDT interface.

If you want the conceptual model, see Authorization Overview.

Prerequisites​

You need an account with the Admin role. Without it, Settings → Users is not visible.

Add a user​

Goal: create an account for someone in your organization.

  1. Open Settings → Users from the left sidebar.
  2. Click Add User.
  3. In the Create New User dialog, fill in:
    • Name
    • Email
    • Role — pick from the dropdown
    • Temporary Password — share this with the user; they can change it on first sign-in
  4. Click Create User.

The user appears in the users table with the role you selected.

Bulk-add users from CSV​

Goal: add many users at once.

  1. Open Settings → Users.
  2. Click the more-options menu (…) next to Add User.
  3. To get the expected format, choose Download Users Schema.
  4. Fill in the CSV, then return to the same menu and choose Import Users (CSV).

You can also choose Export Users from the same menu to download the current list.

Change a user's role​

Goal: promote a User to Admin, or demote an Admin to Viewer.

  1. Open Settings → Users.
  2. Click the user in the table to open their details.
  3. Edit their details and change the Role.
  4. Click Save.

The user's next page load reflects the new permissions.

Remove a user​

Goal: revoke a person's access entirely.

  1. Open Settings → Users.
  2. Find the user.
  3. Open their user details and choose the option to delete the account.
  4. Confirm.

Removing a user deletes their CDT account.

What if a permission is missing?​

If a member reports they cannot do something they should be able to:

  1. Confirm their role on the Users page.
  2. Check the Permission reference to verify the role has the relevant permission.
  3. If the issue persists, see Troubleshooting or open an issue.