Skip to content
alfe.ai

Connecting an account

Connecting an account authorizes Alfe to act in a third-party app on that account’s behalf. It’s a short, browser-based flow that you complete once.

Before you start

Section titled “Before you start”
  • You need permission to manage connections in your organization. If you don’t see the option to connect, ask an organization admin.
  • Decide which scope the connection should live at — your whole organization, a team, a project, or a single agent. Scope decides who can use the connection; see Connection scopes. You can always move a connection to a different scope later.
  • Have the credentials for the account you want to connect ready — you’ll sign in to the provider directly, not to Alfe.

Connect from the dashboard

Section titled “Connect from the dashboard”
  1. Open the Connections hub in the dashboard at app.alfe.ai.
  2. Choose the scope you want the connection to live at.
  3. Select Connect and pick the provider you want to connect (for example GitHub, Notion, or Google Workspace).
  4. A popup window opens the provider’s own sign-in and consent screen. Sign in to the account you want to connect if you aren’t already.
  5. Review the access Alfe is requesting and approve it. You’re approving the provider’s request directly — Alfe never sees your provider password.
  6. The popup closes automatically and the new connection appears in your Connections hub, ready for agents to use.

If you close the popup or decline on the provider’s screen, nothing is connected — you can start again.

What Alfe receives

Section titled “What Alfe receives”

When you approve, the provider hands Alfe a set of access tokens scoped to exactly what you consented to. Those tokens are stored encrypted and are never displayed back to you. The connection row shows only non-sensitive details, such as the connected account’s name and when it was connected.

Connecting more than one account

Section titled “Connecting more than one account”

Many providers let you connect multiple accounts of the same type — for example a personal GitHub account and an organization one, or two Google Workspace mailboxes. To add another, run the connect flow again and sign in to the second account. Each account appears as its own connection.

When more than one account of the same provider is available, agents select which account to use at the point they use it, so connecting several accounts side by side is safe.

Reconnecting

Section titled “Reconnecting”

A connection can lapse — for example if access expires or is withdrawn on the provider’s side. When that happens the connection is flagged in the hub, and you’ll see a Reconnect option on it.

Reconnecting reruns the same approval flow to restore access. It keeps the same connection, so anything already pointing at it — agents, teams, projects — keeps working without further changes.

Connect from the CLI or an agent

Section titled “Connect from the CLI or an agent”

You don’t have to use the dashboard:

  • CLI — see alfe integration.
  • The agent itself — over MCP or the Agent API, an agent can start a connect flow for the accounts it needs.

Next steps

Section titled “Next steps”