RoyakDocsroyak.appReport a problemSign inGet started free

Standing approvals

3 min readUpdated 2 Nov 2026

A standing approval lets named employees repeat one action to one destination, with fixed values and caps, without asking each time. Everything else still asks you.

Before you begin
  • You are the owner.
  • The app is connected and the employees already have Read and write access to it.
On this page

When to use one#

Use a standing approval for a write you would approve every time, such as Daniel Novak creating issues in one Linear team. It is narrow on purpose: one action, one connection, one destination, the employees you name and the values you fix. A request that doesn’t fit it exactly still comes to your Inbox.

Create one#

Open the connection in Connections and select New standing approval under Standing approvals. Or, under a request in the Inbox, select Allow again without asking…: the action, connection, destination and employee are filled in, and your decision on that request is unchanged.

  1. 1

    Name it

    Under Name, say what it is for.

  2. 2

    Pick the action and where it goes

    Choose the Action (writes only), the Connection and the Destination.

  3. 3

    Choose the employees

    Only employees who already have access to that connection can be named.

  4. 4

    Fix values

    Add a fixed value for anything every run must carry, such as the sender. A request with any other value asks you.

  5. 5

    Set the caps

    At most, in all, At most an hour, and how much it may spend: At most (credits) while your plan’s credits pay, else At most (USD).

  6. 6

    Set the sample and expiry

    Sample size is the first 10–20 runs. Expires is in 1, 7, 30 or 90 days. Then Create standing approval.

You can also give one from a table’s Sends column, for its batches.

The sample#

A new standing approval first sends its sample (Sending its sample). Then it stops: Sample sent · confirm it. Nothing more goes out until you check those results and select Confirm sample. After that it is Active until it is used up, expires or you revoke it.

TipCheck the sample in the app itself, not only in Royak: it is real work that already went out.

What it never does#

  • It grants no access. The employees must already be allowed to write to the app.
  • It never covers a request from a task that read content you didn’t write.
  • It can’t be edited once created. Revoke it and create a new one.

It pauses itself if too many recent sends go wrong, such as refusals, unknown outcomes, bounces or unsubscribes. The card says why: check them, then resume.

Pause, resume or revoke#

Each card on the connection shows its phase, who may use it, its fixed values, what it has used In all, An hour and in Spend, and its outcomes, with Pause, Resume and Revoke. A pause or revoke stops the next send at once. Ended ones are listed under Ended as revoked, expired or used up.

CarefulRevoking is final. A revoked standing approval can’t be turned back on; create a new one instead.

Every request it decides is recorded in Settings › Activity as decided by the standing approval, with how many of its runs are used.

Questions#

Does a standing approval let an employee use a new app?

No. Access comes only from the connection’s Who can use it list. A standing approval only skips the question for writes they can already make.

What happens when it is used up or expires?

The next request comes to your Inbox as usual. Create a new standing approval if you still want one.

Can I widen it later?

No. It can’t be edited. Revoke it and create a new one with the caps and values you want.

Who sees what it sent?

Every member can read Settings › Activity, which lists each decision it made.

ControlApprovalsNothing your employees write to a connected app happens until you approve it. Each request shows the exact action, where it goes and what it costs, and it is sent once, exactly as shown.ConnectionsRead, or Read and writeFor every app, each employee has one of three levels: None, Read, or Read and write. Reads run without asking; every write still asks you.AutomationTablesTables hold lists, such as leads or accounts. A column can be filled by an employee or an app for every row in one batch, within a budget you set, and a send column can message each row once you approve.ControlHistory and auditRoyak keeps a record of what happened: every decision, every step a task took and what it cost. Records can’t be edited, and they come from what was stored, not from what an employee says.
Was this page helpful?Report a problem with this page