Account and billing

Roles and permissions

One rule to remember: your workspace role is the ceiling; membership decides what private things you can see; project roles add powers only inside that project.

Roles and permissions

Skrum is the all-in-one AI project control plane — team chat, tasks and sprints, native video meetings, and inbound code activity in one workspace, with every AI action waiting for a human yes.

Skrum ships four built-in workspace roles — Owner, Admin, Member, Guest — and permits custom roles on the Pro plan and above. Permissions are resource.verb strings evaluated at every route.

Workspace role. Sets the ceiling. An Admin can never be denied a permission a Member has.
Membership. Private channels, private projects, and DMs need explicit membership. A Member who is not in a private project simply does not see it — a request would be a 404.
Project role. Adds powers inside a project: task.create, project.settings.manage, sprint.close. Never lets a Guest do something the Guest workspace role denies.

FAQ

Guest boundaries? Guests never see billing, admin, or workspace settings. They see only projects they are added to.
Custom roles on Free? No — Pro plan and above.
Can I make a role that bypasses the workspace ceiling? No.