Connect Synaps to Confluence
Synaps runs inside Jira and reads its dependency data directly. To publish a dependency map to Confluence, a site admin connects the Synaps app to Confluence once, from Atlassian Administration. After that, anyone can publish straight from the Export dialog. Here is the full setup, step by step, and how to publish once it is done.
Synaps is a Jira app. It does not appear in Confluence's app list, and there is nothing to install inside Confluence itself: you always publish from the Export dialog in Synaps, which opens from Apps in Jira's navigation. This one-time connection is only needed for the Confluence export; every other Synaps feature works in Jira with nothing to set up.
01. Before you start
You need three things:
- Synaps installed on your Jira site. Install Synaps covers this; it takes a minute.
- Confluence in your Atlassian Cloud. If your organisation does not have Confluence yet, an Atlassian admin can add it.
- An organisation or site admin with access to admin.atlassian.com. A regular project member cannot connect the app, but everyone can publish once it is connected.
02. Connect the app to Confluence
Installing Synaps on Jira does not give it access to Confluence on its own, even when both products live on the same Atlassian site. A site admin grants that access once, from Atlassian Administration:
- Go to admin.atlassian.com and sign in. If you manage several organisations, pick the one that owns your Jira site.
- Select Apps in the top navigation, then Sites, and choose the site where Synaps is installed.
- In the left navigation, select Connected apps, find Synaps in the list, and select View app details.
- Open the Connections tab. Under App connections, Confluence is listed as Not connected. Select Connect.
- A Connect to Confluence panel opens, listing what Synaps can do and what data it has access to (Actions in Confluence). Review the permissions and select Connect. Confluence now shows as Connected.
One-time setup: once an admin connects Synaps to Confluence, it stays connected. Users never see the connection step again.
Until this is done, the Confluence option in the Export dialog is disabled and Synaps reports that Confluence is not connected.
03. Check it worked
Back in Jira, open Synaps from Apps in Jira's navigation, then open the Export dialog from the navbar and look at the Confluence option:
- Enabled: you are connected. Pick a space, optionally a parent page, and publish.
- Greyed out: not connected yet, or you have no Confluence space you can write to. See the troubleshooting table below.
04. Publish your first map
With the connection in place, publishing takes three clicks from Synaps:
- Click Export in the Synaps navbar and pick Confluence. Synaps fetches the list of Confluence spaces you can write to.
- Pick a space, and optionally a parent page. Leave the parent at Top level to publish at the root of the space.
- Click Export. Synaps creates the page and shows you the link.
The page lands in the space you picked, named Synaps - <view name> - <date and time>, so two exports in the same space never collide. It contains project tables, dependency lists, and links back into Jira:
Export and share covers the other formats (Markdown, CSV, PDF, PNG) and how the exported content follows your current view.
05. Troubleshooting
If the Confluence export is unavailable, Synaps tells you why:
| What Synaps says | What it means | How to fix it |
|---|---|---|
| Confluence isn't connected | The app has not been connected to Confluence | Ask a site admin to connect Synaps to Confluence (step 2) |
| No accessible Confluence space found | The app is connected, but you cannot write to any space | Get write access to at least one Confluence space |
| Cannot reach Confluence | A temporary network problem | Try again in a moment |