flintspark Book a demo

Approval before irreversible actions

In flintspark, an approval is a signed, single-use grant for one exact irreversible action. By default Flint, flintspark's agent, cannot submit, send, pay or delete without one from a person. A workflow owner can switch on trust mode for one workflow, and that switch is logged.

  • CoversOne exact action: the step, the page, the element and a digest of the value
  • SignedBy the server's key. The browser side verifies it before it acts
  • Valid120 seconds by default, once
  • Never coversRelease, disposition or signing

What counts as irreversible?

Anything that cannot be undone: submitting, posting, sending, paying or deleting, payment forms, and pages that ask you to confirm before leaving.

Every action has a risk class. An action of unknown risk is treated as irreversible. The model can never lower a class, and the browser side applies its own check and acts on the higher of the two, so a server mistake cannot downgrade an action.

A sketch, not a screen from the product.

What does the approver see?

The exact action Flint wants to take, with the draft and a screenshot as evidence. The person can approve, reject or take over.

A rejection sends nothing. By default it fails that step, and the workflow can define another path. If nobody answers in time, the run expires and nothing is sent.

A sketch with an illustrative action, not a screen from the product.

Why are grants single-use?

So an approval cannot be replayed. A grant names the step, the kind of action, the site, the page, the target element, a digest of the value and, for a request, its method and address pattern. It holds no screen coordinates, so a re-plan that clicks the same element still matches. A re-plan that changes the target needs a new approval.

Only the server holds the signing key. The process that acts holds the public key and checks the signature, the match and a durable ledger of grants already used. The process that acts therefore cannot mint a grant.

  1. Minted

    When Flint is ready to act, after the approval.

  2. Checked

    Signature, exact action and ledger.

  3. Used once

    The ledger records it. A replay is refused.

  4. Expired

    After 120 seconds by default.

Can approvals be switched off?

Not switched off, switched to policy. A workflow owner can turn on trust mode for one workflow. Policy then issues the grants instead of asking a person each time.

The switch is off by default, applies to that workflow only, and is logged as a decision and an audit event. Each grant it issues is still signed and single-use, the browser side still verifies it, and every issue is audited. Learning a new skill cannot loosen a policy either.

Trust mode off (default)

  • A person answers each approval.
  • The grant is minted after the answer.
  • Signed, single-use, audited.

Trust mode on, one workflow

  • Policy issues the grant. The switch is logged.
  • The browser side still verifies it.
  • Signed, single-use, audited.
Release, disposition and signing still never run.

What is take over?

A person stops Flint mid-task and controls the browser directly. Use the Take over button on the run in the platform, or press Esc twice in Flint's browser window. Flint stops at the next action boundary, and the run continues only when the person presses Resume.

Some acts never run, in any mode. Release, disposition and signing are in a policy class called never_automate. Safety refuses them, and the run hands over with a Your turn request.

A sketch, not a screen from the product.

Questions about this page

How long does an approval last?

An approval stays valid for a configured period (72 hours by default). When Flint is ready to act, the server mints a grant that is valid for 120 seconds by default and can be used once. If nobody answers in time, the run expires and nothing is sent.

What happens when a person rejects an action?

Nothing is sent. By default a rejection fails that step with a policy-denied result, and the workflow can define a different path for a rejection. The person can also take over and finish the task in the browser themselves.

Can Flint release a product or sign a record?

No. Release, disposition and signing belong to a policy class called never_automate. Safety refuses them in every mode, trust mode included, and the run hands over with a Your turn request so a person does it in their own system.

See Flint run

Bring one workflow you'd rather not do by hand. We'll show Flint learning one like it, and stopping before anything it can't undo.

We reply from hello@flintspark.ai.