Jira, Linear, and Sentry
Jira
Open /admin/integrations, choose Jira, select an editable installation, and continue to Atlassian. Approve read-only Jira access and select the provider-named site when Atlassian returns more than one. Merge Preflight never asks for a Jira Cloud email, API token, site slug, Cloud ID, or base URL, and it never writes to Jira.
Linear
Open /admin/integrations, choose Linear, select an editable installation, and continue to Linear. A workspace administrator installs Merge Preflight as a read-only application actor; the workspace name and identity are discovered during OAuth, with no API key or workspace identifier entry.
Sentry
Open `/admin/integrations`, choose Sentry, select an editable installation, and connect through Sentry OAuth. Sentry rules can block unrelated work during active critical incidents.
View Sentry policyCredential handling
Jira, Linear, and Sentry OAuth credentials are application-encrypted before persistence and are never rendered after authorization. Jira Data Center and self-hosted Sentry token fallback stores only encrypted token material. If provider authorization fails, reconnect it from the integration page.