Team and roles
Layered sharing and access
All
Understand sharing layers and grant access at the right level.
In Lyyli, permissions are layered: organisation, workspace, project, content, and chat—sharing at one level does not unlock everything below unless the UI says so.
Ban assumed inheritance
Support macros must avoid “they’re in workspace so they automatically see chats.” Use evidence from Sharing panels.
Triage playbook
- Workspace membership resolves first via org invites.
- Project filters scope Kanban/board views even if broader membership exists.
- Content cards may require discrete sharing dialogs.
- Chat threads persist sharing lists—re-share after fork if policy demands.
- Organisation admins managing billing/memberships still rely on Professional-only flows described in parallel admin article.
Document your matrix internally
Publish a spreadsheet mapping roles × surfaces so CS answers stay consistent beyond help center copy.