Ada Account Connections
Ada asks someone to connect an app profile to Lovelace when Ada needs to know which Slack member, Linear member, GitHub user, Discord member, or email sender belongs to a specific Lovelace account.
Why Ada Asks
Ada asks for an account connection when a request follows the person across apps, uses Lovelace-owned history, shows recent Ada work, or continues in a different Ada surface.
Without the connection, Ada answers only requests that do not depend on the person's Lovelace account. Ada does not silently treat that app profile as a Lovelace user.
What Changes After Connecting
After a person connects an app profile:
- Ada matches that app profile to the person's Lovelace account.
- Recent Ada work appears in connected app surfaces.
- Requests continue across connected Ada surfaces.
- Ada asks for decisions in the app where the person is working.
The connection does not make that person an admin in Slack, Linear, GitHub, Discord, or Lovelace. It also does not let other teammates access the person's Lovelace account.
Where People See Prompts
| App | Where prompts appear |
|---|---|
| Slack | Ada's Home tab, direct messages, or replies when Ada cannot identify the person. |
| Linear | Issue threads when Ada needs to connect the Linear member to Lovelace. |
| GitHub | Issue or pull request conversations when Ada needs to connect the GitHub user to Lovelace. |
| Discord | Ada commands, mentions, or account-status replies. |
| Email replies when Ada needs to confirm the sender's Lovelace account. |
When To Reconnect
Reconnect when someone changes workspaces, uses a different account in the outside app, loses access to an old account, or sees Ada identify them as unconnected after they expected to be connected.