Tabulic

Approval rules

Which writes apply at once and which wait for the owner, per agent and per app.

An approval rule is a per-actor setting, for one kind of write, of whether it applies at once or waits as a pending changeset. Each agent and app has its own set in each workspace, plus a bulk threshold.

Kinds of write

KindWhat it coversAgent defaultApp default
insertadding rows, up to the thresholdappliesapplies
updatechanging rows, up to the thresholdappliesapplies
deletedeleting rows, up to the thresholdwaitsapplies
bulk-insertadding more rows than the threshold in one writeappliesapplies
bulk-updatechanging more rows than the threshold in one writewaitsapplies
bulk-deletedeleting more rows than the threshold in one writewaitsapplies
createa table or columnapplies (always, for now)n/a
renamea table or columnapplies (always, for now)n/a
dropa table or columnwaitsn/a
change-typea column’s typewaitsn/a

The bulk threshold is 10 rows unless the owner changes it. It counts rows touched by one write; fifty single-row writes are fifty small ones.

Apps never change the schema, so only the row kinds apply to them. Their writes apply by default because a person clicking in an app can’t wait for an approval.

How rules are checked

  • A rule is checked when the write is made. Changing a rule never touches writes already waiting or applied.
  • In a batch, if any write would wait, the whole batch waits.
  • A write that waits says which rule held it back (waits_for, reason) and links to where the owner reviews it (review_url).
  • The owner’s own writes never wait.

Who sets them

Only the owner, on the Agents screen (or an app’s Settings). An agent can read its own rules with describe_schema but never change them.

There is no floor: any kind may be set to apply at once, since every change can still be rolled back within the history window. On the hosted service, rules looser than the defaults need the paid plan; on the free plan a looser rule acts as the default.

For agents

When a write comes back with "status": "pending":

  1. Tell the person it is waiting for their approval, with the link if there is one.
  2. Don’t retry it. Retrying creates another pending changeset.
  3. Check later with changeset_status, or take it back with withdraw_pending.

On this page