Integrations

Integrations let you connect Ablebase to external platforms so you can link work to repositories and import issues for accessibility triage. Connections are managed per organization from Settings → Integrations.

Supported platforms

Platform	What connecting enables	Status
GitHub	Link products to GitHub repositories and import issues into Ablebase.	Available
Linear	Connect a Linear workspace. Issue import is coming soon.	Available (connection only)

Each platform must also be configured on the server by an administrator before it appears as connectable (see Prerequisites). Until then, its card shows Coming soon or a “not set up” message.

Who can manage connections

Only organization admins and owners can connect, resync, or disconnect. Other members see the connection status read-only, with no controls.

Connecting an account

You can connect multiple GitHub organizations and multiple Linear workspaces to a single Ablebase organization. Use the + button in a platform’s card header to add another connection alongside existing ones.

GitHub

GitHub uses a GitHub App installation.

Go to Settings → Integrations.
On the GitHub card, click Connect (or the + to add another organization).
You’re taken to GitHub to install the Ablebase GitHub App on the organization you choose, and to select which repositories it can access.
GitHub redirects you back to Ablebase, which finishes the connection and shows the linked organization.

To change which repositories a connection can access later, open the connection’s ⋯ menu and choose Configure in GitHub.

Linear

Linear uses OAuth authorization.

Go to Settings → Integrations.
On the Linear card, click Connect (or the + to add another workspace).
Approve the authorization request on Linear.
Linear redirects you back to Ablebase, which finishes the connection and shows the linked workspace (name and logo).

Importing issues from a repository

Once a GitHub organization is connected, you can link individual repositories to a product and import their issues into Ablebase for accessibility triage. This is set up per product, on the product’s Settings page, in the Connected repositories card.

Linking a repository

Open a product and go to its Settings page.
In the Connected repositories card, choose Link a repository. If no GitHub organization is connected yet, connect one first from Settings → Integrations.
Pick a repository the connected GitHub App can access.
Set the label filters and options (below), then save.

Label filters

Choose which of a repository’s issues are imported by matching their GitHub labels:

Include issues labelled — only issues carrying these labels are imported.
Match — with Any of the labels, an issue matches if it has at least one include label; with All of the labels, it must carry every include label.
Exclude issues labelled — issues carrying any of these labels are skipped, even if they also match an include label.

Options

Each linked repository also has these toggles:

Import closed issues — also import issues that are already closed on GitHub (off by default; open issues only).
Keep open/closed status in sync — reflect the GitHub issue’s open/closed state on the Ablebase issue.
Post a tracking comment on GitHub — comment on the GitHub issue to say Ablebase is tracking it (and again when tracking stops).
Include a back-link (private repos only) — include the Ablebase issue link and title in that comment. Suppressed on public repositories for privacy.

Syncing, editing, and unlinking

Each linked repository row offers:

Sync now — import matching issues on demand. Runs in the background; the row shows Syncing… and a sync-state badge (including Sync error if something went wrong).
Edit filters — change the filters or options. If tightening the filters means previously-imported issues would no longer match, Ablebase asks what to do with them: Stop tracking, keep open or Stop tracking and close.
Unlink repository — stop importing from the repository. New issues are no longer imported and status sync stops, but already-imported Ablebase issues are kept.

Imported issues appear in the product’s Issues list with a GitHub source badge, carrying the title and description copied at import time. The Ablebase issue and the GitHub issue then stay independent — editing one doesn’t overwrite the other.

Automatic syncing

When the GitHub App’s webhooks are configured on the server, linked repositories also sync in near-real-time — new and changed issues import without waiting for a manual Sync now. A few behaviours to note:

Closing an issue on GitHub doesn’t untrack it. If Keep open/closed status in sync is on, the state is reflected in Ablebase; the issue stays linked.
Deleting an issue, removing a repository from the GitHub App, or disconnecting the organization untracks the affected issues.
A manual Sync now also untracks any issue whose labels no longer match the current filter.

Setting up the webhook is an administrator task — see GitHub App (integrations).

Keeping details up to date

If a connected workspace or organization changes its name or logo, use Resync details from the connection’s ⋯ menu to pull the latest information without disconnecting.

Resync also transparently renews the stored access token when needed, so long-lived Linear connections keep working.

Connection states

A connection can be in one of these states:

State	Meaning	What to do
Connected	Active and healthy.	Nothing — it’s working.
Needs reconnect	The platform revoked the connection (e.g. the app was uninstalled or access was withdrawn on the provider’s side).	Admins see a Reconnect button to restore it.

Disconnecting

From the connection’s ⋯ menu, choose Disconnect.

For GitHub, this uninstalls the Ablebase GitHub App from that organization, keeping both sides in sync so a later reconnect goes through the normal install flow again.
For Linear, this revokes the stored access token on Linear’s side.

Disconnecting removes the connection from Ablebase but does not delete any issues you have already imported.

Prerequisites

Connecting a platform requires two things to be in place:

The Integrations module is enabled for your organization (Settings → Features).
The platform is configured on the server by an administrator:
- GitHub requires a configured GitHub App (see the GitHub App environment variables).
- Linear requires LINEAR_CLIENT_ID and LINEAR_CLIENT_SECRET (see Linear environment variables).

If a platform is not configured on the server, admins see a message explaining that a server administrator must add the credentials first.