Scaling Marketing Operations with Braze: Five Controls

A hand lifting a paddle with a green label towards the first of five hooks on a birch pegboard, while three paddles with cream labels wait in a tray below, showing the first control being put in place before the others.

Scaling marketing operations with Braze comes down to five shared controls: workspace boundaries, Teams for approvals, Content Blocks for shared assets, Canvas templates for repeatable journeys, and workspace quiet hours for send-time defaults. Each control has a documented scope and a failure mode worth planning for. Decide the boundaries first, then add the rest in the order this guide sets out.

Key Takeaways

  • Treat the workspace as the first operating decision, because audiences, assets and permissions all sit inside it.
  • Add an app instance for an updated app, and create a new workspace for an entirely new app.
  • Use a Development and Approver Team pattern, and add delivery validations because Team filters check Canvas users only at entry.
  • Settle Content Block names and owners early, since names can't change and earlier versions can't be restored.
  • Set workspace quiet hours last, as a default per channel, with custom windows kept for exceptions.

What does scaling marketing operations with Braze involve?

Campaign volume grows faster than the habits that keep it tidy. As more people launch work, the gaps show up as inconsistent footers, untested sends and audiences nobody meant to reach.

As a Braze implementation partner, we treat scale as a question of shared rules rather than extra effort. Braze gives you the controls for those rules. The work is deciding who owns each one and in what order you switch them on.

Where should you draw the workspace boundary?

Braze states that everything you do happens within a workspace. It also says workspaces group the same or very similar apps together, such as the Android and iOS versions of one mobile app. That makes the workspace your first operating decision, because audiences, assets and permissions all sit inside it.

The documentation gives a clear rule for releases. If you're updating an app, add a new app instance inside the existing workspace.

If you're releasing an entirely new app to the app store, create a new workspace, which starts without the historical data and user profiles of the older app. Name workspaces with a convention others can search, and keep a testing workspace for integration and campaign testing.

Two details are easy to miss. A segment targets all apps and websites in the workspace by default, so a message meant for one app needs a segment limited to that app. Workspaces that share a Google Project ID also share Firebase Cloud Messaging's default rate limit of 600,000 messages per minute, so Braze recommends dedicated Firebase projects for each workspace.

A deleted workspace can't be restored. Treat deletion as a change request with a named approver, not as housekeeping.

Who should be able to launch what with Teams?

Braze separates three kinds of access. Permission sets control what company users can do across all workspaces, roles control what they can do in specific workspaces, and Teams control the audiences they can reach with their messages. Teams depend on your contract, so confirm availability with your Braze account manager before you design around them.

The documentation describes a Teams-based approval pattern for production. A Development Team works against test users only.

An Approver Team validates the campaign, then promotes and launches it. You get a real release step without any extra tooling.

Read the audience behaviour closely before you rely on it. For a Canvas, Braze only checks whether users match the Team filter when they enter. Team filters don't behave like delivery validations, which double-check your audience at each message send.

If your approval model assumes a Team filter keeps protecting a Canvas after entry, add delivery validations to the Message steps as well. The two controls answer different questions, and an approval design needs both.

Approval design is easier to judge against a worked setting. A case study on unifying guest profiles for a hotel group describes approval workflows embedded directly in the Braze interface to reduce regulatory risk.

How do Content Blocks keep shared assets consistent?

Content Blocks hold reusable, cross-channel content in one place. How you insert one decides whether it stays current.

A block inserted with Liquid is linked to the original and reflects every change. A block added by drag and drop is not linked, so later edits to the original don't reach it.

Three documented facts should shape your governance. Names can't be changed after saving, and a name can't be reused even if the block is archived, so settle a naming scheme before the library grows.

Earlier versions can't be viewed or restored, so save a duplicate before significant edits. A block used in any message can't be archived, and when you audit where one is used, Braze advises reviewing each linked message or step to confirm its status.

Nesting is allowed once. Braze notes that a third level won't expand, and its content and Liquid snippet drop out of the message.

Plan for the silent edit. An owner fixes a typo in a shared block, and every Liquid-linked message changes at once with no earlier version to return to. Give each shared block one named owner and take a duplicate before every edit.

Where do Canvas templates fit?

Braze describes Canvas templates as a consistent framework that can be customised across your Canvases. A template can carry builder settings as well as steps, so a target audience you use often can travel with it.

Access follows the same layering as everything else. Adding a Team to a template limits who can use it, and where permissions exist at both workspace and Team level, the workspace level is prioritised.

Build templates from Canvases that have already run in production, not from a blank page. A journey that has been live has had its entry rules, exits and audience tested by real traffic, and that is what a template should pass on.

What should workspace quiet hours control?

Workspace quiet hours set a default window for a channel across the whole workspace. Every campaign and Canvas that sends on that channel automatically respects the window.

Braze's guidance is to use them for the default case, such as a compliance requirement across all SMS sends, and to keep campaign and Canvas-level windows for exceptions. The release notes list the feature as generally available in an entry dated 12 Nov 2026, so check the current status before you plan around it.

