What happens if I ignore an approval?

It expires after 7 days. The run is closed without doing the thing, nothing in your workspace or your site is changed, and you get an Inbox row telling you it expired. Silence is never treated as approval.

Which actions actually stop for approval?

Anything irreversible or hard to undo — publishing a page, sending mail, spending with a third party. Reading your own measurements does not stop, because nothing is changed by reading them.

Will a nightly failure fill my Inbox with rows?

No. The Inbox recognises a repeat of the same problem and updates the existing row with a count instead of adding a new one. Resolving the row closes it; if the same problem happens again it returns as a new row rather than silently reopening.

The pull request chip says checks are failing. Will Attensira fix it?

No, and that is deliberate. Attensira never pushes a second time to a branch it opened, so a red build or a merge conflict is surfaced on the row and left for a person. A failing chip is not a task we are quietly working on.

What is the difference between Done and Approve?

Approve authorises a specific pending action and it then runs. Done records that you handled something outside the product and queues nothing. Declining and dismissing are both stored rather than deleted, because what you turn down is a useful signal.

Can I read the Inbox from outside the dashboard?

Yes. It is exposed over the MCP server and the REST API, so an assistant or a script can answer “what needs me right now”. No tool or endpoint takes a workspace id — the credential you authenticate with names the workspace.

Inbox

The approval layer that makes an autonomous agent safe to run

The Inbox is where the agent stops. Anything irreversible waits for your explicit yes, an approval left unanswered for 7 days closes the run having changed nothing, and repeated failures collapse into one row with a count. “Does anything need me?” is one list.

Get Started Book A Demo

Two tabs
Needs you — nothing moves until you answer. In flight — approved and running.
Expiry, not drift
An unanswered approval expires after 7 days and the run closes changing nothing.
Repeats collapse
The same nightly failure is one row with a count, not fourteen rows.
Raised from evidence
Failed runs and missing connections come from calls that really failed.

By Karl-Gustav KallasmaaLast updated September 3, 2026Behaviour on this page is checked against docs.attensira.com

Why an inbox is the important screen

Every argument against letting an AI agent touch your website reduces to one question: what stops it doing something stupid? The Inbox is the answer, and it is the reason this is not a notifications page.

The agent does the work and stops only when it genuinely needs you. Every one of those stops lands here, so the state of the whole system is one list rather than a hunt through run transcripts. Work that is approved and running sits in a second tab, so you can see what is happening without being asked to do anything about it.

The bound worth reading twice: an approval that goes unanswered expires after 7 days. When it does, the run is closed without doing the thing, nothing is changed, and you get a row saying so. Silence is not consent, and a forgotten approval cannot quietly execute a fortnight later.

What ends up in “Needs you”

Five kinds of row, all of which used to be visible only inside a run's transcript.

Row	What it means
An approval	The agent tried to do something irreversible — publishing, sending mail, spending with a third party — and stopped. Open the row to approve or reject that exact action.
Blocked	It tried and could not proceed: a site refused us, a credential is missing, a file it has no write access to. It files what it attempted and what it needs.
A decision that is yours	Several courses of action are defensible, and picking one is your call rather than a guess made on your behalf.
A missing connection	A tool could not run because a plugin is not connected, was revoked, or lacks the permission the action needs.
A failed automation run	A scheduled run ended in failure. A chat that fails is failing in front of you; a 3am run is not.

What the agent may and may not raise

The agent can file exactly two of those itself: something it is blocked on, and a decision that is yours. Both require it to say what it actually tried.

It cannot file the other three. A missing connection, a failed run and an expired approval are raised from evidence — a call that really failed, a run that really died, a deadline that really passed. That distinction is what keeps the list a set of facts rather than a set of opinions, and it is why a full Inbox means something.

Raising a row costs no credits and changes nothing in your workspace, so the agent is never discouraged from telling you it is stuck.

Repeats become a count, and a count is the useful part

An automation that hits the same wall every night does not produce a row per night. The Inbox recognises a repeat of the same problem and updates the existing row with how many times it has now come up.

That number is the signal. “14 times” means the problem has been there for two weeks and nobody has acted on it — a materially different fact from the same row appearing for the first time this morning. Resolving a row closes that chapter; if the problem returns it comes back as a new row rather than silently reopening one you had already ticked off.

