Skip to main content
A connected account is your own account at a vendor — GitHub, Bitbucket, Slack, Microsoft, Linear, Google — linked to Sazabi so the agent can act as you. It is personal to you: connecting one affects only your actions, not the whole organization. Manage them under Settings > Connected accounts.

​
Connected accounts vs integrations

Connected accounts and integrations both link Sazabi to a vendor, but they belong to different owners:
  • An integration is an organization-level connection. One admin connects it, the organization owns it, and it acts under a shared organization identity (a bot, an app install, a workspace token).
  • A connected account is your personal connection. You connect it, it is scoped to you, and it lets the agent act under your identity at the vendor.
Some vendors support both — your organization can have the GitHub integration while you also connect your personal GitHub account. When that happens, the credential Sazabi uses depends on who the agent is acting for.

​
Which credential Sazabi uses

When the agent takes an action on your behalf for a vendor that has both a personal connected account and an organization integration, it uses your personal connection first:
  1. Your connected account, if you have one. The action runs under your identity at the vendor, so the vendor attributes it to you.
  2. The organization integration otherwise. The action runs under the shared organization identity, and Sazabi adds a “Requested by” note so it is clear the work came from you.
For example, when the agent opens a pull request it uses your personal GitHub or Bitbucket connection if you have one, and falls back to the organization’s app install otherwise. When it files or updates a task in Linear or Jira it uses your account first, and the organization integration otherwise. You get correct attribution when you connect your own account, and things still work when you have not.

​
Connect an account

You can connect an account from the dashboard or the CLI.

​
In the dashboard

Go to Settings > Connected accounts, choose the vendor, and authorize Sazabi. You are taken to the vendor to approve access and returned to Sazabi when it completes.

​
With the CLI

Connect and manage accounts with the Sazabi CLI (installed and authenticated — see CLI reference):
Disconnecting an account (dashboard or sazabi connected-accounts disconnect <provider>) stops the agent from acting as you at that vendor; it falls back to the organization integration where one exists.

​
Further reading

Integrations

Organization-level connections and the features each provides.