> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/getting-started/roles.md). # Seats and Roles Roles define what each workspace member can see and do. ### Inviting members Open workspace settings (gear icon) → **Workspace** tab to invite members.
{% hint style="warning" icon="lock-keyhole" %} Only the workspace **Owner** and **Manager** can access these settings. Other members can neither invite nor view the workspace member list. {% endhint %} Enter an email, pick a role, and send the invite:
Role can be changed at any time from the same list:
If the invited person doesn't have a Vectary account yet, they'll get an email invite to sign up. Your workspace will be added to the invited user's workspace list. If the user already has an account, they don't need to do anything — no email confirmation is required, as the invite is accepted automatically. ## Roles: ### Owner As the primary account holder, the Owner is responsible for managing the contract, creating the workspace, and overseeing billing. This role possesses managerial privileges, overseeing all features and functionalities within the workspace. ✅ full control over the workspace *** ### Manager Managers hold a high-ranking role within a workspace, similar to the Owner, with the exception of not having access to billing information and not being able to delete a workspace. They oversee member access and permissions, and manage project editing and sharing. Managers can add, remove, and approve member requests, move projects between workspaces, and make projects public. They have full editing capabilities in the Studio, ensuring secure workspace management. ✅ possesses nearly the same rights as the Owner ❌ does not have access to billing information and cannot delete the workspace *** ### Editor Editors primarily work with 3D data, import CAD files, and create interactions and animations. While they can create folders and move projects within their workspace, they cannot delete projects or move them outside the workspace. Editors can be internal team members or external professionals managed by workspace managers. ✅ ability to edit all projects within the workspace ❌ lacks permission to: * manage workspace members * delete workspaces, folders, projects, or comments * export projects or change project sharing settings *** ### Collaborator Collaborators have restricted access, with the ability to view or comment on projects, but not to edit them, which ensures project integrity. They can see all shared projects within the workspace but must be approved by a manager to join, ensuring a secure method for sharing sensitive data. This role offers more expansive viewing capabilities compared to the Viewer role. ✅ able to view all projects in the workspace and can perform all operations related to comments, except for deletion ❌ inherits the same restrictions as the **Editor**, with the additional inability to edit projects *** ### **Viewer** Viewers have restricted access, limited to only seeing projects for which they have direct links. While they are technically part of the workspace, they cannot see the overall content or project lists. This role is particularly useful for sharing projects privately without allowing these users to comment or see existing comments. ✅ access only to view projects for which they possess a direct link ❌ inherits the same restrictions as a Collaborator, with the additional limitation of not being able to see projects within the workspace *** ### Permissions overview
ActionsOwnerManagerEditorCollaboratorViewer
Access to billing informationtruefalsefalsefalsefalse
Managing workspace memberstruetruefalsefalsefalse
Deleting workspaces, folders, projects, commentstruetruefalsefalsefalse
Exporting projects and changing project sharing settingstruetruefalsefalsefalse
Project editingtruetruetruefalsefalse
Access to view all projects and comments in workspacetruetruetruetruefalse
Read and add commentstruetruetruetruefalse
Viewing projects via direct linkstruetruetruetruetrue

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.vectary.com/documentation/getting-started/roles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.