Approving actions
An approval card is the final check before a sensitive action such as sending, deleting, purchasing, or changing the system.
Why Assistela asks
Reading a calendar or summarizing a document normally does not need the same confirmation as an action that affects the outside world or changes data. Before a sensitive step, Chat displays an approval card with the action, reason, consequence, and sometimes a time limit.
An approval is consent to one specifically described action. It is not blanket permission for all future tasks.
What to check before approving
Target
Is the recipient, website domain, file, account, device, or event correct?
Content
Are the text, amount, date, quantity, and scope exact?
Consequence
Will it send a message, delete data, run a command, or submit a form?
Need
Does the requested action match what you actually asked for?
Choose Approve only when every detail is right. Do Not Allow rejects the action so you can refine the request. A card may expire after a period and Assistela must request a fresh approval.
When not to approve
- the recipient, amount, domain, or file path is not stated exactly,
- the action uses a different account or device than expected,
- it would use a password, card, or one-time code outside the current task,
- it would delete more items than you reviewed,
- the consequence is unclear or does not match your instruction.
If uncertain, choose Do Not Allow. An expired approval does not send anything by itself. Asking for a new draft with exact details is safer.
A safe workflow
For sensitive work, use two phases: first “prepare and show me a draft,” then after review “perform exactly this draft.” For purchases, verify the domain, items, final total, address, and card. For email and messages, verify every recipient and attachment. Before deleting, ask for a list of all affected items.