Skip to main content
Before you build your first workflow, check four things: that your role and your workspace’s product access let you build and run workflows, that you have a seat and AI steps are available, that the apps your steps use are connected with your own account, and that your workspace has credits to run on. This page covers each one, then ends with a checklist.

Who can do what

Three separate gates decide what you can do with a workflow:
  1. Product access — an Owner or Admin can limit Workflows to chosen members and groups with General access under Settings → Workflows, and limit schedules the same way under Settings → Scheduled, in its Whole workspace view. Every run is checked against it. If Workflows is not enabled for you, a run is refused with “This product is not enabled for your workspace membership.” See Workspace settings.
  2. Your workspace role — Owner, Admin, Department lead or Operator, and an active Basic, Pro or Max seat. See Roles and permissions.
  3. Your access to that workflow — a workflow is private to the member who created it. The owner has full control; anyone else needs a share of Can view, Can run or Can edit. See Share and reuse.
An unattended run only uses a version its owner deployed. If someone with Can edit deploys a new version, Connected app event triggers stop starting runs until the workflow owner reviews and redeploys it, and a saved schedule stops until the member who created it reviews the new version and turns the schedule back on.
Your role also limits which action steps you can add, save or deploy. Every action step in the workflow must be one your role is allowed to take. Hive checks this when you create, import, duplicate or save a workflow, save it as a template, and deploy it:
Admins and Owners can read every workflow in the workspace, but only read it. To edit, run or reshare a workflow someone else owns, they need a share from its owner like anyone else.

AI steps

Agent, AI condition, Parallel agents, Web search and Image steps use AI models and services that Hive provides. An agent step’s model picker offers Workspace default and, where the runtime can pin one, a single named model. Which models members may use is a workspace setting. On Settings → Models, an Owner or Admin chooses the workspace default model, which models are Allowed for workspace, and which members and groups may use each one. Hive checks every AI step against that policy when it runs, and refuses the step if its model is not allowed for the person the run belongs to. Other members see only a note that owners and admins manage this page. The builder tells you when the runtime cannot carry a step out. Anything true of the whole workspace is said once, in the builder’s next step and its setup checklist under Every step can run in this workspace — not repeated on each card: The checklist can also list Reading from apps isn’t switched on for this workspace or This runtime cannot file documents in the Library. What is true of one STEP stays on that step’s card: This tool can’t run in this workspace — remove it to deploy, Select connection, and — when your workspace does have a model and the step pins a different one — No AI model is available for this step. For that last one, switch the step to Workspace default. A deploy refusal names the problem too, for example “Web search is not available in this workspace. Remove this step to continue.” The runtime limits are not settings you or your admin can change: remove the step, or contact Hive support.

Seats and model costs

Building a workflow needs a Basic, Pro or Max seat. A member without a seat, or whose seat is suspended because the workspace has more members than seats, can do nothing in the workspace, and the workflows they own skip their scheduled and event-started runs until they have a seat again. See When someone loses their seat. AI calls in a workflow use credits like the rest of your Hive model use: on Business, the AI credits of the member the run is charged to (yours for a run you start, the workflow owner’s for a scheduled, app-event or public form run); on an earlier plan, the workspace’s shared pool. Test runs get no free credits: a test run calls models the way a run you start yourself does, and uses the same credits. Runs started another way can use different models. On Hive’s keys, a run started by a schedule or a Connected app event uses only Efficient or Balanced models, and a step pinned to a Frontier model is refused there even though it works in a test run. A public form run uses the form’s Model for visitors (Efficient unless you turn on Balanced), runs any dearer step on an Efficient model instead, and on an earlier plan draws on the workspace’s public budget (see Credits and models for form runs). None of these model limits apply while your organisation’s own model key is in use. On Business, Team and Enterprise, an Owner or Admin can store the organisation’s own OpenAI or Anthropic key in the Keys section of Settings → Workspace → Models. Members’ model work then runs on that key, and only on that provider’s models: a step pinned to a model from another provider is refused, never moved to a different model. On Business, model calls on your key use no AI credits; on an earlier plan, each still uses 1 credit from the pool. Web search and knowledge search always run on Hive’s own accounts and use credits as usual. If your provider refuses the key, the work stops and Owners and Admins are told; Hive never switches to its own key.

Connected apps are personal

Every connected-app account in Hive belongs to the member who connected it. A workflow step that uses an app always uses the account of the person the run belongs to — never a teammate’s, even for an Owner or Admin. So each teammate who runs a shared workflow needs their own account connected for every app its steps use, and a Read from an app step reads from their account, not the owner’s. Their choices apply only to their run and never change the shared workflow. A workflow started by a public form cannot read from apps at all. Keep the workflow owner and every schedule creator at Operator or above. A public form submission or connected-app event for a workflow whose owner is below Operator starts no run, and neither does a saved schedule whose creator is below Operator. See Schedules and forms and Share and reuse.

Enable an app for the workspace first

An Owner or Admin enables an app for the workspace by connecting it themselves in Integrations → Connectors; the first connection enables it. After that, every member can connect their own account. Until then, a member who tries to connect sees “A workspace administrator must enable this provider before you can connect a personal account.” Disconnecting the admin’s account does not disable the app again. See Connect an app and Enabling a provider for members.

Connect an app without leaving the builder

You do not have to go to Integrations first. When a step needs an app you have not connected, its Connection field says “No Outlook account connected yet” (with the app’s name) and offers Connect Outlook. That opens the app’s sign-in while your workflow stays open, and once you have signed in the new account appears in the field. If you have accounts but none is chosen, the field asks you to “Choose which Outlook account this step uses”. An app that needs more details before sign-in, such as a region, opens Integrations already searched for it instead. The template setup guide works the same way, and so does Connect an app on the Describe tab, except that there Integrations opens in a new tab so your description stays as you left it (see Connect an app from Describe).

