.svg)
Delegate drafting, questions and pre-launch checks to BrazeAI Operator, and review anything that changes settings, access or live content. Keep auto-approve off for those, because approved actions can't be undone through Operator. Operator can't launch anything that affects your users, so make that launch your real review point, and limit the personal data it sends to OpenAI.
Key Takeaways
- Delegate drafting, questions and pre-launch checks to Operator; review anything that changes settings, access or live content.
- Each proposed change appears as an action card, and approved actions can't be undone through Operator.
- Auto-approve is off by default and resets when you refresh, open a new tab or log out.
- Operator can't launch anything that affects your users, so the launch is your human checkpoint.
- Requests to OpenAI can include page content, and Braze states there's no automated redaction of personal data.
- Turn off View PII for Operator users, avoid user profile pages, and don't paste personal data into prompts.
What is BrazeAI Operator?
BrazeAI Operator is an AI-powered assistant built into the Braze dashboard. It drafts campaigns, Canvases, segments and content, answers questions, and helps with troubleshooting, and by default you review and approve each action it proposes.
Operator has the same dashboard access you do, and it fully inherits the permission profile of the logged-in user. If you can't do something in Braze, Operator can't either.
It also shows its working. Reasoning steps appear in collapsible sections labelled Reasoned, which is the quickest way to check how it reached a suggestion.
What should you delegate to BrazeAI Operator, and what should you review?
Sort tasks by what goes wrong if Operator is mistaken. The table is our recommended split, built on Operator's documented behaviour.
| Task | Delegate or review | Why |
|---|---|---|
| Answering questions and explaining features | Delegate | Nothing changes in your workspace |
| Drafting campaigns, Canvases, segments and content | Delegate, then review each card | Drafts are easy to inspect before anything goes live |
| Pre-launch checks for spelling, tone, stray code or unrendered Liquid | Delegate the check | Operator finds issues; a person decides what to fix |
| Edits to active content | Review every card | Operator can prepare them, and approved changes can't be undone through it |
| Roles, permission sets and security settings | Review every card, auto-approve off | A mistake here changes who can do what |
| Permanent deletions | Operator prepares, you confirm | You must type the confirmation text yourself |
| Launching anything that affects users | Yours alone | Operator can't launch |
The pattern is simple. The more permanent or far-reaching the change, the closer a person should look at the card.
How do action cards and auto-approve work?
When Operator proposes a change, it summarises the plan, then shows each change as a separate action card. For changes to existing values, the card shows the previous and proposed values side by side.
Approve or decline each card. Approved actions run in Braze, declined ones don't, and approved actions can't be undone through Operator.
Auto-approve skips that step, so Operator's suggested actions run immediately. It's off by default, and it resets when you refresh the page, open a new tab or log out.
We'd keep it off whenever the page involves live content, access or settings. For a drafting session in a staging workspace, turning it on can save time, and the reset on refresh limits how long it stays on.
Operator can't approve its own actions or turn auto-approve on for you. For certain actions it always pauses for approval, even with auto-approve on.
What can't Operator do?
Braze has set deliberate boundaries. Operator can't launch anything that would affect your users, even though it can prepare a campaign or Canvas end to end, including edits to active content.
It also can't confirm a permanent deletion, since you have to type the confirmation text yourself. It can't complete external authentication flows or change billing or contract terms.
That makes the launch your built-in human checkpoint. Use Operator's own pre-launch checks to catch errors, then treat the launch as a decision a person makes with the draft in front of them.
Operator's reach is growing. Braze notes that coverage expands regularly, and recent release notes added Canvas editing, drag-and-drop design edits and dashboard navigation, so review your delegation rules when new capabilities arrive.
What data does Operator send to OpenAI?
Operator integrates with OpenAI. Each message or navigation event while Operator is open sends a separate request to OpenAI, with no standing connection or continuous data feed.
A request can include your prompt, results from Operator's tools, and content scraped from the active dashboard page, truncated to approximately 4,000 characters. Braze states there's no automated redaction of personal data in that pipeline.
Retention depends on your cluster. On most clusters OpenAI keeps the data for 30 days for abuse monitoring, with zero retention on the US-02 cluster used by health-data customers. Braze states the data isn't used to train OpenAI models, and that EU data routing isn't implemented for Operator.
Those facts belong in front of your security team before rollout. The absence of EU routing matters most if your data policy depends on where processing happens.
How do you limit personal data exposure?
Braze lists practical steps, and they work best as a written team rule. Apply these before anyone uses Operator on a production workspace.
- Grant the Use BrazeAI Operator permission only to users who need it.
- Turn off the View PII permission for Operator users, so Operator can't access personal data either.
- Don't open Operator on a user profile page, because page content is sent with each request.
- Don't type or paste personal data into prompts, since Operator doesn't block it.
- Keep auto-approve off to control what Operator can access and run.
- Don't ask Operator to show preview values for attributes when building segments or writing Liquid.
The second step has a cost. Users without the View PII permission lose it across the dashboard, not just in Operator, so decide which roles need personal data for their own work.
Which mistakes should you avoid?
Name the mistakes so a reviewer can spot them. An auto-approve habit leaves the toggle on while moving from drafting into live content or settings.
A profile-page prompt opens Operator on a user profile, sending that page's content with the request. A pasted record types personal data into a prompt, which Operator doesn't block.
An unreviewed active edit approves a change to live content without reading the side-by-side card. Because approved actions can't be undone through Operator, that card is the last chance to catch it before launch.
Where does this connect to the rest of the programme?
Operator drafts content, so the standards in high-converting email campaigns and hyper-personalisation in Braze still apply. Shared content it may edit is covered in seven ways to deliver dynamic content.
Segments it drafts are only as good as your data, set out in tracking user events in Braze. Journeys it builds sit inside multichannel engagement campaigns.
As a Braze implementation partner, CustomerIK recommends writing down what Operator may do on its own before anyone turns on auto-approve. Delegate the drafting, review the changes, and keep the launch with a person.
A review record for an Operator task
Start with a task whose result is easy to verify: draft two subject lines for a specified draft email without changing its audience or schedule. Record the workspace, object and allowed fields before reviewing an action card.
Compare the proposed edit with the brief, then reopen the saved draft to verify the result. Treat a shared active Content Block differently: identify its consumers, retain the previous version and preview dependent messages before approving changes.
| Test case | Expected result |
|---|---|
| Card changes an out-of-scope field | Reject it and narrow the task |
| Approved draft edit completes | Verify the saved value and unchanged delivery settings |
| Shared live module is edited | Review dependent messages and rollback plan first |
The worked example and test cases are illustrative editorial guidance, not measured client outcomes or a claim that a live integration has been tested.
Frequently Asked Questions
1. Can BrazeAI Operator launch a campaign?
It can't. Operator can prepare a campaign or Canvas end to end, but you always have to launch changes yourself.
2. Can I undo an action Operator has taken?
Not through Operator. Approved actions can't be undone through it, so describe the new change or make it manually in the dashboard.
3. Is auto-approve on by default?
It isn't. Auto-approve is off by default and resets when you refresh the page, open a new tab or log out.
4. Does Operator send data to OpenAI?
It does. Each request can include your prompt, tool results and up to approximately 4,000 characters of content from the active page.
5. How do I stop Operator accessing personal data?
Turn off the View PII permission for Operator users, avoid user profile pages, and don't paste personal data into prompts.
Sources
- Braze, BrazeAI Operator. Retrieved 18 Oct 2026.
- Braze, Reviewing BrazeAI Operator actions. Retrieved 18 Oct 2026.
- Braze, What you can do with Operator. Retrieved 18 Oct 2026.
- Braze, Data privacy and security for BrazeAI Operator. Retrieved 18 Oct 2026.
- Braze, What's new in Braze. Retrieved 18 Oct 2026.
CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.
If you're rolling out Operator and want the delegation rules written first, let's talk.
.svg)
