ProvenMap
Reference & Resources

Integrations Reference

Connectors authorize access to third-party systems. A connection belongs to one user or the organization, depending on the provider. Manage them under Settings → Connectors.

Important

Today, one connector is live: the model provider. Connect OpenRouter and Chat runs on your own account and models, on every plan. Every other provider below is listed in Connectors with Coming soon — it cannot be authorized yet, and nothing can be added from it as a source. Use a Web URL, a Note, or the connect plugin for documents in the meantime.

Connectors

ProviderAuthCategoryStatusWhat it provides
OpenRouterOAuth 2.0 PKCE (org)LLM ProviderAvailable now — powers ChatModel routing, chat completions, streaming
ConfluenceOAuth 2.0 (user)DocumentationComing soonSpaces, pages, content search
JiraOAuth 2.0 (user)Project ManagementComing soonProjects, issues, issue search
NotionOAuth 2.0 (org)DocumentationComing soonDatabases, pages, content search
GitHubOAuth 2.0 (user)Code RepositoryComing soonRepos, files, code search, directory trees
Google DocsOAuth 2.0 (user)DocumentationComing soonDocuments, document search via Google Drive
SlackOAuth 2.0 (org)CommunicationComing soonChannels, message history, message search
TerraformAPI Key (org)InfrastructureComing soonWorkspaces, state files, runs, plan output
SentryAPI Key (org)ObservabilityComing soonProjects, issues, error events
LogRocketAPI Key (org)ObservabilityComing soonSessions, session replay, error tracking
IntercomOAuth 2.0 (org)Customer SupportComing soonConversations, contacts, support articles
Note

Planning to analyze a codebase? Use the code plugin instead. It analyzes the repo locally and pushes an architecture graph. The GitHub connector reads repo content, such as READMEs and docs; it does not map architecture.

Auth methods

Providers use three authentication patterns:

Standard OAuth 2.0 redirects you to the provider to authorize access. You approve the requested scopes on the consent screen, then return to the platform. The platform stores encrypted tokens on your behalf.

  • User-scoped providers (GitHub, Confluence, Jira, Google Docs): each team member connects their own account, so everyone sees only the resources they personally have access to.
  • Org-scoped providers (Slack, Notion, Intercom): a single org-wide token is shared across your organization. One person connects it for everyone.

Token scope

ScopeMeaningProviders
UserEach user connects their own accountGitHub, Confluence, Jira, Google Docs
OrgOne connection shared across the organizationSlack, Notion, Intercom, Sentry, LogRocket, OpenRouter, Terraform
Tip

Org-scoped connectors only need to be set up once. User-scoped connectors, such as GitHub, need each team member to connect individually so each person sees only the resources they can access.

Connection status

Each connector can be in one of these states:

StatusMeaning
ConnectedActive and working
DisconnectedNot yet configured or manually disconnected
ExpiredToken has expired and needs re-authorization
Needs re-authProvider revoked access or scopes changed
ErrorSomething went wrong; check logs

Connect the model provider

  • Navigate to Settings → Connectors in your organization
  • Click Connect on OpenRouter and approve the request in the browser
  • Verify that the card shows Connected
  • Open Chat on any board and ask a question — it now runs on your account

Provider setup

OpenRouter setup is available today. The other instructions describe planned connectors and cannot be completed until those providers ship.

GitHub setup
  1. Click Connect on the GitHub connector card.
  2. You are redirected to GitHub's OAuth consent screen.
  3. Approve the requested scopes (repo read access, code search).
  4. After redirect, your account is linked. Each team member repeats this for their own GitHub account.
  5. When this connector ships, Chat will read repo content on your behalf. GitHub sources are also coming soon; see the note above.
Confluence / Jira setup
  1. Click Connect on the Confluence or Jira card.
  2. Authorize via Atlassian's OAuth flow. Both products share the same Atlassian identity.
  3. Confluence provides: spaces, pages, and content search.
  4. Jira provides: projects, issues, and issue search.
  5. These will be user-scoped. Each team member will connect their own Atlassian account.
Slack / Notion / Intercom setup

These will be org-scoped OAuth providers. One team member will connect them for the organization.

  1. Click Connect on the provider card.
  2. Authorize at the provider's consent screen.
  3. The org-wide token is stored for the organization.
  4. Slack gives you channels and message search. Notion gives you databases and pages. Intercom gives you conversations and support articles.
Sentry / LogRocket / Terraform setup (API key)
  1. Go to the provider's dashboard and generate an API key or auth token.
  2. Back in the portal, click Configure on the provider card.
  3. Paste the API key into the field and save.
  4. The key is encrypted at rest before storage.
  5. One key covers the whole organization.
OpenRouter setup (PKCE)

OpenRouter uses OAuth 2.0 with PKCE. No client secret is required.

  1. Click Connect on the OpenRouter card.
  2. Authorize at OpenRouter's consent screen.
  3. Return to the portal and verify that the card shows Connected. Your organization can now use model routing and Chat completions.

What's next

Organization Settings

Configure archetypes, tags, roles, and icons for your organization.

Permissions & Access

Control who can view and edit boards, internally and externally.

Connecting Sources

Learn how sources feed real-world data into your boards.