# Working with other capabilities

Most of what makes Diagrams for Jira worth having in the suite comes from what sits next to it. This page is the summary; each connection has its own page with the detail.

Where a connection does not exist, it is listed as such rather than left out, so you can stop looking.

---

## Every connection

| **Connects to**                                | **What you get**                                                                                                                                                                                                                                                                                             |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| External services to connect                   | Nothing for a user or admin to connect after install.                                                                                                                                                                                                                                                        |
| Outbound domains an admin approves at install  | Static.app.<zone>. Fonts, styles, scripts, images, frames and client fetch. Client.api.app.<zone>. Images and client fetch (this is the diagram rendering service). Wss://ws.api.app.<zone>. Client websocket. Server.api.app.<zone>. Browser.sentry-cdn.com and o4504357537906688.ingest.sentry.io. All are |
| Jira permissions requested                     | Permission enforcement is app-managed (rolling releases), so a version that adds a permission installs immediately and waits for approval in Admin Hub rather than blocking existing installs. Note that three of the seven scopes (manage:jira-webhook, manage:jira-configuration, manage:jira-project) plu |
| Content security policy relaxations            | \-                                                                                                                                                                                                                                                                                                           |
| How you are authenticated to Capable's service | This matters for anonymous dashboards: without a token, server-rendered diagram types draw nothing.                                                                                                                                                                                                          |
| Where diagrams are stored                      | Saving does POST /rest/api/3/issue/{key}/attachments with a file named <Title><extension>, using your own Jira permissions. The extension comes from the diagram language (mermaid → .mermaid, drawio → .drawio, excalidraw → .excalidraw, and so on). Diagrams therefore appear in the issue's Attachments. |
| What leaves your Jira site                     | Rendering encodes or posts the source to client.api.app.<zone>/v1/diagram with your token attached. Nothing in the Jira edition lets an admin turn this off, because there is no settings screen.                                                                                                            |
| Licensing                                      | The banner reads "License Not Found" when no licence record exists, or "Trial expired" / "License expired" when it has lapsed. A fresh install can take a few minutes for the licence to become active. Separately, the background job that keeps the diagram JQL index up to date stops firing entirely on. |
| Site registration                              | \-                                                                                                                                                                                                                                                                                                           |

---

## The pages

[External services to connectOne connection.](https://help.gocapable.com/jira-diagrams/external-services-to-connect.html)

[Outbound domains an admin approves at installOne connection.](https://help.gocapable.com/jira-diagrams/outbound-domains-an-admin-approves-at-install.html)

[Jira permissions requestedOne connection.](https://help.gocapable.com/jira-diagrams/jira-permissions-requested.html)

[Content security policy relaxationsOne connection.](https://help.gocapable.com/jira-diagrams/content-security-policy-relaxations.html)

[How you are authenticated to Capable's serviceOne connection.](https://help.gocapable.com/jira-diagrams/how-you-are-authenticated-to-capable-s-service.html)

[Where diagrams are storedOne connection.](https://help.gocapable.com/jira-diagrams/where-diagrams-are-stored.html)

[What leaves your Jira siteOne connection.](https://help.gocapable.com/jira-diagrams/what-leaves-your-jira-site.html)

[LicensingOne connection.](https://help.gocapable.com/jira-diagrams/licensing.html)

[Site registrationOne connection.](https://help.gocapable.com/jira-diagrams/site-registration.html)

---

## A few things worth knowing

* A connection needs both halves installed. In a standalone app most of these do not exist.
* Anything that depends on search only reflects pages that have been indexed.
* Published sites render Capable macros properly, which is where several of these pay off.

---

## Related

[IntegrationsThe section.](https://help.gocapable.com/jira-diagrams/integrations.html)

[Capable for ConfluenceThe whole suite.](https://staging.dev.capable-sites.com/wiki/pages/1412890864)

---

_Better with company._