# Customer managed egress

If your diagrams need to load something from your own servers, an administrator approves that domain. It is a deliberate act with a real consequence: the reader's browser then connects to that host directly.

That is the honest description. It is a useful capability and it should be a considered decision.

---

## When this matters

* Diagrams embedding images from an internal host.
* A self-hosted renderer, which requires its own domain approved.
* Reviewing which domains an administrator has already added.

---

## The detail

| **Thing**           | **What happens**                                                          |
| ------------------- | ------------------------------------------------------------------------- |
| Who approves        | A Confluence administrator, explicitly.                                   |
| What it allows      | The browser may fetch diagram resources from that domain.                 |
| What that host sees | Requests from your users' browsers, including the usual request metadata. |
| What it does not do | It does not give that host access to Confluence or to your data.          |

---

## A few things that catch people out

* Only add domains you control or trust. This is the setting most worth reviewing periodically.
* Approving a domain does not proxy the request through us; the browser goes direct.
* Removing a domain takes effect immediately, and diagrams relying on it stop loading.

---

## Related

[Anonymous and guest viewersWhat a logged-out reader actually sees.](https://help.gocapable.com/diagrams/anonymous-and-guest-viewers.html)

[Scopes and permissionsWhat the app asks for, and why.](https://help.gocapable.com/diagrams/scopes-and-permissions.html)

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

---

_Ask us the awkward questions. They have answers._