Role and permission
In Any, what a user can do results from the combination of two independent mechanisms: their roles, which apply to the whole platform, and their room membership, which applies locally. See Room members.
Roles are granted to a user or to a group.
A main role (Read only, Standard or Advanced) matches the license of the user and sets the baseline of what they can do: view, contribute, or reach advanced features such as workflow and packages.
Extended roles add up to it to open targeted capabilities: create rooms, manage the recycle bin, apply retention, administer users, call the REST APIs.
The two kinds of permissions
On a content, Any distinguishes two levels of permissions:
- Listing permissions let the user find the content through search and see its metadata.
- Advanced permissions grant access to the content itself and to the actions that can be performed on it.
This split is not just a configuration convenience: listing permissions are evaluated on every search, over large volumes, and keeping them simple is what preserves performance. Advanced permissions, evaluated one content at a time, can on the contrary be as fine-grained as needed.
Permissions also depend on the context: the same user can have write access from one application and read-only access from another.
Going further
- Roles: the full reference of main and extended roles
- Permissions: the user side