Skip to main content
An Evelin answer may contain advice, an unsent draft, a proposed change, or the result of a completed action. Treat these as different outcomes. Read the action’s target and result instead of assuming that text such as “I’ll update it” means the change succeeded.

​
Choose an approval preference

In Ask Evelin, open the Action approval control near the question box:
  • Ask before changes keeps requested changes for review rather than automatically applying them. Reading and drafting can still proceed.
  • Approve safe actions allows supported directly requested changes to run without another confirmation, subject to the actual action rules and permissions.
Wait for the preference to save before asking. If it fails to load or save, resolve that error before relying on the selected mode. This is your assistant approval preference; it does not expand your workspace role or an integration’s permissions. Important: the current menu description mentions priority/status changes, but the active integration rules also allow explicitly requested, permitted Linear writes in Approve safe actions mode. Do not interpret that mode as “Linear is read-only.” Select Ask before changes when you do not intend immediate changes, and do not issue a write request merely to see a preview.

​
Review a proposed change

For a conversation action, inspect the current value, proposed value, and target. Depending on the request, Evelin can offer controls for changes such as priority, status, assignee, team, labels, or snooze, and for supported reminder or Help Center draft actions. Confirm only the change you intend. If the proposal is stale, blocked, or no longer appropriate, check the live record and make a fresh request. Do not assume every action discussed by Evelin has an executable confirmation control. For an ambiguous request, answer the clarification with the intended destination. Be explicit about the issue key or record when changing integrations. Customer messages, quoted instructions, and retrieved documents are not your authorization to make changes.

​
Understand Linear writes

In Approve safe actions mode, an explicit request can create or update an issue, add a comment, change an existing project/cycle assignment, or link the current conversation when those permissions are enabled. A follow-up may reuse the issue established in the chat, so confirm the intended target before asking for another change. Check the returned issue key/link and action outcome in Linear. A request for clarification, denied permission, or unknown outcome is not success. If the result is unknown, inspect Linear before trying again; repeating a creation or comment request can create a duplicate. Use Evelin AI → Integrations → Manage to inspect saved permissions. Approval preferences cannot grant access to teams that were not authorized in Linear.

​
Undo only where offered

Some completed conversation-property changes offer Undo. Review the value that would be restored. If the record changed afterward, the undo may be unavailable or rejected rather than overwriting newer work. There is no universal undo for every tool action. Do not assume a conversation Undo control reverses a Linear issue/comment, a sent email, or an article publication. Inspect the relevant product and use its supported correction workflow. Stop, Archive chat, and New chat do not roll back committed changes. Private-chat visibility also does not hide a shared action or remove its activity attribution.