Authority

What the agent is allowed to do, and where it must stop and ask.

Authority in SigmaPointPi
/settings/authority

Sigma holds tools. This page sets which ones, up to what value, and what always requires a person.

Authority is per business. An agent working in one business has no path to another, and the grants are independent.

Where everything sits

Northline Systems
Northline Systems
Single act
Single act
-hour allowance
-hour allowance
Two-person rule
Two-person rule
First payment
First payment
The grant
The grant

How to work this page

Decide what it may do unattended

Reading, searching, scheduling and navigating are safe. Anything that moves money or changes a record should be staged.

Set the value ceiling

Above it, everything stops for approval regardless of the action.

Keep payment execution out

The agent can prepare a payment. It should never be able to execute one, and by default it cannot.

Read the turn record

Every action the agent took, what it was asked, and what authority applied at the time.

On a phone

Authority on iPhone 15 Pro Max

Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.

Questions people actually ask

Can the agent be talked into something by a document?

Its authority narrows during a turn when retrieved document text enters context. The tool set shrinks, so a document cannot reach an action that was not already permitted.

What if I want it to do more?

Widen the grant deliberately here. It is a decision with a record rather than a setting that drifts.