Skip to content
ProvenMap
Reference & Resources
On this page

Integrations Reference

Connectors give ProvenMap authorized access to third-party systems. Manage them under Settings → Connectors.

Connectors

ProviderAuthConnectionWhat it does
OpenRouterOAuth 2.0 PKCEOrganizationRuns Chat and in-portal analyses on your own model account
ConfluenceOAuth 2.0Your own accountRead your pages in Chat; add them to boards as sources
NotionOAuth 2.0Your own accountRead your pages in Chat; add them to boards as sources
JiraOAuth 2.0Your own accountRead issues and epics in Chat; Send to Jira turns work items into issues
SlackOAuth 2.0OrganizationAutomations and Share to Slack post board moments to channels
SentryAPI keyOrganizationA project bound to an app board turns new and regressed issues into insights

Google Docs is listed on Connectors with a Coming soon badge and can't be connected.

Note

Planning to analyze a codebase? Use the code plugin. It analyzes the repo locally and pushes an architecture graph. There is no repository connector.

Whose connection it is

ConnectionMeaningProviders
Your own accountEach member connects their own account. Every read and every issue you create goes through it, so you see and change only what the provider already allows you.Confluence, Notion, Jira
OrganizationOne connection that everyone in the organization shares. An owner or admin sets it up once.OpenRouter, Slack, Sentry

Until a teammate connects their own account, they can't read your pages or send issues through yours.

Who can connect

  • Your own account: any member can connect or disconnect it, from any role.
  • The organization's connection: only owners and admins can connect or disconnect OpenRouter, Slack and Sentry. Other members see An org admin connects this on the card.
  • OAuth apps: only owners and admins can set the organization's OAuth app for a provider. Once the app is set, members connect their own accounts through it.

What each connection enables has its own permission and plan:

FeatureWhoPlan
Read connected documents and issues in ChatAny member, with their own accountEvery plan
Send to JiraOwners, admins and editorsEvery plan
Share to SlackOwners, admins and editorsEvery plan
Slack automationsOrganization owners and adminsPro and above
Sentry insightsAn owner or admin connects Sentry; you then bind the project from the app board's hub like any sourcePro and above

Permissions and Access lists the same actions by role, and Plans and Billing by plan.

Auth methods

Standard OAuth 2.0 sends you to the provider's consent screen. You approve the requested permissions there, then return to Connectors. We store the tokens encrypted.

Used by: Confluence, Notion, Jira (your own account) and Slack (the organization).

Connection status

The card showsMeaning
ConnectedActive and working. The card's menu has Disconnect.
ConnectNot connected: never set up, disconnected, or the provider ended your access
An org admin connects thisAn organization connection, which only an owner or admin sets up
Coming soonNot available yet

For what a lapsed connection means for pages you've already added, see When your connection lapses.

Provider setup

OpenRouter
  1. Click Connect on the OpenRouter card.
  2. Approve the request on OpenRouter's consent screen.
  3. Check that the card shows Connected. Open Chat on any board and ask a question: Chat now runs on your OpenRouter account.
Confluence and Notion
  1. Click Connect on the provider's card.
  2. Approve access on the provider's consent screen. For Notion, pick the pages to share.
  3. Each member connects their own account. See Provider Sources.
Jira
  1. Click Connect on the Jira card.
  2. Approve access on Atlassian's consent screen. Jira and Confluence share one Atlassian identity, but you connect each one separately.
  3. Each member connects their own account. ProvenMap creates issues under it, so Jira's permissions decide which projects you can send to.

If you connected Jira before ProvenMap could send issues, reconnect once to grant the permission to create them. See Send to Jira.

Slack
  1. An owner or admin clicks Connect on the Slack card.
  2. They approve the ProvenMap app on Slack's consent screen for your Slack workspace.
  3. The ProvenMap app posts to public channels without being invited to them first.

Then set up automations in Workspace settings → Automations. See Automations.

Sentry (API key)
  1. In Sentry, create an auth token that can read your organization's projects and issues.
  2. An owner or admin clicks Connect on the Sentry card, pastes the token into API Key, and chooses Connect.
  3. Add a Sentry project to an app board from the board hub: Bindings → Add → Create New → Browse Providers, then Sentry. See Sentry insights.

What's next

Automations

Post board moments to Slack, share by hand, and turn Sentry issues into insights.

Send to Jira

Send work items and epics to your team's Jira, linked both ways.

Provider Sources

Read your documents in Chat and add them to boards.