Approve an assistant action and have it run as you

When the assistant proposed editing an automation, renaming an asset or applying a label, approving it carried the action out under the permissions of whoever the proposal came from. If that person could not touch the row, your approval was refused, and the change showed up as theirs.

Approvals run as you

Approve a proposed edit or deletion of an automation, an asset rename or delete, or a label creation, and Chief runs it with your own access and records you as the person who made the change. A project owner can now approve a teammate's proposal and have it go through.

Approve buttons you can act on

Action cards you are not allowed to accept still appear in the chat, without an Approve button. Some actions, like sending mail or changing a calendar event, land in the proposer's own account, so only that person sees the option to approve them.

New automations stay with their author

Creating an automation is the one action that keeps running as the person who proposed it. Every scheduled run afterwards acts as the automation's creator, so approving one does not hand your access to a prompt someone else wrote.

Open a chat with a pending action card and approve it to see the change reflected under your name.