Roles & Permissions
How workspace roles and project roles work together in Stil
Workspace vs. project scope
Stil permissions live at two levels. Workspace membership controls who belongs to the team space at all. Project membership controls who can access one specific project inside that workspace. This lets you keep a shared team space while limiting access to sensitive projects.
Project roles you will see most often
Owner manages the project at the highest level. Admin can manage members, integrations, and invitations. Member can work in the project without owning its administration. Viewer is read-only and does not consume a paid seat. Viewers are the right default when someone only needs to inspect Stilbook or project state.
Inviting from workspace vs. inviting by email
If someone already belongs to the workspace, add them directly to the project. If they do not, invite them by email from the same Add member flow. The UI shows whether the selected person is in the workspace or outside it so you do not need to switch mental models before acting.
Recommended defaults
Keep the number of admins small, use member for day-to-day collaborators, and default to viewer for stakeholders who only need visibility. When in doubt, grant the lowest role that still lets the person finish their work. It is easier to promote later than to recover from overly broad access.