# 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.

---

## When you would change this

* Answering a security question about who can see diagrams.
* Working out why somebody cannot open a diagram.
* 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. |

---

## 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.
* To lock down one diagram rather than a whole page, see Restrict a diagram

---

## Related

[Restrict a diagramLocking one diagram without locking the page.](https://help.gocapable.com/diagrams/restrict-a-diagram.html)

[Diagram indexingWhy new things take a few minutes.](https://help.gocapable.com/diagrams/diagram-indexing.html)

[ExamplesWorking diagrams you can copy.](https://help.gocapable.com/diagrams/examples.html)

---

_Set it once, in the right place._