Approve what your Talent does

Your Talent does not ask permission for everything, and it does not act unsupervised either. Actions fall into three postures, and knowing which is which stops both of the usual complaints: constant interruptions, and surprise.

Approval cards appear wherever you are working, in the web console and in your connected messaging channel. Every action leaves a receipt in Activity, approved or not.

Never asks

Safe, reversible work inside its own space. Your Talent does it and tells you what it found.

• Reading anything you connected. Searching email, pulling a CRM pipeline, opening a spreadsheet.
• Running code in its own sandbox to work something out.
• Keeping its own notes about you.
• Writing a private document that has no schedule on it.
• Creating, editing, running, or deleting one of your own Routines.

Asks once for this conversation

A recoverable write in one of your connected accounts. Updating a knowledge page, commenting on an issue, or adding a row to a database.

The card offers three answers: Approve, Decline, and Allow for this conversation. The third one covers the same action on the same account for the rest of that thread, so a long piece of work does not raise the same card twenty times.

A different action asks again. A different account asks again. A new conversation asks again. Grants die with the conversation, by design.

Asks every single time by default

Six kinds of work always ask, however many times you have said yes before.

1. Anything sent to a person. An email reply or a team-chat message.
2. Anything that books calendar time. Creating or moving a calendar event spends other people's hours, and deleting the event gives none of them back.
3. Anything that moves money. Invoices, payments, ad spend.
4. Anything that deletes. Any delete, archive, clear, or purge, on any connector.
5. Anything that changes who can reach your data. Sharing a drive file, adding a project member, or setting a secret.
6. Anything that arms a standing commitment. Putting a Routine on a schedule, so it keeps firing after you have walked away.

Custom connectors you registered yourself always ask too. So does proposing a fact into department memory, because the whole department reads it.

A worked example

You ask for a weekly client update: pull the CRM pipeline, draft the summary, email it to the client.

Reading the CRM: no card. Drafting the summary: no card. The email send: a card, showing exactly what will go out, to whom. Approve it and it goes. That is one decision on a job with a dozen steps.

Change the defaults

Open Settings and find the action policies. Each governed action can be set to:

• Ask, the default. You see exactly what will happen before it happens.
• Auto, run it without a card. It still leaves a receipt.
• Off, block it. Your Talent will tell you the setting stopped it.

If you run that same weekly update every Monday and you trust the draft, set the email send to Auto and the Routine completes without you. Set anything you never want it touching to Off.

What to check

"Your admin requires approval for this action." Your workspace is set so that action always asks. You can leave it on Ask, but you cannot set it to Auto.

A scheduled Routine finished without doing the last step. It parked on an approval and is waiting for you. Approve it from the bell, or set that eligible action to Auto if it runs every week.

Your Talent says it was stopped by a setting. That action is set to Off. Change it in Settings.

It keeps asking for something you approve constantly. Approving repeatedly never turns into permission. Only the switch in Settings does.