Connect project tools

Linear and Notion connections let squads work with project information outside their repositories. An administrator connects the account in Settings → Integrations; each squad then selects the connection it can use. Connecting an account does not automatically give every squad access.

For source code, follow GitHub setup. For conversations in Slack, Discord, or Telegram, use chat channels.

Connect Linear

1. Create a personal API key in Linear for the account Tau should use. Limit its teams to the ones relevant to your squads. Read access is sufficient for issue search and assignment routing.
2. In Tau, open Settings → Integrations → Linear and enable the card.
3. Under Add account, enter a recognizable name and the personal API key. Choose Create and validate.
4. Confirm validation succeeds, then enable the account if it is disabled.
5. Open the squad’s Settings → Integrations, enable Linear, and select that account. Under Linear Routing, add the Linear team IDs for assigned issues this squad should receive, then save your changes.

For assignment updates, expand Webhook delivery in the global Linear card. Copy the displayed URL into an Issue webhook in Linear and configure the same signing secret on both sides. Save the secret in Tau to enable delivery. The connected account supplies the assignee identity; Tau checks issue access, team, and assignee before routing an update.

Tau CloudSwitch to Self-hosted

Use the webhook URL from your hosted instance’s Linear card. Linear uses a personal API key for this connection; the GitHub or Notion Cloud authorization flow does not connect Linear for you.

Self-hostedSwitch to Tau Cloud

Direct Linear webhooks require a public URL that reaches your instance. Set the correct public instance URL before copying the webhook address. See configuration if Tau displays a local-only address.

Ask your squad to find an issue in an allowed team and summarize it. If assignment updates are missing, check the connected account, team ID, issue assignee, and webhook configuration before changing the squad’s workflow.

Connect Notion

Enable Notion in Settings → Integrations and expand its settings.

Tau CloudSwitch to Self-hosted

Choose Connect Notion. Follow Notion’s authorization flow, choose the workspace and pages to share, and return to Tau. Cloud supplies the OAuth application configuration.

Self-hostedSwitch to Tau Cloud

Create an OAuth integration in the Notion Developer Portal with Read content, Insert content, and Update content capabilities. Register the exact callback URL shown in Tau’s Notion card. Enter its client ID and client secret, acknowledge those capabilities, and choose Save OAuth application and acknowledge capabilities. Then choose Connect Notion, authorize the workspace and pages, and return to Tau.

In the squad’s Settings → Integrations, enable Notion and select the connected workspace. Wait for its setup status to become ready before asking the squad to use Notion. The connection makes the Notion command-line tool available in the squad environment.

Ask the squad to read and summarize a page you shared. If it cannot see a page, check the sharing choice in Notion as well as the squad’s connection. Authorizing the workspace does not make every page readable. To connect a different workspace, authorize it and assign the resulting connection explicitly.

Manage access later

Disable an integration globally to stop new use across squads while retaining account choices. Disable it in a squad to preserve that squad’s selection for later. Removing a connection affects the squads assigned to it; review the usage shown before confirming removal.

Use Validate, Reconnect, or the account’s key-replacement action when its status requires attention. Enter credentials only in the integration’s credential fields. Once the connection works, ask the assistant for a specific task using the project information you shared.