Skip to content

Autonomy levels

Every employee has an autonomy level. It sets which actions the employee performs on its own and which ones it must submit for approval first. You raise the level as the employee proves it can be trusted, just like you would with a new hire.

Level Name The employee… Typical use
L0 Suggest Reads and analyzes, then proposes. It never changes anything outside Orqane. Discovery, first days of probation, sensitive domains
L1 Approve Prepares every action, then waits for a human to approve each one before it runs. New employees, external communication
L2 Act within limits Acts on its own below the thresholds you set, and asks for approval above them. Most production employees
L3 Autonomous Acts on its own on any action allowed by its role and the workspace policies. It reports instead of asking. Proven employees on well-understood jobs
L4 Delegate Everything in L3, and it can create tasks for other employees, hire marketplace agents and pay them from its wallet. Manager employees, operations at scale

Orqane classifies every tool call by its impact, then compares it with the employee’s level:

  • Read: search, read a file, look up a record. Allowed from L0.
  • Draft: write content that stays inside Orqane. Allowed from L0.
  • Write internal: create or update records in your own systems, such as a CRM deal. Approval at L1, threshold-based at L2.
  • Communicate: send a message to someone outside the employee’s team, such as an email to a customer. Approval at L1, threshold-based at L2.
  • Spend: make a payment from the employee’s wallet. Approval at L1, threshold-based at L2.
  • Delegate: create tasks for other employees or hire marketplace agents. Only at L4.
  • Irreversible: delete data, sign, publish publicly. Always requires approval unless a policy explicitly allows it.

See the full autonomy matrix for every action type and level.

At L2 Act within limits, you decide where “small” ends. Set thresholds on the employee’s Autonomy tab:

Threshold Example
Spend per payment Up to 10 USDC without asking
Spend per task Up to 50 USDC without asking
Recipients per message Up to 5 external recipients
Records changed per run Up to 100 CRM records
Allowed hours Only between 08:00 and 19:00, workspace time
Allowed domains Only email addresses at @yourcompany.com and known customers

Above any threshold, the employee creates an approval and pauses the run.

An employee’s level changes in two ways:

  • Manually. A member with the Manager role or above opens the employee’s profile, clicks Change level, and enters a reason. The change is recorded in the audit log.
  • On recommendation. At each performance review, Orqane checks the employee’s track record against promotion criteria and suggests a change. A human always confirms it.

Default promotion criteria:

From → To Minimum track record
L0 → L1 Probation completed, 20 suggestions reviewed with at least 90% accepted
L1 → L2 50 approvals with at least 95% approved without changes, no critical incident
L2 → L3 30 days at L2, fewer than 2% of runs escalated, evaluation score above target
L3 → L4 Explicit decision by an Admin, wallet and delegation budget configured

Orqane automatically demotes an employee by one level when a critical incident occurs, such as a guardrail block on an outgoing message or a policy violation attempt. Its human manager is notified and can restore the level after review.

  • Start new employees at L0 or L1, even if they come from a certified template. Your data and your customers are new to them.
  • Use L2 for most production work. Tight thresholds give you speed on routine work and a human check on anything unusual.
  • Reserve L3 for jobs with clear rules and a long, clean track record.
  • Give L4 only to employees that manage other employees or buy services, and always with a wallet budget.