Reviewing KAI's suggestions and controls
Understand a proposal, who may apply it, and when eligible actions can run under your autonomy settings.
Start with a proposal
KAI prepares a proposed change from the records and information available to it. At the default propose level, that change waits for an authorised person to review it. The model does not write directly into the business records.
Execution uses the same domain action and permission checks as the corresponding product workflow. A proposal is not a way around a role, module or plan requirement.
Check the autonomy setting
Eligible action tasks can progress beyond proposals through consecutive unchanged approvals or an owner-set level. Depending on the level and risk cap, an action can run within a threshold, run with a notification, or run with an audit trail. Medium-risk actions cannot reach the silent level; payments, refunds and other high-risk actions are excluded from this ladder.
Owners can pin a task to a level, including proposals, or turn autonomy off. A pinned level does not change automatically. Turning autonomy off makes eligible tasks wait as proposals; it does not erase their stored level. Re-enabling it can restore that level, so review the settings before switching it back on.
Open Settings → AI → Autonomy to inspect the controls available to your account. Automatic execution still uses the current user's permissions and the normal action checks. Read the execution trail to see what actually happened.
Review the facts before a change
Open the Suggestions screen or the suggestions shown in the assistant. Check what would change, the supporting facts, and any warning about live stock or prices. Money figures come from the product's calculations over recorded data.
Available proposal kinds include supported menu, purchase and operational changes. Who may apply a proposal follows that action's role and policy checks; an out-of-stock proposal can require a manager under the restaurant's settings. A remembered business note requires owner authority.
Expiry and repeated approvals
A waiting suggestion expires after 72 hours. An expired proposal does not apply; review the current records and request a fresh one if the action is still needed.
The application deduplicates execution of a draft. A repeated approval is not a request for a second copy of the business action. Check the result and its record before starting a new proposal.
When a proposal cannot run
AI must be configured and within its available allowance. Advanced proposal capabilities require the relevant plan entitlement, and each action can have additional module or role requirements.
If the product reports a refusal or failure, read the reason and correct that condition. Retrying cannot grant a missing permission or activate a provider. Rejecting a waiting suggestion closes it without applying it.