What is a Workspace Member?
Think of your workspace as your account; therefore, workspace members are people who have paid seats on your account.
Important: Being a member does not automatically grant access to all projects in the workspace, they need to be invited independently. Visibility depends on workspace role (see below).
Workspace Roles: Manager vs. Editor
🔜 Available on Aug 3, 2026.
Every paid seat comes with a workspace role, with different granular permissions on who can access what across your workspace.
Summary: Owner vs. Manager vs. Editor
Permission | Owner | Manager | Editor |
Create & manage projects | ✅ | ✅ | ❌ |
See all workspace projects | ✅ | ✅ | ❌ — only assigned projects |
Invite members | ✅ | ✅ | ❌ |
Assign, downgrade, or reassign already-purchased seats | ✅ | ✅ | ❌ |
Purchase new seats / change subscription | ✅ | ❌ | ❌ |
Manage label & contact groups (Studio) | ✅ | ✅ | ❌ |
Be assigned any project-level role | ✅ | ✅ | Editor/Reviewer only |
Manage billing and subscription | ✅ | ❌ | ❌ |
Update workspace settings | ✅ | ❌ | ❌ |
Transfer or delete workspace | ✅ | ❌ | ❌ |
Workspace Manager — full workspace access:
Create and manage all projects
See every project in the workspace (regardless they were invited)
Seat management permissions: can assign available seats (from the pool the Owner has already purchased)
Manage label groups and contact groups (in Studio
Can be assigned any project-level role (Owner, Manager, Editor, Reviewer)
Invite members (full sharing capabilities in projects)
Workspace Editor — scoped access:
Only sees projects they've been explicitly invited to
Can't create projects, see the rest of the workspace, or manage members
Can be assigned Editor project-level role.
Useful for external vendors who should have limited visibility.
See What Permissions Are Associated with Each Project Role? for that layer.
Owner-only, regardless of workspace role: billing, workspace settings, transferring or deleting the workspace.
Changing someone's role: if you downgrade a Manager to Editor and they're a Project Manager or owner on other projects, you'll see a confirmation first, their project roles downgrade to Reviewer and any projects they own transfer to the workspace Owner.
Workspace Managers: Seat Management
Workspace Managers have seat management permissions. They can:
Invite members
Assign available seats to a member
Downgrade a member's seat
Delete a seat
Reassign a seat that's already been purchased by the Owner to someone else
Managers cannot buy new seats or change the subscription, that stays Owner-only (see Purchase new seats / change subscription in the table above).
Why: this gives your team day-to-day flexibility. Seat assignment is something that comes up constantly, someone new joins, someone leaves, a seat needs to move from one person to another, and none of it should have to wait on the Owner. Managers can handle it directly, the Owner only needs to step in to purchase more seats.
Note: if you do not have any empty seats to assign to someone, you can click on the request seat to notify the workspace Owner directly.
Why add members?
As a Workspace Owner, adding members gives you:
Less back-and-forth — members work independently without needing you to create and invite them to every project
Better visibility — all projects live under one workspace, so you can see and manage everything in one place
Access control — you decide who's a member, and what workspace role they hold
Shared storage — all workspace projects count toward a single quota
Security — centralized team management, useful for external vendors who should have limited visibility (assign them Editor, not Manager)
Seat Management
How to add a member
Click your avatar (top right) → Settings
Select the workspace you want to manage
Go to the Members tab
Click Invite Members and enter their email
Choose their workspace role: Manager or Editor. Each option shows a short description of what they can and cannot do.
They'll receive an email invitation, if they don't have a VeryBusy account yet, they'll be prompted to create one.
