Audience
Node ACLs apply to content editors (overlay), not dashboard collaborators. Collaborator roles gate the app itself.
How access layers stack
- Role presets — baseline capabilities (edit, publish, sync data, …)
- Capability overrides — per-editor grants or denies
- Node permissions — ACL on individual content nodes
In the dashboard
Open Content, select a node, and manage its permissions. Typical use: restrict a sensitive page or section to a smaller editor set while leaving the rest on the default “everyone” role.
Editors handbook
Field-level day-to-day: Editors · node permissions · roles overview: Role presets & capabilities.
Do
- Keep the default role broad; tighten only sensitive nodes.
- Document why a node ACL exists in the team’s runbook.
Don’t
- Don’t confuse Team Admin with overlay publish rights.
- Don’t lock every node — maintenance becomes painful.