Separate a proposal from an action
Preparing an email is not sending it. Writing a page is not publishing it. Make the distinction visible and keep the approval step easy to understand.
Give a clear brief
Explain the intended result, relevant constraints and what the assistant must not assume. For example: prepare a friendly reply, do not confirm a price, and ask for the missing deadline.
Check the details that matter
A polished sentence can still contain a wrong fact. Before an external action, review names, commitments, amounts and context. Keep the responsibility for the final choice clear.
Expand deliberately
Start with drafts. Once the workflow is understood, decide which connections and permissions are appropriate. More autonomy is a choice to make for each use case, not a default setting.