Skip to main content
Every member of a Hive workspace has exactly one role. The role decides what they can see, which proposals they can approve, and which settings they can change. Roles are ranked, so each role can do everything the roles below it can, plus more. A member also needs a seat to use the workspace at all.

The four roles

The read-only Analyst role (viewer in the product’s data) was retired in October 2026, when every member came to need a paid Pro or Max seat. Members who have the Analyst role are removed from their workspaces with this release; an Owner or Admin can invite them again at another role, with a seat. An invitation sent at the Analyst role before then can no longer be accepted and holds no seat: it is listed with No role, and the person can join only once you invite them again at another role. Anyone still listed with it shows as No role on Members, and can do nothing in the workspace until an Owner or Admin removes them, or gives them another role and a seat. People added directly in your sign-in provider now join as Operator (see Team and workspace).

What each role can do

Each member’s seat also decides what they can do: without an active seat a member can do nothing in the workspace, whatever the role. On an earlier plan, an Approver seat gives only what is routed to its holder, and Signals come only with a Max seat.

Approval tiers

Every proposed action carries a blast-radius tier from B0 to B4. The tier sets how senior the approver must be. When a proposal routed to a role is above your tier, the review panel tells you it is “above what your role can approve” and shows you exactly why Hive proposed it. A card you hold yourself — one raised by your own signal, run, schedule or workflow — you can approve at any tier from your own Review decision panel on the Signals page. See Autonomy and blast radius for how tiers interact with autonomy.

Seats and roles

Each member holds a seat as well as a role. The role decides what they can see, approve and change; the seat decides whether they can use the workspace at all. Both apply, so a seat never raises a role: a Max seat does not let an Operator approve above B2, beyond the cards they hold themselves. On Business, a Basic, Pro or Max seat gives its holder every capability below, Signals included: the seats differ only in the AI credits they include. On an earlier plan, the seat also decides what Hive does for its holder:

The Approver seat

An Approver seat is for people who only sign off what is sent to them, such as a partner who approves payments or client letters. It is sold only on earlier plans: there it costs £5 a month billed annually (£6 monthly), adds no credits to the pool, and a workspace can hold up to 2 for each Pro or Max seat. On Business, choose a Basic seat for someone who uses Hive only now and then. When a workspace on Starter or Team moves to Business, each Approver seat becomes a Basic seat: its holder keeps their access, and can then use everything in Hive with a Basic seat’s own AI credits. See Approver seats become Basic seats.
  • What they can do. Open the approvals routed to them, in their Inbox and on a workflow’s Approval step that names them, and approve, deny or undo them within their role’s tier. They can ask Hive 10 questions a calendar month about items routed to them, in the app; each is a short answer on an Efficient model, paid from the pool, and cannot be asked while the pool is empty.
  • What they cannot do. Connect accounts, build or run agents and workflows, publish links or forms, connect AI clients, ask Hive anything else in the app, Slack or Teams, use quick answers, or open the Library, Business Brain, search and chats. Hive refuses any of these; an Owner or Admin can give them a Pro seat instead.
  • Their pages. Hive opens only their own pages: Approvals, with the approval cards sent to them and a question about each, and under Just decided the cards they have just decided, with Undo on their own decision while it can be undone; Inbox, with the items addressed to them; and My usage, with the questions they have left this month. Any other address opens Approvals.
  • Signals. Approvers have no connected accounts, so no Signals proposals come to them: only the member who holds a signal’s source decides it.
  • Owners and Admins can hold an Approver seat. They also keep Billing and Members beside their own pages, as an Owner or Admin without a seat does, and their role still decides which approvals they can give.
Changing a member from a Pro or Max seat to an Approver seat asks you to confirm first. See Moving someone to an Approver seat.

A member without a seat

A member can be left without a seat: an Owner or Admin moved their seat to someone else, seats were removed and theirs was suspended over the plan’s limit, or they joined while no seat was free for them (see Team and workspace). The Members page then shows them as No seat, or Suspended. Whatever their role, a member without an active seat can do nothing in the workspace: no viewing, approving, Ask, connected accounts, building or AI clients, and no work runs as them, until an Owner or Admin gives them a seat. Hive shows them one screen saying they need a seat, naming the workspace and saying its Owners and Admins have been told, with Check again, Switch workspace and Sign out, and every request they make, from the app or an AI client, is refused with “You need a seat to use this workspace. An owner or admin can give you one in Settings → Members.” A seat suspended over the plan’s limit is refused the same way. An Owner or Admin without a seat keeps what they need to put it right: Settings → Billing, to buy seats, change the plan, pay an invoice or answer a billing notice (their billing notices are listed first there, under Billing notices, because they cannot open the Inbox); Members, to invite people, give out seats (their own included), and remove a member or revoke an invitation, which can free a seat (they cannot change anyone’s role until they hold a seat); and the kill switch. Hive opens Billing or Members for them instead of the screen above. If a workflow run is waiting for approval to take more than 50 agent steps and no Owner or Admin holds a seat, any Owner or Admin can approve or decline it under Billing notices in Settings → Billing, because it is a spending decision. Hive staff who open a workspace to give support hold no seat in it and are not refused. On a complimentary workspace, every member is given a seat automatically when they join (see Seats). What happens to a member’s work when they lose their seat is described in Team and workspace.

Signals and the Max seat

Signals follow the seat a member actually holds, never their role. On Business, and during the trial, every seat includes Signals on the holder’s own accounts, which use their own AI credits. On an earlier plan, Signals come only with a Max seat: a member on a Pro seat sees on the Signals page that Signals on your own accounts come with a Max seat, and is offered no Act on this, and AI clients and the API are told “Signals come with a Max seat. An owner or admin can change your seat in Settings → Members.” Owners and Admins choose each member’s seat when they invite them and can change it later. See Team and workspace and Billing and plans.