A few documented behaviours matter for planning. A window can't exceed 20 hours.

A scheduled campaign with a fixed send time falls back to Abort message. If a large audience was held during the window, those messages can become eligible to send all at once when it closes.

A custom window on a campaign or Canvas step takes precedence over the workspace window, and updates to the workspace window are recorded in a changelog. Whether a given window satisfies a legal sending-time rule is a question for your counsel. This post does not settle it.

How do the five controls compare?

ControlWhat it governsDecide firstFailure mode to plan for
WorkspaceThe boundary for audiences, assets and permissionsRelease rule: new app instance or new workspaceA segment targets every app in the workspace by default
TeamsAudience access and approvalsWho approves, and what Development can reachTeam filters check Canvas users only at entry
Content BlocksShared contentNaming scheme and one owner per blockAn edit reaches every Liquid-linked message with no earlier version to restore
Canvas templatesRepeatable journeysWhich proven Canvas becomes the templateWorkspace permissions are prioritised over Team permissions
Workspace quiet hoursSend-time defaults per channelWhich channels get a default windowHeld messages can all become eligible when the window closes

What does this look like for a regional retailer?

Take a hypothetical retailer with a mobile app, a website and a loyalty programme. A central team runs the programme and two regional teams adapt it by language. None of this describes real client work.

The central team keeps a production workspace and a testing workspace. When the app is updated, it adds a new app instance to the production workspace. Each regional team becomes a Team defined by language, and a central Approver Team launches anything that reaches the full audience.

A regional marketer builds a win-back Canvas and assumes the language Team filter protects it throughout. It doesn't: the filter is checked at entry, so a customer who later changes language keeps receiving steps. The retailer adds delivery validations to each Message step and promotes the finished Canvas to a template.

The compliance lead owns the shared footer Content Block, and SMS gets a workspace default window. A region that needs a different window sets a custom one, and the Approver Team sees it at review.

In what order should you roll this out?

The order below puts the hardest-to-reverse decisions first. Each step assumes the one before it is settled.

  1. Write the workspace release rule and naming convention, and create the testing workspace.
  2. Confirm Teams availability with your Braze account manager, then set up the Development and Approver pattern.
  3. Name an owner for each shared Content Block, fix the naming scheme and agree to duplicate before edits.
  4. Promote proven Canvases to templates and attach Teams to them.
  5. Set workspace quiet hours by channel last, because the change reaches every campaign and Canvas that sends on that channel.

How does this connect to the rest of the programme?

Approvals and permissions for AI-assisted work are covered in Governing Braze AI: Permissions, Limits and Approvals. Template choices for journeys sit in Using Templates for Faster Marketing Automation in Braze. Your release step pairs well with Agentic Standards: Automated Campaign QA in Braze.

For the build itself, see How to Build an Automated Marketing Workflow in Braze and Marketing Automation Best Practices for Braze Users. Channel-level planning continues in Email Automation in Braze: Six Failure Modes to Plan For.

For the people side of operations, a case study on moving a multi-brand rewards programme to Braze covers the organisation-wide data dictionary and the ongoing hands-on training for marketers.

As a Braze implementation partner, CustomerIK recommends starting with the workspace rule and the approval pattern, because every later control depends on knowing who owns what.

Frequently Asked Questions

1. Do I need Teams to scale marketing operations in Braze?

It depends on the contract. Braze says Teams aren't available on all contracts, and permission sets and roles still control access without them. Teams add audience-level control and the Development and Approver pattern.

2. Should every brand get its own workspace?

Braze documents the rule for apps: a new app gets a new workspace, and an updated app gets a new app instance. It gives no guidance on how many workspaces an organisation needs, so this post states none.

3. Do edits to a Content Block reach every message?

Edits reach it only where it was inserted with Liquid. A block added by drag and drop is not linked to the original.

4. Can a campaign override workspace quiet hours?

You can. Braze says you can keep the workspace default, or opt out and apply a campaign or Canvas-specific window instead.

5. Does this post replace the Braze documentation?

Braze documentation stays the source of truth, and limits and release status can change, so check the linked pages before you rely on a figure.

Sources

CustomerIK is a Braze implementation partner working across onboarding, technical integration, marketing operations and customer data management.

If you're deciding how to set the workspace rule and the approval pattern for your Braze programme, let's talk.

Preferences

Privacy is important to us, so you have the option of disabling certain types of storage that may not be necessary for the basic functioning of the website. Blocking categories may impact your experience on the website.

Accept all cookies
Accept all cookies

These items are required to enable basic website functionality.

Always active

These items are used to deliver advertising that is more relevant to you and your interests.

These items allow the website to remember choices you make (such as your user name, language, or the region you are in) and provide enhanced, more personal features.

These items help the website operator understand how its website performs, how visitors interact with the site, and whether there may be technical issues.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.