Skip to content
Hydra

Roles and approvals

Everyone in Hydra has one role. The role decides which screens a person sees and what the agent may do for them. On top of that, the agent asks before it writes: some writes need the person's own approval in the chat, and the riskiest ERP changes also need a manager.

The four roles

Role Who it is for What it adds
Member Most staff The chat, pictures, designs, documents and the integrations they connect with their own accounts.
Operator Engineers Terminal mode: real terminals with Claude and Codex on the server's projects.
Admin The people who run Hydra Terminal mode, the System area, managing people, reading the audit log, deciding ERP approvals, personal AI API keys.
Owner One or two people Everything. Only an owner can make or change another owner, and only an owner can use View as.

At Kestrel Freight, for example, Nora Vance is the owner, Dev Okafor is an admin who runs the server, Ilse Brandt is an operator who works in terminals, and Mai Linh, Sam Reyes and Tomas Ferreira are members.

A few rules always hold:

  • An admin can change anyone's role up to admin, never to owner, and cannot change an owner.
  • The last active owner cannot be demoted or disabled, so Hydra always has one.
  • A person's own chats, devices and designs stay theirs, whatever the role of the person looking.

People and their status

Open System → People to see everyone, their role and their status.

Status Meaning
Pending Signed in once, waiting for an admin. Sees only a waiting page.
Active Uses Hydra with their role.
Disabled Cannot sign in. Disabling someone also signs them out of every browser at once.

People from a pre-approved email domain start active. You can also add a person before their first sign-in, with the role they should have. Every role and status change is in the audit log.

Teams

Some integrations matter only to one group, such as finance or e-commerce. System → Teams gives a named group of people those extra integrations without changing their role.

Approval 1: you, in the chat

When the agent wants to do something that writes and cannot simply be undone (create or change an ERP document, edit a design someone else owns), it stops and shows a card in the chat: what it will do and to what. Nothing happens until you press Approve. Deny stops it.

  • Only the person who owns the chat can answer the card.
  • If nobody answers within a few minutes, the agent is told the write was not done, and it says so.
  • Writes that Hydra can measure and undo, such as filling cells in your own Google Sheet, run at once. They are still recorded as writes, and the answer tells you how to undo them.

Approval 2: a manager, for risky ERP changes

After your approval, every ERP write passes the change guard. It looks at what the change would do and picks one of four paths:

Path When What happens
Refused The document type grants access (users, roles, permissions, system settings), or the request is a delete Never done through chat.
Manager A bulk change of more than 5 documents; submitting a document that moves money or stock (invoices, payments, journal and stock entries, delivery notes); a sensitive field such as a price, discount, credit limit, tax id or bank detail; clearing a filled field; a number changed by more than half; many writes in a few minutes Queued for a manager.
AI check Several documents, an unusual document type, or a person's first write to a type An AI review decides: it runs, or it goes to a manager. If the review is unavailable, it goes to a manager.
Runs Everything else Done at once.

Admins can adjust these rules in System → Approvals.

The approval queue

A queued change waits in System → Approvals. Admins get an Inbox message for each one (and an email, when your server has mail set up), and can read the full impact before they decide: which documents, and each field before and after.

  • Approve runs the change with the requester's own ERP connection. A bulk change is counted again first, and stops if many more documents match than were approved.
  • Reject takes an optional note. The requester gets an Inbox message either way, and sees their requests under My requests.
  • Nobody can decide their own request, except an owner.
  • A request nobody decides is approved by itself after a few hours (4 by default), or, if an admin turned that off, it expires.

Every review, request, decision and result is in the audit log, with names and counts but never the field values.