Account levels and write steps

Each connected account has a level. It decides what Hive does with that account in Ask and in Signals, and what a workflow’s write step does with it: New accounts start on Act. You set the level of your own accounts in Integrations → Connectors, whatever your role, and nobody else can change it, an Admin included. An Owner or Admin can also cap a provider at Draft or Read with a workspace ceiling; like the level, it holds a workflow’s action steps too. A connected-app step that writes — sending, creating or updating something in the app — runs from the runner’s own account and follows its level: on Act it runs, on Draft it waits for approval, and on Read it takes no action. The account picker for a write step lists all of your accounts for that app, Read ones included, so pick one on Draft or Act. On Act, what can still make a step wait for approval is where it sends: see What agents and workflows do by themselves. A workflow started from a Public form runs on the owner’s accounts.

Production writes and approval

In a test run nothing is sent and no approval is requested — Past runs shows what would have been sent. A test does check recipients: a send a production run would refuse, such as to a Slack channel the connection cannot see, fails the test step with the reason (see Test runs check recipients). In a production run, a connected-app write on an Act account is carried out by itself (on Draft it waits as an approval card, and on Read it is not run), unless where it sends came from a public form, an app event, an app’s records, an AI step or a web search: then it waits as an approval card in Review decision on the Signals page of the person the run runs as (see When an action waits for approval). To have a person sign off on every run, add an Approval step before it; the run then waits for an approver’s decision in Inbox → Needs you. Your workspace’s safety rails still apply: the kill switch, the hourly action limit, the spend caps and the recipient check (an email can go to any valid address, a Slack direct message only to a workspace member, a Slack post only to a channel the connection can see). A write one of them stops is recorded on the step as not sent, with the reason. A Public form run holds a send to an address a visitor typed, except an acknowledgement email whose other parts are typed into the step or come from that same form (see Who an email step may send to). See Test and deploy.

Credits and costs

Workflow runs use AI credits the way Ask and agents do: on Business, the credits of the member the run is charged to; on an earlier plan, the workspace’s shared pool. On Business, every live run also counts as one of your workflow runs: each seat includes 2,500 a month, and the execution add-on adds more for the workspace.
  • Every run uses credits for its AI steps — test runs from the canvas as well as production runs, however they start: manually, from a schedule, a form or an app event. Steps that only carry out actions use none.
  • A workflow can have a monthly credit limit. On Business it has none unless you set one; on earlier plans, a workflow without its own limit gets the plan default: 2,000 credits a month on Starter and Team, and 10,000 on Business and Enterprise. Set a Monthly credit limit, a Per-run credit limit and Runs per hour on the workflow’s Settings tab, under Limits. See Credit limits.
  • A large run asks first. A run Hive estimates at more than £5 (500 credits on an earlier plan) waits for you to confirm it.
  • When the credits run out (on Business, the credits of the member the run is charged to; on an earlier plan, the pool), the AI steps of a run you start are refused. Scheduled runs and runs started by a connected app event wait for credits instead, for up to 72 hours. See Waiting for credits.
On Business there is no plan limit on active workflows, hourly schedules or connected app events beyond your workflow runs. An earlier plan also sets how many workflows can be active (5 on Starter; no fixed limit on Team), how many hourly schedules the workspace can have (2 or 50), and whether connected app events can start runs (Team, up to 20,000 runs a month). See the limits reference. Two other limits refuse runs. While the kill switch is on, every run is refused, tests included. A run you start shows “Automation is halted for this workspace. Release the kill switch to run workflows.”; a scheduled run or public form submission is recorded as a failed run with “Automation is halted for this workspace by the kill switch”. And a Connected app event trigger starts at most 60 runs of a workflow an hour; later events in that hour do not run it. The Runs recorded chip beside the Workflows tabs counts the runs recorded on the workflows you can see, for example Runs recorded · 48. It is hidden on All workflows, which leads with how many of your workflows are live instead, and while a workflow is open. Owners and Admins see the workspace’s credits and usage under Settings → Usage. Costs are shown in GBP, at 1p a credit. Past runs shows the cost of each run and each step, and each row on All workflows gives the workflow’s model cost across the runs you can see since 12 October 2026, test and failed runs included. See Runs and errors.

Checklist

Some of these settings are visible only to Owners and Admins: product access under Settings, allowed models, seats and the workspace’s credits. If you are an Operator or Department lead, ask an Owner or Admin to confirm them for you.
  • Your role is Operator or above (needed to create, test and run).
  • Workflows is enabled for you under Settings → Workflows, and schedules under Settings → Scheduled (Whole workspace) if you will use them.
  • You have a Basic, Pro or Max seat, and the models your AI steps use are allowed for you on Settings → Models.
  • An Owner or Admin has connected each app your workflow uses, so it is enabled for the workspace.
  • You have connected your own account for each of those apps.
  • For steps that write to an app, you have your own account for that app at any level.
  • The setup checklist under the builder’s next step shows Every step can run in this workspace as done, and no step card shows a warning.
  • Teammates who will run the workflow have a Can run share, the Operator role or above, product access and their own connected accounts.
  • Your workspace has credits left this month — remember that test runs use credits too.
Once you are building, the builder keeps this list for you: the next step in its header counts what is still missing, and its setup checklist shows each item with Fix beside it.

Next: build your first workflow

Build a workflow step by step, test it, read the run and deploy it.

Roles and permissions

The five workspace roles and what each can do.

Accounts and autonomy

Read, Draft and Act, and who owns each connection.

Share and reuse

Can view, Can run and Can edit, and running with your own accounts.

Billing and plans

Plans, seats, credits and top-ups.