Safety And Approvals

Alfrada includes approval flows because some actions should never happen silently.

Common Approval Moments

• enabling additional tools
• approving sensitive outbound actions
• confirming image-reference sharing
• answering high-leverage clarification questions

Why This Exists

Approvals protect both quality and trust. They keep the system from taking sensitive actions or expanding scope without your knowledge.

How To Use Them Well

• read the approval request carefully
• approve only what is needed for the current task
• use "always allow" sparingly and only when you understand the implications
• treat approvals as a quality control checkpoint, not a nuisance

Prompting With Safety In Mind

If a workflow may trigger sensitive actions, say your boundaries up front.

Boundary-setting prompt

You may research broadly, but do not send messages, connect accounts, or take irreversible actions without asking me first. If a tool needs approval, explain why before requesting it.

Clear boundaries reduce unnecessary interruptions and make approvals easier to evaluate.