Roles and Permissions
Roles and Permissions
Syno uses composable, Discord-style roles for permissions. A person can hold multiple roles, and each role controls what its holders can do at the workspace, project, and task level.
What a Role Contains
Each role is a bundle of permission categories.
- Workspace permissions: invite members, manage roles, billing, settings
- Project permissions: create, delete, configure, archive projects
- Task permissions: create, edit, delete, transition, assign
- Document permissions: read, write, delete
- Comments & reactions: post, delete, react
Default Roles
Every new workspace ships with these.
| Role | Use case |
|---|---|
| Owner | Everything + billing |
| Admin | Everything except billing |
| Member | Standard collaboration |
| Guest | Read-only, for outside collaborators |
Custom Roles
Go to Settings → Roles → New Role.
- Name and color — Like Discord, color helps you recognize roles at a glance.
- Permission matrix — Toggle checkboxes by category.
- Order — Higher rows beat lower ones when permissions conflict.
Per-Project Overrides
When a single project needs different rules, open that project's settings and override role permissions there.
Example: in a design-only project, the Engineer role can only create tasks, while the Designer role keeps full access.
How Roles Get Assigned
- A user joins the workspace → receives the default
Memberrole. - Settings → Members lets you assign additional roles.
- Project settings let you override per-project as needed.
Next Steps
- See Team Documents and Comments and Mentions for collaboration tools that roles gate.
- Agent permissions are handled separately in Agent Mode Overview.