Billing

  • Owners and Admins see and manage everything in Settings → Billing (the plan, seats, add-ons, Usage and spend limits with each member’s top-up limit, offers and invoices), Settings → Usage (the workspace’s usage) and Settings → Members (who holds which seat). They decide members’ requests for a higher limit in the Inbox, never their own: they raise their own top-up limit in Usage and spend limits. On an earlier plan, Billing also has credit top-ups, and Settings → Usage member caps and spend controls. Billing notices, such as a trial ending or a failed payment, always reach them, by email and in the app; an Owner or Admin without a seat finds them under Billing notices at the top of Settings → Billing.
  • Only an Owner can cancel the subscription. An Owner or Admin can reactivate it before it ends.
  • Other members who open Settings → Billing see only the workspace’s plan and its status, and their own seat (on Business, with its AI credits: “Your seat: Max, £60 of AI credits a month.”), with “Plans, payment and invoices are restricted to workspace owners and admins. Ask one of them to change the plan.” Every member can see their own credits, extra usage, workflow runs and limits in Settings → My usage, and ask for a higher limit there.
  • People make billing changes, not AI clients. An AI client connected over MCP can read the billing details its member can see, but cannot change plans, seats, payments, usage controls or top-up limits, or decide usage requests.

Signals from members’ own accounts

Role is not the only check on signals. A signal read through a member’s own connected account is visible to, and can be acted on, snoozed, dismissed, muted and approved by, only the member who holds that account, whatever their role. Owners and Admins cannot see other members’ signals, decisions or matters, from business tools such as Stripe, Xero or HubSpot or from mail and files, and the Signals page has no view of everyone’s. A signal no member’s account produced belongs to nobody, so nobody sees it, the Owner included. The same goes for each member’s Business Brain and learned behaviours. Creating or lifting a workspace-wide type mute needs the Owner or Admin role. See Who can see a signal.

Department scope

Owners and Admins always see every department, though never another member’s signals, decisions or matters (see above). Hive’s role model also has department scope for Department leads and Operators (Finance, Sales, Marketing, Customer Success, People, IT & Security), but you can’t choose a member’s departments yet: invites don’t ask for them, and nobody can switch departments.

What a new member sees

While your workspace offers the Get Started guide, a Department lead or Operator finds a welcome on Settings → Account → Get Started (the sidebar’s Get started row links there until the checklist is finished). It names the workspace and their role, for example “You’re in Acme as Operator.”, says what the role does, and offers two questions to ask Hive. If they have nothing connected of their own, the Ask home shows them the Connect your work card once. A member listed with No role is told that an Owner or Admin can give them one. Owners and Admins get the setup steps instead. See Set up your workspace. A link to a page your role cannot open, such as Policy & autonomy for an Operator, opens Ask instead, and Hive says why once: “Policy & autonomy isn’t available to the Operator role. Ask an Owner or Admin for access.” Reloading the page does not repeat it.

Preview a role

On a workspace that shows sample data (no identity provider connected), Owners and Admins can preview the product as another role from Roles & access with Preview as …. A banner reads “Previewing as …” while the preview is on, and Exit preview returns you to your own view. Use it to check what a new Operator will actually see. Signed-in workspaces do not offer preview, because a local preview would not reflect real permissions.

Connectors and roles

Connectors use a two-step model:
  1. An Owner or Admin enables a provider for the workspace. Connecting it yourself as an admin enables it automatically.
  2. Any member with an active Basic, Pro or Max seat can then connect their own account for that provider (see Billing and plans); an Approver seat connects no accounts. Until a provider is enabled, members see “A workspace administrator must enable this provider before you can connect a personal account.”
Connected accounts belong to the person who connected them. Each member sees only their own connections in Integrations → Connectors, Owners and Admins included. Owners and Admins can see how many accounts of each app the workspace has connected in Settings → Products → Integrations, but not whose they are, nor anyone else’s credentials, scopes or actions. Each member sets the Read, Draft or Act level of their own accounts; Owners and Admins can cap a provider for everyone with a ceiling. See Accounts and autonomy.

Workflows and agents: per-item access

Workspace roles decide whether someone can run or build. Each workflow and agent also has its own sharing: Running a workflow, and creating a schedule for it, still requires the Operator role or above as well as Can run or Can edit. Deploying needs Can edit and no minimum role, but Hive refuses the deploy if the workflow contains an action your role is not allowed to take. Creating a new workflow needs the Operator role or above. Admins and Owners can read every workflow and agent in the workspace, even ones not shared with them, but cannot run or edit one they have not been given access to. See Share and reuse.

Rules that protect the workspace

  • No self-edit — you cannot change your own role.
  • No escalation — you cannot grant a role higher than your own.
  • Last Owner — the final Owner cannot be demoted or removed.
  • Fail closed — if Hive cannot confirm your role, you get the most restrictive view, not the most permissive.

Frequently asked

Keep Owners to the people accountable for the business — usually one or two. Owners and Admins share almost every capability, so most administrators should be Admins.
Operators can pause learned behaviours and work with the knowledge Hive holds. Activating a proposed behaviour so Hive uses it needs a Department lead, Admin or Owner. See Learned behaviours.
Not today. Hive uses the four fixed roles above, combined with department scope and per-item sharing.
Hive retired the read-only Analyst role in October 2026, when every member came to need a paid Pro or Max seat. Members who have it are removed from their workspaces with this release, and an invitation sent at the Analyst role can no longer be accepted. To bring someone back, invite them from Members at another role and give them a seat.

Team and workspace

Invite, change and remove members.

Review and approve

How approvals work in practice.

Safety and control

Policy, kill switch and spend caps.

Security overview

How Hive enforces access behind the scenes.