Skip to main content
Connections is an enterprise feature. An open build has no Connections tab.
Settings › Connections lists the accounts a document can come from, one row each with its mark:

​
Connections and sources

A connection is an account: the site and the credentials TrueCourse reads through, made once per workspace. A source is what that account reads, a Jira project or a Confluence space, added on Context like a repository or a documentation site. One connection can serve several sources. Connecting an account is this tab’s job. Adding what it reads is Context’s: once the Atlassian site is connected, Add context offers Jira and Confluence among the connected accounts, and when it is not, the dialog points here.

​
Connect an Atlassian site

An Atlassian site is one account, and one API token serves both Jira and Confluence on it, so there is one row for both. Open the Atlassian row. You need three values.
1

Site URL

The address of your Atlassian site, with no path:
Open Jira or Confluence in your browser and copy the origin. From https://acme.atlassian.net/jira/software/projects/KAN/boards/1 or https://acme.atlassian.net/wiki/spaces/ENG/pages/12345 the site URL is https://acme.atlassian.net.
2

Account email

The email of the Atlassian account the API token belongs to. The account needs browse access to the Jira projects and read access to the Confluence spaces you will add; a regular member account works, and admin rights are not required. For production use we recommend a dedicated service account, so the connection does not break when a person leaves the team.
3

API token

Atlassian API tokens are created on the account’s profile, not in Jira or Confluence:
  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens, signed in as the account above.
  2. Press Create API token, label it (for example TrueCourse), and confirm.
  3. Copy the token immediately. Atlassian shows it only once.
TrueCourse stores the token encrypted and never displays it again.
4

Test, then save

Test makes one read against each product with these credentials and answers per product, because an account can have Jira access without a Confluence license. A connection with one product answering is still a connection.
  • Authentication failed: check the email and token pair.
  • Access denied: the account has no access to that product on this site.
Press Save. The row now reads Connected, with the site and when it was saved.
To change the token, open the row and paste a new one; leaving the field blank keeps the stored token. Disconnect deletes the connection and pauses every Jira and Confluence source that read through it. Their documents stay until the sources are removed, and connecting the account again is a Resume rather than an add.

​
What the others do today

Google Drive, OneDrive, Notion and Slack say Coming soon. None can be connected, and their rows carry no controls. They are listed rather than hidden so the page is honest about where this is going, and marked rather than offered so it is honest about what it does now.

​
Next steps

Jira

Add a project as a source, and what an issue becomes.

Confluence

Add a space as a source, and what a page becomes.

Sources

Every kind of source, and how each one syncs.

Enterprise edition

What else the enterprise edition adds.