Restrict a diagram
Sometimes one diagram is more sensitive than the page around it. Rather than restricting the page, restrict the diagram: move it to a restricted page and reference it from the open one, or restrict the page that stores the source.
The rule that makes this work is that a reference follows the source's permissions, not the host page's.
#When you would change this
A public page that needs one internal-only diagram.
Templates that only certain teams should use.
Diagrams under review that should not circulate yet.
#What you can set
Setting | What it does |
|---|---|
Restrict the source page | The diagram disappears for anyone without access, wherever it is referenced. |
Store it in a restricted space | Same effect, applied to a whole set of diagrams. |
Restrict the host page | Blunter: hides the whole page, not just the diagram. |
#A few things that catch people out
A reader without access sees a gap, not an error. Say in the page text that something is restricted.
Restrictions apply to the stored preview too, so nothing leaks through exports of a page they cannot see.
Do not rely on obscurity. A diagram on an unrestricted page is visible to everyone who can read it.
#Related
Set it once, in the right place.
