Diagram permissions
A diagram inherits the permissions of whatever stores it. If you can see the page, you can see its diagrams; if you can edit the page, you can edit them.
That is the whole model, and it is deliberate: a second permission system would be one more thing to get wrong. Comments and collections follow the same rule.
#When you would change this
Answering a security question about who can see diagrams.
Working out why somebody cannot open a diagram, comment on it, or add it to a collection.
Planning where to store diagrams that need tighter control.
#What you can set
Setting | What it does |
|---|---|
Page diagrams | Follow the page's permissions and restrictions. |
Space templates | Follow the space's permissions. |
Global templates | Visible to everyone; managed by site admins. |
Referenced diagrams | Follow the permissions of the page holding the source, not the page showing it. |
Diagram comments | Anyone who can view the diagram can read them. Only people who can edit the diagram can add one, and only the author can edit a comment. See Comments on diagrams. |
Collections | Creating, renaming or deleting one needs permission to create content in its space, or the global space. Adding or removing a diagram needs edit access to the diagram's page. See Diagram collections. |
#A few things that catch people out
A reference shows nothing to somebody who cannot see the source page, even on a page they can read.
Restricting a page restricts its diagrams immediately; there is no separate step. The same goes for their comments.
A collection only lists diagrams on pages the viewer can read, so two people can see different contents and counts in the same collection.
To lock down one diagram rather than a whole page, see Restrict a diagram.
#Related
Set it once, in the right place.
