Roles
In Arcweave, roles define what users can see and do, both at the workspace and project level, based on their set of permissions.
Roles section
The Roles section of the workspace allows you to manage user roles and their associated permissions. Each role is presented in its own tab, containing its name, description, and a list of permissions.
Team workspaces allow Owners to define custom roles with granular permissions.
Default roles
The workspace includes three default roles:
- Owner
- Editor
- Commenter
These roles come with predefined permission sets that cannot be modified:
Commenter
- Can view the workspace's Projects list.
- Can open and comment on all workspace projects.
Editor
- Includes all Commenter permissions.
- Can edit all projects in the workspace.
- Can create new projects.
- Can export any project.
- Can delete projects they've created.
Owner
- Includes all Editor permissions.
- Can invite or remove members and assign their roles.
- Can manage Settings, Billing, and all workspace-level configurations.
- Can delete any project.
Multiple users can hold the same role. The initial Owner is the user who created the workspace, but additional Owners can be assigned later.
Adding new roles
Below the default roles, Team workspaces have access to a button for adding custom roles. This feature allows you to tailor roles to match your team's workflow.
To create a custom role (Team workspaces only):
- Go to the Roles section of your workspace.
- Click + New workspace role.
- Name and describe the role, then click Save.
- Toggle the desired permissions on or off.
Deleting custom roles
To delete a custom role (Team workspaces only), do the following:
- Go to the Roles section of your workspace.
- Select the role to delete.
- Scroll down and click Delete.
- Press Delete on the popup to confirm the deletion.
List of permissions
Within each role tab, beneath the name and description, you'll find a list of available permissions.
Default roles have fixed permissions.
Custom roles (Team workspaces only) allow toggling permissions on or off to suit specific responsibilities. Custom roles can be configured using the following permissions:
Permission | Description |
---|---|
Manage workspace | Edit workspace settings and delete workspace. |
View memberships | See the list of members and Guests. |
Manage memberships | Invite and edit member roles (requires view permissions). |
Delete memberships | Remove members (requires view permissions). |
View projects | Access project list and open all projects and Play Modes. |
Comment on projects | Add and reply to comments (requires view permissions). |
Edit projects | Modify project content (requires view permissions). |
Duplicate projects | Duplicate any project (requires view permissions). |
Manage projects | Change project-level settings (requires view permissions). |
Delete projects | Delete any project (requires view permissions). |
Create projects | Start new projects in the workspace. |
Export projects | Export projects to external formats. |
Export projects backup | Export .arcw backup files. |
Import projects | Import projects from .arcw files. |
Manage roles | Create, modify, and delete custom roles. |
View API keys | See workspace API keys. |
Create API keys | Generate new API keys (requires view permission). |
Manage API keys | Rename or delete API keys (requires view permission). |
Manage billing | Modify billing settings and view invoices. |
Project roles
In addition to workspace roles, users can be granted project-specific roles, which control access and permissions within individual projects:
Project Commenter
- Can view the project and its Play Mode.
- Can add comments and replies.
Project Editor
- Includes all Commenter permissions.
- Can edit the project.
- Can access the project's debugger.
- Can export the project.
Project Owner
- Includes all Editor permissions.
- Can manage the project's roles and invite/remove users.
- Can transfer project ownership and modify public view.
- Can duplicate or delete the project.
A user's project role overrides their workspace role within that project. For example, a workspace Commenter may be a Project Editor on a specific project.
Workspace guests
Guests are users invited to collaborate on specific projects without being workspace members. Guests:
- Are assigned either Project Commenter or Project Editor roles.
- Can only access the specific projects they are invited to.
- Cannot view the workspace's Projects list or create/delete projects.
Guests are not a workspace role, but an implicit status based on access. If a Guest loses all project roles, they are removed from the workspace entirely.
Project Editors who are Guests count toward billing (1 seat). Project Commenters do not.
Inviting Guests
To invite someone to a project:
- Open the project.
- Click Share in the top menu.
- Enter their email under Email address.
- Choose a role: Commenter or Editor.
- Click Invite.
Project Visitors
Project visitors are users who view a public project or its Play Mode via a link. They:
- Do not require an Arcweave account.
- Cannot comment or interact with the project.
- Are not members or Guests and have no assignable role.