The Action Assistant's limits are not settings; they are the design.
- Drafts only. No proposal posts a document, sends a message, pays money or deletes anything. Each action ends at a draft created through the same machinery the equivalent screen uses — the Assistant is a new caller of the existing workflows, never a shortcut around them, and the approve/post separation of 1.5 still stands between every draft and the books.
- Your permissions, checked twice. Making a proposal requires the permission for that kind of action; confirming checks it again. A reminder proposal needs the dunning permission, an adjustment the inventory-adjustment permission, and so on. If your role lacks it, the action is not offered to you — hidden, as everywhere in this application, never greyed out.
- Your company only. A proposal acts in the company you are signed into — always, and only. A request that names a different company is rejected outright and the attempt is logged. There is no cross-company action, under any role.
- Confirmation is not optional. Every kind of proposal requires a person's confirmation before it executes. That is built into what a proposal is; it cannot be configured away.