Skip to main content
Connect your Atlassian account to let the Canvas Agent use Jira and Confluence during an investigation.
Connectors work per user and per Honeycomb Team. You connect your own account, and the Canvas Agent uses the connected service as your account. Connecting a connector does not connect it for anyone else on your Honeycomb Team. If you belong to more than one Honeycomb Team, connect your account in each Team. Your tool permissions also apply only to you, in one Honeycomb Team. There are no Team-level connector controls yet.Connectors work through your account, so an automatic investigation has no connector access at all.

​
What the Canvas Agent can do

  • Search Jira issues and Confluence pages.
  • File or update Jira issues and Confluence pages.
Honeycomb reviews each tool in a connector and gives it a default permission. Until you set your own tool permissions, these defaults apply:
  • The Canvas Agent runs reviewed read-only tools without asking.
  • For reviewed write tools and destructive tools, the Canvas Agent asks you to approve each call.
  • The Canvas Agent does not run deprecated tools.
The Canvas Agent runs a tool only when your investigation needs it. To change the defaults, visit Managing tool permissions.

​
Access this connector grants

Atlassian’s authorization covers every product your account can reach, which is broader than Jira and Confluence alone. The Canvas Agent authenticates to Atlassian with your identity. It can reach the Jira projects, Confluence spaces, and other Atlassian content your account can see. It can also create or update items there, based on your tool permissions.

​
Before you connect

The Canvas Agent connects to Jira and Confluence through the Atlassian Rovo MCP server, which has these requirements:
  • An Atlassian organization admin must allow the Honeycomb redirect URL. Honeycomb is not on Atlassian’s list of supported domains, so Atlassian blocks it by default.
  • Your Jira and Confluence sites must be on Atlassian Cloud.
  • If your Atlassian organization uses an IP allowlist, the allowlist also applies to MCP connections.
Some Rovo MCP tools use credits from your Atlassian organization.

​
Allowing the Honeycomb redirect URL in Atlassian

An Atlassian organization admin does this task one time for the Atlassian organization.
  1. In Atlassian Administration, select your organization.
  2. Select Rovo > Rovo MCP server.
  3. In Domain settings, select Add domain.
  4. Enter the Honeycomb redirect URL for your region:
    • US: https://ui.honeycomb.io/callback/atlassian
    • EU: https://ui.eu1.honeycomb.io/callback/atlassian
  5. Save the change.
If the admin does not allow the redirect URL, Atlassian stops the authorization with this message: “Your organization admin must authorize access from this redirect URL”.

​
Connecting Atlassian

  1. Navigate to Canvas > Connectors.
  2. Find Atlassian in the connector list.
  3. Select Connect.
  4. Authorize Honeycomb from the Atlassian authorization page.
Atlassian shows a Connected badge once the connection succeeds.

​
Turning Atlassian on or off

  1. In a Canvas chat, select the plus (+) button.
  2. Choose Connectors.
  3. Use the toggle beside Atlassian.

​
Disconnecting Atlassian

  1. Navigate to Canvas > Connectors.
  2. Find Atlassian and select Manage.
  3. Select Disconnect.
To learn more, visit Canvas Connectors.