Skip to content

Approvals per customer

Each customer decides which of its agent's actions wait for its own yes, by action class and amount, inside what the product allows.

Each Customer decides what its own agent asks before acting, by action class and amount. The Approval goes to the Customer's people, never to the Startup that sells the agent.

One rule shape

A rule is one action class and an optional amount in USD, the same shape as the Startup's own approvals. At or under the amount the agent acts; above it, the Action waits.

Action classFor a renewals agentA Customer's rule
priceA rent or concession the manager has not setEvery one
sendA message to every resident of a building at onceEvery one
spendA fee paid for the Customer, such as a screening reportAbove $50
signA renewal Agreement signed in the Customer's nameEvery one
publishA listing on the Customer's own siteNever asks

The rules live on the Customer's Mandate for its agent. Mandate.authorize sets them, with the Limit, the channels and the expiry, and the Customer changes them in its Portal.

Inside what the product allows

The product's Role sets the default rules and its Entitlements set the ceiling. A Customer's Mandate never widens a Permission past the product's own, so its agent never does more than the product sells.

Set byDecidesExample
The product's RoleThe default rules every new Customer starts withprice always asks
The Customer's MandateIts own rules, inside the product'sspend above $50 asks Marcus Hale
The legal floorActs reserved to a credentialed personA notarized signature waits for a notary

Who answers

The Customer names who answers each class. An Approval nobody answers by its deadline ends expired, and the Action it held ends canceled. Each answer is on the record beside the Action, by whom and when.

The Startup sees that an Approval was asked and how long it took, because those numbers judge the product. It never sees or answers the Customer's Approvals.