Skip to main content
Every connected account has its own autonomy level. It decides how far Hive may go with that account — from reading and summarising only, up to carrying out actions your policy has approved. Levels are set per account, not per provider, because a team often connects a shared mailbox that may act next to a personal one that should only be read.

​
The three levels

Every write to a connected tool is routed to human approval today, whatever the account’s level. Levels set the ceiling; your policy and autonomy settings and approvals decide what actually runs.

​
Change an account’s level

1

Open the provider

In Integrations → Connectors, select a connected tile to open its Accounts panel.
2

Pick a level

Choose Read, Draft or Act for the account you want to change.
Only Owners and Admins can change autonomy levels.

​
Who owns a connection

Each connection is owned by the member who connected it. In the Workspace connections panel, each account shows one of:
  • Owned by another workspace member — a teammate connected it.
  • Needs reconnect to establish an owner — an older connection made before ownership was recorded. Select Reconnect to claim it.
Only the owner can disconnect their own account. Sharing a workflow or an agent never shares the owner’s connected accounts: whoever runs it uses their own.

​
Workspace connections (Owners and Admins)

Owners and Admins see a Workspace connections panel listing other members’ connections and any older connections that still need an owner. It shows metadata only. Personal credentials, configuration, scopes, webhook URLs and actions stay private to their owner.

​
Enabling a provider for members

A provider must be enabled before members can connect personal accounts. An Owner or Admin enables it by connecting it. Until then, members see: “A workspace administrator must enable this provider before you can connect a personal account.”

​
Several accounts of one provider

When you connect more than one account of a provider — for example four Gmail mailboxes — they appear under one tile. Accounts are listed in an order, primary first. You can reorder them with the arrows in the panel. The order sets which account an approval’s account picker offers first. Hive never quietly switches to another account on its own. When more than one account could carry out an approved action, the approval shows an account picker.

​
How levels fit with the rest of Hive’s safety

Autonomy is layered. For an action to run automatically, every layer must allow it:
  1. the account’s level (Read, Draft, Act);
  2. the workspace’s per-action autonomy rung, spend caps and budgets (Safety and control);
  3. the action’s blast radius and reversibility — money, legal and irreversible actions always ask a human;
  4. the kill switch, which halts everything when engaged.

Review and approve

How approvals work.

Autonomy and blast radius

The safety ladder.