Source Connections
Connect the tools where your product work already lives — Linear, Notion, Atlassian (Jira/Confluence), GitHub, and Miro — 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.
Connecting a GitHub repository owned by an organization?
GitHub shares a repository once the dot•requirements app is installed on it. When you connect GitHub and the app isn’t on any repository you can access, GitHub takes you on to install it and choose the repositories; if it already is, you come straight back. To share more repositories later, use Install the dot•requirements app on more repositories beside GitHub on the integrations page. For repositories owned by an organization, GitHub may require one of your org admins to approve the installation before it works.
The app’s installation page lists write access to code, pull requests, Actions and checks. That is for a project’s agents, which work in the repository a team admin chooses for the project, through the same dot•requirements app: they open each solution’s pull request, read its checks and reviews, and reply to review findings and resolve them, and the agent that watches it brings its branch up to date. The assistant only reads.
Miro connected to the wrong team, or refusing to connect?
The access you grant is scoped to one Miro team, chosen during Miro’s approval screen. If you granted the wrong team, disconnect and connect again, picking the right one.
On Miro Enterprise plans, this kind of access is off until a Miro admin enables it. If connecting fails and your company runs Miro Enterprise, ask a Miro admin to enable AI/MCP access for your organization or team (and, if your org restricts which apps may connect, to allow dot•requirements).
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.