Brevo permissions: who can send to your whole base?

Jean RubensUpdated July 20269 min read

A new team member joins on Monday. On Tuesday, they prepare their first Brevo campaign, open the recipient picker, tick "All contacts" out of reflex and click Send. Forty thousand people receive an email that wasn't ready. Nobody meant any harm, and yet the damage is done.

The problem is structural, not a matter of discipline. In Brevo, permission to send a campaign says nothing about which contacts you're allowed to target. Whoever can send can send to everyone. Let's look at what Brevo permissions actually control, why the whole base stays one click away, what it costs, and how to frame who sends to whom.

What do Brevo permissions actually control?

They control access to features, not to contacts. An admin enables modules per user (Campaigns, Contacts, Automations, Transactional) and, for campaigns, a scope per folder. No permission limits which lists or segments a user can target (Brevo, User permissions and permission levels, 2026).

Granularity therefore stops at the feature and the campaign folder; it never descends to the list or the record. As soon as a colleague can create and send a campaign, they see every list in the account in the recipient picker, including the "All contacts" option.

The free account is single-user: multi-user access and granular permission settings appear only on higher paid plans, and reusable predefined roles are an Enterprise-plan feature. Because plan names and seat counts change regularly, confirm the details on Brevo's pricing page. We also summarize Brevo permissions without the Enterprise plan.

In other words: in Brevo, permissions are set per product module and, for campaigns, per folder, never per list or segment (Brevo, 2026). The moment a user can send a campaign, they can point it at any list in the account, including the entire base.

Why can anyone reach the whole base?

Because nothing stops them, and human error is common. In a Tessian survey, 58% of employees admit having sent a work email to the wrong person (Tessian, The Psychology of Human Error). Brevo installs no guardrail between that reflex and your entire base: no per-user list restriction, no "All contacts" box you can hide.

Above all, an approval step is missing. Brevo offers a preview and a test before sending, and an internal compliance review for SMS, but no team circuit where a member prepares and an admin approves before it goes out. True approval workflows come from third-party tools placed above the account.

The only truly native levers are blunt. The first: don't grant send rights at all. The second: physically separate databases into sub-accounts, an Enterprise-plan capability that multiplies the accounts you administer. Between the two, nothing bounds the scope of a send.

What does a send to the whole base really cost you?

It costs deliverability, to all your teams, not just the person who sent it. Since February 2024, Gmail and Yahoo require bulk senders to keep the spam-complaint rate below 0.3%, that's three complaints per thousand emails, and Google recommends staying under 0.1% (Google, Email Sender Guidelines, 2024). A large, untargeted send spikes complaints all at once.

The starting margin is already thin. In 2026, roughly 15% of legitimate marketing email never reaches the inbox, for a global inbox placement at 84.5% (Validity, $42 Million a Day, Q2 2026). Burning your reputation with a send to the whole base eats into an already reduced margin.

The risk goes beyond marketing. Nearly six data breaches in ten involve human error (Verizon, Data Breach Investigations Report, 2025), and sending to the wrong recipient consistently ranks among the top recorded errors. An entire base sent by mistake is also a potential GDPR incident.

Conversely, targeting pays. With the same senders, segmented campaigns see 100.95% more clicks and 9.37% fewer unsubscribes than non-segmented sends (Mailchimp, Effects of List Segmentation). On top of the risk, a send to the whole base is also the worst performer.

How do you limit who can send, and to whom?

Start by restricting the right to send, then add the scope Brevo doesn't handle. Because native permissions don't descend to the list, the only immediate native fix is to grant sending only to the people who need it. The rest, per-list scope and approval before sending, is handled on top of the account.

The first two steps are native. The last two require a governance layer on top of Brevo. The full method, with the setup order, is detailed in our complete guide to multi-team Brevo governance. The same logic applies on the Mailchimp side, where roles are also global and without per-audience scope.

Frequently asked questions

Jean Rubens

Co-founder, Sendgate

Jean is a co-founder of Sendgate. He writes about email sending governance for teams: access compartmentalization, per-list scope and approval before sending across shared sending accounts.