Lanes
A change records its lane when it is filed. Read it as
lane on GET /v1/changes, served on webapp.attensira.com (not on api.attensira.com yet).
Levels
L0, L1 and L2 differ in the approval mode they set (see How levels relate to the approval mode): at each of them, a change waits for you. L5 ships the same way as L4 today.
Defaults. Every workspace starts every lane at L2, whether it is on a trial or a paid plan: nothing ships without your yes, unless you let a lane ship on its own. A lane nobody has set follows the default, so starting to pay does not raise it. A lane you raised keeps the level you chose.
What no level changes
These hold at every level, L5 included:- A change that cannot be undone waits for your yes. Sending an email, spending money, deleting a page: none of them ships when a window ends or on its own. See What cannot be undone.
- A claim waits for your yes. A change that says something about your business (a price, a promise, a competitor’s name, new wording) is never shipped by a level. The 48-hour window and shipping on its own apply to safe changes only. See the classes.
- What is refused stays refused. A change classed never is not made at any level, not even with your yes.
- Work inside the workspace goes ahead. Reading, researching and drafting leave nothing outside the workspace, so they run at every level.
- A project can be stricter, never looser. A project set to Ask first or Leave drafts holds every change for your yes, whatever its lanes say.
- Other limits still apply. Change caps, the site policies for work on other sites, and the outreach rules sit on top of the level. A level never overrides a site whose policy says a person presses submit.
A lane can run lower than you set it
A lane set to L4 or L5 runs at L3 for any playbook whose quality checks have not passed yet, and a page rewrite with little an answer engine could quote waits for your yes. Neither ever raises a level. The rules, the checks and theheld_reason sentence are in A lane can run lower than you set it and A page rewrite with little to quote waits for your yes.
Seeing and changing levels
The Autonomy settings page (/settings/autonomy) lists every lane with its level, the level it runs at now, and why, when that is lower.
- Lowering is applied at once, whoever asks: you, a teammate, an API key or an agent. Over the API it is
actwithlower_autonomy(POST /v1/actions). Over MCP it is the same:actwithlower_autonomyandpayload: {lane, steps}.configuretakes no autonomy kind. - Raising needs a signed-in person and a confirmation given for that exact lane and level, in the app. An API key, an agent or an assistant can ask (
POST /v1/autonomy/raise, MCPrequest_autonomy_raise), which files the request in your Inbox and changes nothing. That route is served onwebapp.attensira.com, so a key asks there;api.attensira.comdoes not serve it yet and answers404. The MCP server does not listrequest_autonomy_raiseyet, so an assistant cannot ask over MCP today. See Only a person raises a level.
GET /v1/autonomy, or get on attensira://{workspace}/autonomy over MCP. Every change of level is kept in the workspace’s settings history with who made it.
When agents ask for more
After 14 changes of one kind in a lane went out with nobody editing, undoing or withdrawing them, the agents propose one step up for that lane, never past L4. The proposal is a row in your Inbox. Accept it in the app to raise the lane, with the same confirmation as any raise; decline it and that step is not proposed again for 30 days. See When agents propose a raise.Related
- Changes: what a change goes through, the Weekly Ship, stopping, shipping now and undo.
- Approval modes: Ask, Draft and Act, the change classes and the draft check.