Account-level roles establish a user's general access and permissions across the entire Clayton platform. These roles determine a user's capabilities beyond the scope of a single project.
Administrator: This is the highest account-level role. Administrators have comprehensive control, managing users, connections, and policies across all projects within the Clayton account. They oversee the platform's overarching configuration.
User: A common role with significant flexibility, Users can access and join any project in Clayton. They can also be assigned specific project-level roles (such as Developer or Project Lead) to define their responsibilities within those projects.
Collaborator: Collaborators have restricted access, limited to viewing only those projects to which they have been explicitly assigned. This role is suitable for individuals needing focused access to specific work.
Exploring Clayton Project Roles: Developer and Project Lead
Project-level roles define a user's specific responsibilities and capabilities within an individual Clayton project. These roles manage access to project functionalities, including code reviews and scan execution.
Developer: This is the most prevalent project-level role. Developers are directly involved in code work and have access to their project and its code reviews. Their capabilities include:
Manually launching code scans.
Downloading any generated code review reports.
Ignoring issues or reporting incorrect detections (false positives).
Accessing their project and participating in code reviews.
Project Lead: This role is designed for users responsible for managing a specific project and its team. Project Leads possess all the capabilities of a Developer, in addition to administrative and configuration authorities within their assigned project:
Configuring code review criteria by selecting from policies installed within the workspace.
Dismissing issues, which is useful for acknowledging deliberate architectural decisions that might otherwise be flagged.
Managing team members and their roles directly within the project.
Removing users from the team.
Both Project Leads and Account Administrators are responsible for ensuring appropriate access and visibility for all contributors within a project. They can manage team members by adding new users, modifying their roles, or revoking access directly through the project settings.