Source Connections
Connect the tools where your product work already lives — Linear, Notion, Atlassian (Jira/Confluence), and GitHub — so the requirements assistant can draft specs from your existing material instead of a blank page.
Connect a source
You connect a source once, with a single approval through that tool’s own sign-in screen. There are no API keys or tokens to copy.
There are two places to start:
- From project settings. Open your project’s Integrations settings and find the Connected Sources panel. Click Connect next to a source (e.g. Linear, Notion, or Atlassian) and approve access on the provider’s screen. When you return, the source shows as connected.
- From the chat. If you ask the assistant to draft from a source you haven’t connected yet, it offers a Connect button right in the conversation. Connecting opens in a new tab, so your conversation is never lost — when the connection lands, the in-chat prompt updates to show the source is connected, and you carry on in the conversation.
A connection is personal to you. Sharing a project with a teammate does not share your connected accounts — each person connects their own.
One GitHub-specific note: when you connect GitHub you also choose which repositories to share, and for repositories owned by an organization, GitHub may require one of your org admins to approve the connection before it works.
Draft from your material
Once a source is connected, point the assistant at a specific item — for example, a Linear issue, a Notion page, a Jira ticket, or a GitHub issue — and ask it to draft requirements. The draft reflects the specifics of that item rather than being written from scratch.
If you point at something the assistant can’t read (it doesn’t exist, or you don’t have access), it tells you so plainly instead of inventing content.
Stay connected
A connected source keeps working across sessions — you won’t be asked to sign in again for routine use. If a connection lapses, the assistant tells you and offers to reconnect right in the conversation; meanwhile, the rest of the product and any other connected sources keep working normally.
Review and disconnect
The Connected Sources panel in your project’s Integrations settings lists everything you’ve connected. Disconnecting a source does two things:
- The assistant can no longer read that material on your behalf, and dotrequirements keeps no stored access to it afterward.
- The access you granted is revoked at the source, so the credential issued for that connection can no longer be used.
Your credentials are protected
Stored credentials are encrypted, and they’re only ever decrypted on the server to act on your behalf — they’re never handed back to your browser. So neither a copy of stored data nor a hijacked session exposes the keys to your connected accounts.