Permissions
Permissions that stay understandable.
Control access at the workspace, project, and page level without making the system harder to trust.
Engineering wiki
Project access
🌐OpenWorkspace
Visible to everyone in Acme Studio. Anyone can read and contribute.
🔒Private5 people
JLSKMRABTZ
iInheritance is explicit. No surprises.
Five rules
Permissions you can explain in one sentence.
01
Open vs private projects
02
Page-level access
03
Public read-only pages
04
Clear permission inheritance
05
Less guessing about who can see what
Open by default — until it shouldn't be.
Make a project visible to the whole workspace, or restrict it to the right people. Inheritance is explicit; nothing changes by accident.
Engineering wiki
Project access
🌐OpenWorkspace
Visible to everyone in Acme Studio. Anyone can read and contribute.
🔒Private5 people
JLSKMRABTZ
iInheritance is explicit. No surprises.
Permissions that stay understandable.
Control access at the workspace, project, and page level without making the system harder to trust.