Done is deliberately not called Approve — nothing is queued to run when you press it. The work happened outside the product and you are recording that it is handled.
Declining and dismissing are recorded rather than deleted. What you turn down is as useful a signal as what you accept.
Rows can be snoozed when the answer is “not today”.

The pull request chip

A row whose work ended in a GitHub pull request carries a PR chip: the pull request number, linked, plus its current state read from GitHub rather than guessed by us. The chip is how you tell “the agent opened something” from “the agent opened something and it is stuck”.

Chip	What it means
Open	Waiting for review. Checks have not failed
Open · checks failing	Your CI went red on our branch. It is yours to fix — Attensira does not push again
Merged	It landed. The finding is resolved
Closed	It was closed without merging

It is not only a screen

Everything above is available through the MCP server and the REST API as well, so “what needs me right now” is answerable from wherever you already work — your editor, your assistant, a cron job — and not only from the dashboard.

That matters for the same reason the Inbox itself matters. An approval queue nobody sees is a queue that expires, and an expired approval is work that did not happen.

What a row actually looks like

Three rows from an ordinary week: one waiting on a person, one repeat with a count, and one that already went to code.

Needs you · Approval · Publish updated pricing FAQ copy — expires in 5 days

Needs you · Missing connection · Plugin revoked; the tool call failed · seen 14 times

In flight · Pull request #412 · Open · checks failing — yours to fix, we do not push again

Nothing on that list is the agent's opinion about what it might have done. The approval is a real pending action, the repeat count comes from calls that really failed, and the pull request state is read from GitHub.

What it does not do

The Inbox is deliberately narrow. It is a control surface, not a project tracker.

It does not chase you. An approval left for 7 days expires and the run closes without doing the thing — the product will not decide on your behalf that silence meant yes.
It does not fix a failing pull request. A red build or a merge conflict is surfaced and left for a person, because Attensira never pushes a second time to a branch it opened.
The agent cannot raise a missing connection, a failed run or an expired approval itself. Those come from evidence only.
Pressing Done queues nothing. It records that you handled something outside the product.
It is not a task manager for your team. There are no assignees, sprints or due dates.

Which plans include it

Included on every plan — Starter $129/mo, Growth $349/mo, Business $699/mo.

The Inbox is on every plan, and raising a row costs no credits. It is exposed over MCP and the REST API on every plan too.

Plan facts on this page are read from the same ladder that prices /pricing, so they cannot drift from what you are actually charged.

Read further

Documentation

Inbox — the two tabs, the 7-day expiry, and what the agent may raise

Documentation

GitHub — where the pull request chip states come from

The agent

What stops here, and why it stopped.

Automations

A 3am run that fails is not failing in front of you — it comes here.

Plugins

Grants are revocable, and a revoked grant shows up as a missing connection.

Pricing

Three plans, no free tier and no trial. Approvals cost nothing on all of them.

FAQ

Questions people actually ask

Answers here match the product documentation. Where the product cannot do something, this says so.

Still deciding? Compare plans or talk to us.

The approval layer that makes an autonomous agent safe to run

Two tabs

Expiry, not drift

Repeats collapse

Raised from evidence

Why an inbox is the important screen

What ends up in “Needs you”

What the agent may and may not raise

Repeats become a count, and a count is the useful part

The pull request chip

It is not only a screen

What a row actually looks like

What it does not do

Which plans include it

Read further

Questions people actually ask

What happens if I ignore an approval?

Which actions actually stop for approval?

Will a nightly failure fill my Inbox with rows?

The pull request chip says checks are failing. Will Attensira fix it?

What is the difference between Done and Approve?

Can I read the Inbox from outside the dashboard?

Why an inbox is the important screen

What ends up in “Needs you”

What the agent may and may not raise

Repeats become a count, and a count is the useful part

The pull request chip

It is not only a screen

What a row actually looks like

What it does not do

Which plans include it

Read further

Questions people actually ask

What happens if I ignore an approval?

Which actions actually stop for approval?

Will a nightly failure fill my Inbox with rows?

The pull request chip says checks are failing. Will Attensira fix it?

What is the difference between Done and Approve?

Can I read the Inbox from outside the dashboard?