Skip to main content
When Abbie uses an integration, the call happens under one of two identities: hers, or yours. Understanding which is which matters because it decides what she’s able to see and do, and whose access is on the line if something goes wrong.

​
Abbie’s own login

Some integrations can be connected directly to Abbie herself, separate from any individual person’s account. An admin sets this up from the Abbie’s identity section of Integrations settings. This is what she uses for work that isn’t tied to a specific conversation with you, for instance, something running on a schedule when you’re not actively there to supply your own connection.

​
Your personal connection

If you’ve connected an integration personally, the normal, individual sign-in you’d use yourself, Abbie can use that connection on your behalf while she’s actively working with you.

​
What Abbie will never use

The wider set of shared, team-level connections your account has configured for other purposes are deliberately off-limits to her. Abbie only ever acts through her own login or your personal one, never a shared connection she wasn’t specifically given, even if one technically exists on the account. This is what stops her from quietly having more access than anyone actually intended to give her.

​
Why the distinction shows up in the product

Wherever an integration’s connection state is shown, the integrations catalogue, or a card asking Abbie to connect something, you’ll see it labelled plainly as Abbie’s login, Your login, or Needs connecting, so it’s always clear which identity a given action would run under before you approve anything.