TerraTrue for Confluence allows product and engineering teams, as well as any other team across the business, to initiate and track risk reviews directly from within Confluence without leaving their documentation workflow. By embedding launch creation and real-time status tracking into the Confluence page interface, the integration eliminates manual triage and context switching between documentation and risk management platforms. Positioned natively in the Confluence toolbar and metadata byline beneath the page title, it establishes a seamless bridge between product specs and TerraTrue launches.
Prerequisites & Permissions
Setting up the integration requires an admin to complete the following steps in both TerraTrue and Atlassian Confluence:
-
Configure Jira Integration: Navigate to Integrations → Jira and connect using your Atlassian site URL, account email, and Jira API token. Your Jira site URL must be unique across all TerraTrue instances; using the same URL across multiple or staging orgs will cause Confluence launch creation to fail.
-
Enable TerraTrue AI (Optional): Go to Settings → AI Settings and turn on Enable TerraTrue AI. While this step is optional, turning it on enables TerraTrue to automatically summarize the Confluence page content and populate the launch description. If left disabled, launches can still be created normally from Confluence, but the launch description field will remain blank.
-
Publish a Launch Type: Ensure at least one launch type is published under Settings → Launch Types.
-
Enable Confluence Integration: Go to Integrations → Confluence integration, toggle on Enable Confluence Integration, and select the default launch type and product for incoming Confluence launches.
- Install the TerraTrue app in Confluence: After you complete the TerraTrue configuration, a Confluence user with site or organization admin rights must install the TerraTrue Forge app.
To create a launch from a Confluence page, an individual user's Confluence email address must match an active TerraTrue account provisioned with the Launch Summary Editor permission. Upon their first interaction with the TerraTrue panel in Confluence, each user must authorize a one-time Atlassian Forge consent prompt ("Allow access") to grant individual access.
How TerraTrue for Confluence Works
The integration runs as an Atlassian Forge app installed on your Confluence site.
On Confluence pages, you will see a TerraTrue metadata entry alongside standard page details. To create a launch in TerraTrue from Confluence, click on the TerraTrue button. In the modal that appears, click on Create TerraTrue Launch.
Tip: Create the launch when the Confluence Page has key details in place. TerraTrue takes a snapshot of the page at creation time and will not sync later edits.
When an authorized user clicks Create TerraTrue Launch, TerraTrue initiates launch creation using the default launch type and product configured in your integration settings, setting the Confluence page title as the launch title. If TerraTrue AI is enabled, the platform analyzes the body of the Confluence page, generates a concise summary, and populates the launch description. Simultaneously, TerraTrue attaches the full page content as a Markdown file (confluence_page_content.md) and establishes bidirectional linking between the Confluence page and the launch.
After launch creation, the Confluence page byline displays the current review status (for example, TerraTrue • Ready for Review), and the expanded panel presents a status chip with a direct link. Clicking the launch title inside the expanded panel opens the launch directly in TerraTrue in a new browser tab.
Core Capabilities & Logic
Launch creation is governed by strict identity and permission checks. TerraTrue correlates user accounts by matching the authenticated Confluence user's email address to an active TerraTrue user. If no matching user exists or if the user lacks the Launch Summary Editor permission, TerraTrue rejects the request and displays a "Couldn't create launch" error in the panel rather than silently creating the launch under a generic or system account.
Status tracking in Confluence updates based on specific interaction triggers rather than a continuous feed. The collapsed page byline re-computes its status whenever the page loads or when the expanded panel is opened and closed. When left open, the expanded panel re-checks the launch status whenever the browser tab regains focus.
Content capture is executed as a creation-time snapshot. Edits made to the Confluence page after launch creation do not update the launch description or the attached Markdown file in TerraTrue. Furthermore, launch metadata remains associated with the Confluence page indefinitely until the launch is permanently deleted from the trash in TerraTrue, after which a new launch can be created and overwrite the previous metadata.
Frequently Asked Questions
Which Confluence content types are supported by the integration?
The integration supports standard Confluence pages and live pages. Other Confluence content types—such as slides, folders, and whiteboards—are not supported at this time.
Does updating a Confluence page update the linked TerraTrue launch?
No. The launch description and attached Markdown file represent a snapshot taken at the moment of launch creation. Re-editing the Confluence page content does not alter the description or attachments in TerraTrue, though the two records remain linked.
What happens if a user without TerraTrue access tries to create a launch?
If a Confluence user's email address does not match an active TerraTrue account with the Launch Summary Editor permission, the request is rejected. The user will see a "Couldn't create launch" error in the Confluence panel, ensuring launches are never created anonymously or under system accounts.
Can users select a different product or launch type when creating a launch from Confluence?
Not during creation. All launches created from Confluence automatically adopt the default product and launch type specified in TerraTrue's Confluence integration settings. However, product assignments and launch types can be modified within TerraTrue after the launch has been created.
Why must our Jira site URL be unique across TerraTrue organizations?
The Confluence integration identifies your organization by matching the installed Confluence site back to your connected Jira site URL. If a staging or test TerraTrue organization points to the same Jira URL as your production instance, Confluence launch requests will fail due to routing conflicts.