Skip to main content
All CollectionsUser roles
Account user roles explained
Account user roles explained

Accounts and roles explained

Gabriele Gallo Stampino avatar
Written by Gabriele Gallo Stampino
Updated over a month ago

In Clayton, account-level roles and project-level roles serve distinct purposes in managing access and responsibilities.

Account-Level Roles
​

These roles are assigned at the account level and define what users can do across the entire Clayton platform. They determine a user's general access, permissions, and visibility across multiple projects. The main account-level roles are:

  1. Administrator - Has full access across all projects, manages users, connections, and policies. This role is ideal for those who oversee the platform as a whole and need visibility into all projects.

  2. User - Can access and join any project in the account and can also be assigned as a Project Lead or Developer in specific projects.

  3. Collaborator - Has limited access, viewing only the specific projects they are assigned to. This role is suited for users who need access to select projects rather than the entire account.

Project-Level Roles

These roles are assigned within individual projects and define specific responsibilities and permissions for users within that project. They focus on a user's tasks and involvement at the project level rather than account-wide access. The main project-level roles are:

  1. Developer - Typically assigned to users who work directly with the code within a project, Developers can access code reviews, run scans, and download reports.

  2. Project Lead - A more managerial role within a project, responsible for configuring code review criteria, managing team members, and overseeing the project. Project Leads have authority over the project’s settings and team but only within that particular project.
    ​
    ​

Administrator

  • can invite and manage users (specifying role and projects)

  • can manage Connections (read more here)

  • can manage OAuth apps

  • can manage code review Policies (read more here)

  • can see and configure all the projects

  • on every project, can be Developer or Tech Lead (read more here)

  • see People add-on insights

User

  • can see and join all the projects

  • can be project lead or developer (read more here)

Collaborator

  • can see only the projects they are associated

  • can be project lead or developer (read more here)

Did this answer your question?