# User roles and permissions Roles are a great way to group permissions and make it easier to manage them, while permissions define the specific actions that a user can perform within the application. The following roles and permission matrix tables list the permissions for each role available within Vectice, along with their granted permissions. ## Organization user roles and permissions Organization user roles define what users can do within their organization in Vectice. The available roles are as follows: * **Admin -** Recommended for users who need full access to organization settings and management. * **Member -** Recommended for users who are part of an organization and need access to resources and functionalities provided by Vectice. * **Viewer** - **Read-only** access to the organization's resources in Vectice with ability to comment, review and export documentation. {% hint style="info" %} **Viewers** automatically assume the role of workspace **Reviewers** by default, which remains unchangeable unless they request to upgrade to the Member role at the organizational level. {% endhint %}

Permissions	Admin	Member	Viewer
Read workspaces content	✅	✅	✅
Export documentation	✅	✅	✅
Review and comment on resources	✅	✅	✅
Create new Workspaces**	✅	✅
Invite colleagues**	✅	✅
Delete Workspaces	✅
Manage organization settings	✅
Manage organization users	✅
Manage organization invites	✅

\*\* Org Admins can update organization settings to also allow members to create workspaces and invite colleagues. ## Workspace roles and permissions Workspace roles define what the user can do and access within a workspace. The available roles are as follows: * **Manager -** Recommended for users who need the ability to make administrative decisions, configure settings, and manage user access within workspaces. * **Editor -** Recommended for users who are actively involved in creating, editing, and modifying content within a workspace * **Reviewer** - **Read-only** access to a workspace resources in Vectice with ability to comment, review and export documentation.

Permissions	Manager	Editor	Reviewer	Reader	Editor
Read workspace content	✅	✅	✅	✅	✅
Export documentation	✅	✅	✅
Review and comment on phase documentation	✅	✅	✅
Access workspace dashboard	✅	✅	✅		✅
Create projects, phases, and assets	✅	✅			✅
Add members to Workspace	✅	✅			✅
Remove members from Workspace	✅
Update Workspace settings	✅
Delete Workspaces	✅

## Project roles and permissions Project roles define what the user can do and access within a project. The available roles are as follows: * **Creator -** the user who created the project. * **Owner -** the user responsible for the project’s overall success. * **Contributors** - users who actively participate in the execution of the project.

Permissions	Owner	Creator	Contributor
Access/read project content	✅	✅	✅
Contribute to project	✅	✅	✅
Review project phases	✅	✅	✅
Request phase reviews	✅	✅
Transfer project ownership	✅	✅
Delete projects	✅	✅

## Other roles Here are a list of other roles you may find in Vectice:

Project level	Roles
Phase	Owner - the user who is responsible for overseeing the phase
Iteration	Owner - the user who created and owns an iteration
Models and Datasets	Creator - user who created the asset Contributor - user who contributes to the asset (i.e., add properties, metrics)

Project level

Roles

Phase

Owner - the user who is responsible for overseeing the phase

Iteration

Owner - the user who created and owns an iteration

Models and Datasets

Creator - user who created the asset

Contributor - user who contributes to the asset (i.e., add properties, metrics)

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.vectice.com/25.1/admin-guides/user-management/user-roles-and-permissions.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.