Approvals

Inspect evidence, destination, audience, and reversibility before allowing an action.

Current status: live for the approval queue’s defined scope. An approval is permission for the exact proposed action and version—not a blanket authorization for future work.

Check the source evidence, precise change, destination, recipients, timing, and rollback path. Approve only when all are clear. Request a factual correction when the draft is close; reject when the action is unauthorized, unsafe, misleading, or aimed at the wrong destination.

Leave an item pending when the restaurant needs more evidence. If the reviewed source changes, let the approval expire and review the new version. Website publication and Fleksa menu sync are separate owner actions; approving one does not approve the other. Public replies, outbound messages, publication, charges, refunds, deletion, and other irreversible effects require particular care.

If a Website draft approval returns after a reload, compare the exact proposal again. Choose Leave unchanged to close it without applying the draft. Choose Apply anyway or Finish approved change only when the shown version is still the one you intend to keep. These choices are saved, so the same recovered request cannot later take the opposite action.