What Brief can do on your behalf

People hold back from asking Brief to do things, and the reason is almost always the same one: you want to see it before it goes out. That is the right instinct, and the defaults already answer it.

Brief drafts automatically. Every action that sends a reply, a new email, an invite, or a chat message waits for your approval. You can loosen that, action by action, once you want to. Nothing about it is buried.

The controls are under Settings → Briefing & Actions, in the group named What Brief can do.

The three levels, and Recommended

There are three trust levels. Every action in an area follows the area's setting unless you pin the action to something else.

Recommended is the first choice on the control and is not a level at all. It clears the area's override, so every action falls back to its own default, which is what the table further down lists.

The five areas are Email, Calendar, Tasks, People, and Messaging. Open an area to see its actions and set one on its own. A single action set to Default follows whatever the area is on.

Where approvals appear

Anything waiting on you shows up on the Actions page, marked "Awaiting approval", with Approve and Dismiss on the card. The Actions tab in the navigation carries a badge while something is waiting, so you do not have to go looking.

Drafts are different. When Brief drafts a reply or an email, the draft lands in your email drafts folder, where you edit and send it yourself in the client you already use. Brief drafting for you and Brief sending for you are two separate actions with two separate settings.

Every action, and what it does by default

The shape of that table is the policy. Reading, drafting, filing, and your own task and contact records are automatic, because getting them wrong costs you an undo. Anything another person receives is not.

Loosening a single action

The common case is wanting one thing to stop asking. Brief creating calendar events without checking, say, while every send still waits for you.

Open the area, find the action, and set it to Automatic. Brief asks you to confirm first, with the reason stated plainly: setting it to Automatic "means Brief will do this without asking you, including sending on your behalf. You can change it back anytime." Confirm and it holds until you change it.

There is no floor. You can put a send on Automatic if that is what you want. The confirmation exists so that it is a decision rather than a stray click.

A note on messages Brief sends for you

When a message goes out on your behalf, the person receiving it generally wants to know. Not because it matters to the content, but because they are reading it for tone and they will spend real effort wondering if something is off.

Brief has no configurable attribution line today. If you want one, the practical approach is to write it into the instruction you give Brief, so agent-sent messages open by naming what sent them. It costs a line and saves the recipient the guesswork.