Practical guide
Who should have access to what?
Start with the audience, then map the information they need.
Define what “public” means
A resource open to all authorised platform users is not necessarily open to the internet. Write down which meaning applies before configuring access or discussing a requirement.
Map situations, not just job titles
List the audiences that need a document: the working group, all platform users, staff or a restricted set of people. Record who may view it and who may maintain it.
An illustrative access worksheet
Use this as a planning worksheet, not as a statement of configured permissions.
- Committee working paper → relevant group participants; maintenance by the designated coordinator.
- General reference note → the authorised users who need it; named content owner.
- Restricted governance record → explicitly approved people; periodic access review.
Test a handover
Walk through a delegate arriving and another leaving. Check group membership, access and the person responsible for keeping those decisions current.
Bring the matrix to the demo
Use your worksheet to ask how each situation is represented in the platform. Confirm the actual permission behaviour rather than relying on labels alone.
Start with your organisation
Bring one real challenge to the conversation.
Tell Julien who takes part, what they share and where the process becomes difficult.
Request a demo