Collaboration
Roles and permissions
The two levels of role — workspace and project — and how a plan can clamp what a role can do.
SpaceSync has roles at two levels, and they answer different questions. Workspace roles decide what you can do to the organisation; project roles decide what you can do to a piece of work.
Workspace roles
- Owner
- Full control of the workspace, including billing and the ability to transfer ownership.
- Admin
- Manages members, seats and workspace settings. The day-to-day administrative role.
- Member
- A normal user. Creates projects and works in the ones they belong to.
- Viewer / Guest
- Read-only access to the workspace. Typically an external reviewer or a client.
Project roles
- Owner
- The project's owner. Can invite, change roles, manage the share link, transfer, archive and delete.
- Collaborator
- Works on the project — draws, edits the programme, comments, saves versions.
- Viewer
- Reads the project. Cannot change it.
Where the answer actually lives
SpaceSync does not decide what you can do by looking up your role name in a table. The server computes your capabilities for each project directly and sends them with the project — the interface then renders exactly those. A button you cannot see is a capability the server did not grant, not an oversight.
That is why this page does not publish a role-by-role grid: it would be a second answer to a question the product deliberately answers in one place. If you need to know whether a specific person can do a specific thing, open the project's member list — it reflects the real computation.
When your plan clamps your role
An effective role can be lower than an assigned role
Your plan can restrict what a role is allowed to do. When that happens your effective role is lower than the one you were given, and the interface says so — offering an upgrade when the limit is the plan, and *"ask the project owner"* when the limit is genuinely your role.
The distinction matters when you are troubleshooting: an owner who cannot edit is almost always looking at a plan limit, not a permissions bug. See Plans.