Connect issue trackers and documents
Connect an issue tracker so reviews can read referenced work, or a document service so you can pin relevant pages to repository paths.
An organization administrator must authorize or disconnect these services. Use a recent sign-in session; sign in again if Proofline requests it. Each connector must also be available on your Proofline deployment.
Choose the allowed sources#
Open Organization → Connections and choose a provider. The connection form asks for stable resource IDs, one per line.
| Provider | Allowed resources |
|---|---|
| Jira Cloud | Project IDs |
| Linear | Team IDs |
| Asana | Project GIDs |
| Confluence Cloud | Space IDs |
| Notion | Root page or database IDs |
| Google Drive | Folder IDs |
Use the IDs of the resources you want reviews to read. Display names do not substitute for these IDs.
Authorize the connection#
- Select Connect on the provider's page.
- Enter the allowed resource IDs.
- Select Continue to the provider.
- Complete the provider's authorization and return to Proofline.
- Wait for verification, then check the connected account and allowed resources.
The provider must confirm that the account can read each allowed resource. If authorization reaches several accounts, choose the intended account and authorize again.
If the page says the provider is unavailable on this deployment, ask your Proofline operator to configure it. Repeating authorization does not resolve deployment configuration.
Use the connected sources#
Reviews read Jira and Linear references from the pull request text, or linked Asana tasks within the allowed projects. Asana task comments are excluded.
A review uses one tracker connection. When several are active, it prefers Jira Cloud, then Linear, then Asana. Connecting several trackers does not make a review read all of them.
For Confluence, Notion, or Google Docs, pin a document to repository paths. Connecting a document service alone does not select a page for a repository.
Change or remove access#
Use Authorize again to update the allowed resources or restore provider authorization. Check the account and resource list after verification.
Use Disconnect and confirm the action to remove the connection. Earlier review records remain; a disconnected source cannot supply fresh context.