Threaded Logo
Using Threaded

User Roles and Permissions

This document provides an overview of the roles and permissions available within the system. Each role has a set of permissions that define what actions users assigned to that role can perform.

The roles are organized into two levels: organizational and project.

#Organizational Roles

#Org Owner

An Org Owner has full access to all projects and organizational settings. They can view, edit, and create projects, as well as share them with others. They have the authority to add or remove other Org Owners, manage user permissions at both the project and organizational levels, and handle project versions. Additionally, they can delete projects, add new organization members, and comment on projects.

#Org Editor

Similar to the Org Owner, the Org Editor can view, edit, and create projects. They can share projects and manage user permissions at both the project and organizational levels. They also have access to project versions and can perform actions like creating, editing, and deleting them. They can add new organization members and comment on projects, but they cannot add or remove Org Owners.

#Org Viewer

The Org Viewer role is primarily for those who need to view project details. They can see all projects and their versions within the organization. They also have the ability to add comments on projects.

#Specific Projects Only

Users with the Org Direct Only role have no specific permissions at the organizational level. However, they can be added as project collaborators with either view or edit permissions, enabling them to contribute to specific projects as needed.

#No Access

Users with the No Access role cannot view or interact with any projects or organizational details. This role is used to explicitly restrict a user’s access to projects and organizational information.

#Project Roles

#Project Owner

A Project Owner has extensive control over the projects they own. They can view and edit project details, create new projects, and manage direct collaborator permissions within the project. They also have access to project versions, enabling them to view, edit, create, and delete versions. Additionally, they can delete projects, add new project collaborators, and comment on projects.

#Project Editor

The Project Editor can view and edit project details and create new projects. They can manage user permissions within the project and handle project versions by viewing, editing, and creating them. They also have the authority to delete projects and add comments.

#Project Viewer

This role is designed for users who need to view project details and versions. Project Viewers can see project information and add comments but cannot make any changes to the projects themselves.