Skip to content

Authorize an app account so Elaichi can turn the app's documented methods into tools that AI clients can run. A connection is one authorized account for an app, such as your Jira, your team's shared HubSpot, or the company's Salesforce.

Where to find it: Connections → Add connection. You can also choose Connect on a connector's row or detail page under Connectors.

Elaichi keeps the credentials in a secure vault and uses them only when a tool runs.

These steps match the video, which connects Notion. Menu paths can change as the app updates (checked October 2026).

Before you start

Permission What it allows
connection:create Connect an account for your own use.
connection:share Share a connection with a member, a team, or everyone in your organization when you connect it.

You need connection:create or connection:share to see Add connection. The built-in Member role and every role above it include both. The built-in Guest role has neither, so a Guest cannot connect accounts. Without connection:share, you can create private connections only.

An administrator can restrict a connector for a role or a member. A restricted connector shows a restriction icon in the Add connection list. Hover over the icon to read the reason, and select it to ask an administrator for access.

Connect an account

  1. Choose Connections in the sidebar, then Add connection.
  2. Search for the app, or filter by category, then select it.
  3. Optional: enter a Label. Leave it empty to name the connection after you and the connector.
  4. Optional: under Share with, choose Add people or teams. Pick A member, A team or Everyone, choose a level, and choose Add. Skip this to keep the connection private. Elaichi shows Share with only if you have connection:share.
  5. Choose Connect. For an app such as Notion, Elaichi first asks how you want to sign in. Choose OAuth 2.0. The other choice is an API key.
  6. Elaichi opens the app's sign-in window. Sign in to the app and approve the access it requests. In Notion's window, select Select pages, choose the pages Elaichi may use, then choose Allow access.

Elaichi shows Connection added, and the connection appears in the list with the status Active.

Some connectors need your organization's own OAuth app before anyone can connect. In that case, Elaichi shows This connector needs setup first. Someone who can set up the connector sees a Set up button. Everyone else sees a message to ask an administrator.

Most connectors work with Elaichi's own OAuth app, and most organizations keep it. If your policy requires it, an administrator can add your organization's own OAuth app on the connector's page instead. Connections made before the change stop working at their next refresh and must be connected again.

Tip

Every connection automatically gets a toolbox named "{connection name} tools". It appears on the Toolboxes page under Automatic, and AI clients can use it through your organization's MCP endpoint right away.

Who owns a connection and who can use it

Two separate things decide who can reach a connection.

The owner is the member who connected the account. A connection has exactly one owner. Only the owner can transfer or delete it. See Transfer and offboard.

Access is a list of grants. A new connection has no grants, so it is private to its owner. Add grants in Share with when you connect, or later in the connection's Manage access dialog. Each grant names a member, a team, or everyone in your organization, and carries one level.

Level What the grantee can do
View See the connection and its configuration. Cannot run it.
Use See the connection and run its tools.
Edit Change the connection's settings and who it is shared with.

A team grant needs a team to exist. If the list is empty, create a team under Settings → People → Teams first.

Who can reach a connection
flowchart TD
  Connect["You connect an account"] --> Owner["You own it. It is private."]
  Owner --> Share{"Share with (optional)"}
  Share -->|"A member"| User["One person"]
  Share -->|"A team"| Team["The members of one team"]
  Share -->|"Everyone"| Org["Everyone in your organization"]
  Owner --> Tools["Tools run with the vaulted credentials"]
  User --> Tools
  Team --> Tools
  Org --> Tools

In words: a connection starts private to its owner. The owner can share it with one member, one team, or everyone in the organization. In every case, tools run with the credentials in the vault.

Reconnect a connection

Reconnect when a connection shows Needs sign-in or Disconnected, or finish a connection that shows Awaiting sign-in.

  1. Choose Connections in the sidebar.
  2. On the connection's row, choose the Reconnect icon. For a connection that never finished, the icon reads Finish sign-in. You can also open the row's actions menu and choose Reconnect.
  3. Sign in to the app again in the window that opens.

The connection keeps the same owner and the same grants. Toolboxes that use it work again as soon as its status returns to Active.

The owner and anyone with Edit access can reconnect a connection. Only the owner can finish a connection that is Awaiting sign-in, because finishing it binds the owner's own account to it.

What the status means

Status Meaning What to do
Active The connection works. Nothing.
Awaiting sign-in The sign-in with the app was never finished. The owner chooses Finish sign-in.
Needs sign-in The app's sign-in stopped working, for example because access expired or was revoked. Choose Reconnect.
Disconnected The account is no longer available in the vault. Choose Reconnect, or delete the connection.
Setup incomplete The connection works and its tools run, but the connector's setup step is still pending. Choose Finish setup on the connection's page.

Elaichi refreshes working connections by itself. You reconnect only when the status asks for it.

What to know

  • You see the connections you own and the connections shared with you, directly, through a team you belong to, or with everyone in your organization. No organization role widens that. An unshared connection stays private to its owner, even from an organization owner.
  • Deleting a connection immediately breaks the toolboxes and synthetic tools that use it. You cannot undo it. When someone leaves, transfer their connections first. See Transfer and offboard.
  • Browse what an app can do under Connectors before you connect. The connector's detail page lists its tools.