# One agency, many clients: namespaces, teams, and roles

> Create one namespace per client from the selector at the top of the menu, with sender, groups, and templates in the client's language. Invite the agency and client teams by email, as Admin or User, in each namespace. Everyone signs in with their own login, sees only their clients, and switches accounts in one click.

Fonte: https://wiki.bip.marketing/en-us/agency-multiple-clients · Atualizado: 2026-10-08

<UseCaseMeta effort="nocode" plan="free" />

Each of your agency's clients gets its own BIP account, and your team signs in to all of them with a single login, each person with the right access.

<Checklist items="A BIP account (the free plan works: each new namespace gets 1,000 free sends per month)|The list of clients and who handles each one|The email of each person, at the agency and at the client, who will use the dashboard|A computer: the dashboard is built for large screens" />

## What you'll get

- One namespace per client, with separate contacts, campaigns, plan, send capacity, billing, sending domain, and WhatsApp.
- A team with a single login: each person switches clients from the selector, without signing out and back in.
- The client in the dashboard, with access to their own account only.
- Campaign, template, and segment lists organized the same way across all clients.
- Email templates in each client's language.
- A checklist for launching a new client without missing a thing.

## How it works

<Steps items="Create a namespace for each client|Invite the team to each namespace, as Admin or User|Standardize sender, groups, names, and language across all clients" />

In BIP, each account is a **namespace**. For an agency, a namespace is a client. Everything that belongs to the client stays inside it, and nothing crosses from one namespace to another:

| Kept in each namespace | What it means for the agency |
| --- | --- |
| Contacts, segments, campaigns, email templates, and webhooks | Each client's base and history, kept apart |
| Plan, send capacity, and billing | Each client has its own monthly usage and its own subscription. Every new namespace starts on BIP Lite, with 1,000 free sends per month |
| Sending domain | One domain per namespace, and each domain belongs to a single namespace |
| WhatsApp | The client's own WhatsApp Business, connected in their namespace |
| Fields, KPIs, tags, groups, topics, and API keys | Each client's settings, set up their way |
| Team | Who gets in and with which role, client by client |

One person has a single login and joins as many namespaces as needed, with a role in each one. The selector at the top of the menu shows only the namespaces that person belongs to. Invitations are per namespace: inviting someone to Padaria Aurora doesn't give them access to Clínica Vida Leve.

### Admin and User

| What the person can do in the namespace | Admin | User |
| --- | --- | --- |
| Invite people, change someone's role, and remove people from the namespace | Yes | No |
| Add, verify, and delete the sending domain | Yes | No |
| Create, edit, and delete API keys | Yes | No |
| Contacts, segments, campaigns, email templates, WhatsApp, and webhooks | Yes | Yes |
| Edit their own name and password | Yes | Yes |

Whoever creates a namespace joins it as **Admin**. Invited people get the role chosen in the invitation.

### An example: the Agência Pulso team

Agência Pulso handles three clients and has an internal namespace for testing. The marketing person at Clínica Vida Leve also uses the dashboard, but only in the clinic's account.

| Person | Who they are | Padaria Aurora | Clínica Vida Leve | Studio Kraft | Agência Pulso (internal) |
| --- | --- | --- | --- | --- | --- |
| Marina Alves | Agency director | Admin | Admin | Admin | Admin |
| Tiago Pereira | Analyst | Admin | User | User | User |
| Rafael Lima | Analyst | User | Admin | Admin | User |
| Sofia Costa | Marketing at Clínica Vida Leve | — | User | — | — |

Each client has two agency Admins. That way, there's always someone to invite people, change roles, and manage the domain, even when one of them is on vacation.

## Step by step

### 1. Create one namespace per client

1. At the top of the side menu, open the namespace selector and click **+ Create New Namespace**.
2. In **Account Name**, write the client's name the way people know it, in full: _Padaria Aurora_. This is the name that appears in the selector.
3. In **Language**, choose the client's language. The namespace's default groups and topics are created in that language, and the topics appear to the client's contacts in their communication preferences. The screen defaults to **English**.
4. In **Timezone**, choose the client's timezone. It's the reference for dates in segments and the timezone new campaigns start with.
5. Click **Create Namespace**. You enter the new namespace as **Admin**.

Repeat for each client. It's also worth creating a namespace for the agency itself, such as _Agência Pulso (internal)_, to test templates and train the team without touching any client's base.

<Shot src="/img/agencia-varios-clientes/1-en-us.png" alt="Create a new namespace screen with Account Name, Language, and Timezone filled in for Padaria Aurora" url="dash.bip.marketing/namespace-selection?mode=create" />

### 2. Check the client's sender

1. Inside the client's namespace, open **Settings** → **General**.
2. **Email From (Name)** already comes filled in with the **Account Name**. Adjust it if the client signs off differently.
3. **Email From (Address)** is `no-reply@bip.marketing` until the client has a verified domain. On a paid plan, an Admin adds the client's domain in **Settings** → **Email Domains**. See [Your own sending domain](/en-us/sending-domain).
4. In **Account Information** → **Namespace**, copy the identifier. The client's dashboard address is `dash.bip.marketing/<namespace>`: add it to the team's bookmarks.
5. Click **Save**, at the top of the page.

<Shot src="/img/agencia-varios-clientes/2-en-us.png" alt="Settings General tab with the namespace, Email From (Name), and Email From (Address) for Padaria Aurora" url="dash.bip.marketing/…/settings" />

### 3. Organize the groups

1. In **Settings** → **Groups**, review the **Campaigns Groups**, **Email Templates Groups**, **Segments Groups**, and **Webhooks Groups** lists. On BIP Full, **Flows Groups** and **Forms Groups** also appear.
2. Every new namespace comes with ready-made groups, such as **Newsletter**, **Promotional**, and **Special Offers** for campaigns. Change the **Group Name** and **Description** to match the agency standard, and use the trash can to remove the ones the client won't use. Each list keeps at least one group.
3. To create a group, click the list's button, such as **Add Campaign Group**.
4. Use the arrows to change the order. It's the order in which groups appear in the **Campaigns**, **Emails Templates**, **Segments**, and **Webhooks** lists.
5. Click **Save**.

Then choose the **Group** in each campaign, template, and segment. Anything without a group, or in a group you removed, appears under **Ungrouped**. The group convention is in [Ready to copy](#ready-to-copy).

<Shot src="/img/agencia-varios-clientes/3-en-us.png" alt="Groups tab with the Campaigns Groups renamed to the agency standard" url="dash.bip.marketing/…/settings?tab=groups" />

### 4. Invite the agency team

1. In **Settings** → **Users**, click **Invite User to Join**. Only namespace **Admin**s can use this button.
2. Fill in the person's **Email** and **Name**.
3. In **Role**, choose **Admin** for whoever is accountable for the client's account and **User** for whoever builds segments, templates, and campaigns.
4. Replace the **Email Subject** and **Email Body** with the agency's copy, keeping `{INVITE_LINK}` in the body. The copy is in [Ready to copy](#ready-to-copy).
5. Click **Send Invitation**.

The link is valid for 7 days. Anyone who already has a BIP login just confirms the invitation, and the new client shows up in their selector. Repeat this in each namespace: an invitation only covers the namespace you're in.

<Shot src="/img/agencia-varios-clientes/4-en-us.png" alt="Invite User dialog with email, name, role, and the Agência Pulso invitation copy" url="dash.bip.marketing/…/settings?tab=users" />

### 5. Give the client access to their account only

1. In the client's namespace, invite the client's contact person with the **User** role. At Clínica Vida Leve, that's Sofia Costa.
2. She opens the email, clicks the link, and, in **Complete Your Invitation**, creates a **Password** (or just confirms, if she already has a BIP login). Then she clicks **Accept Invitation** and lands right in the clinic's namespace.
3. Her selector shows only Clínica Vida Leve. She can follow contacts, segments, campaigns, and stats, without inviting or removing people.
4. To change someone's role, use the selector next to the person in **Settings** → **Users**. To remove their access, click the trash can and confirm in **Are you sure?**.

<Shot src="/img/agencia-varios-clientes/5-en-us.png" alt="Clínica Vida Leve user list with two agency Admins and the client as User" url="dash.bip.marketing/…/settings?tab=users" />

### 6. Write templates in the client's language

1. In **Emails Templates**, click **New Template** and then **Settings**.
2. In **Name**, follow the agency convention, such as _Welcome · Padaria Aurora_.
3. In **Group**, choose the template's group.
4. In **Language**, choose the language the email is written in: **Portuguese**, **English**, or **Spanish**. Language is set per template, and every new template starts in **English**.
5. Click **Save**.

To reuse a block you've already styled, such as a button or social networks, select the block and click **Copy to Clipboard**. In the same browser tab, switch namespaces from the selector, open the other client's template, and choose **Paste Block** from the blocks menu.

<Shot src="/img/agencia-varios-clientes/6-en-us.png" alt="Email Template Settings panel with name, group, and Language set to English" url="dash.bip.marketing/…/emails-templates/…" />

### 7. Switch clients from the selector

1. Click the selector at the top of the side menu and choose the client. The dashboard reloads in that client's account, and the address changes to `dash.bip.marketing/<namespace>`.
2. On BIP Lite, the **Usage** card, at the bottom of the menu, shows usage for the open namespace: **Used** and **Remaining**.
3. When signing in, anyone who belongs to more than one namespace picks the client in **Choose a namespace to continue**.

<Shot src="/img/agencia-varios-clientes/7-en-us.png" alt="Namespace selector open with the Agência Pulso clients and the Create New Namespace button" url="dash.bip.marketing/…" />

## Ready to copy

### Invitation for the agency team

Replace _Padaria Aurora_ with the namespace's client. The body is a single paragraph, with the link at the end.

<Copy label="Email Subject">
Agência Pulso: your access to Padaria Aurora on BIP
</Copy>

<Copy label="Email Body">
Hi! You're now part of the Agência Pulso team that handles Padaria Aurora on BIP. To get in, click the link at the end of this message and finish setting up your access. After that, switch clients using the selector at the top of the menu. The link is valid for 7 days: {INVITE_LINK}
</Copy>

### Invitation for the client

<Copy label="Email Subject">
Clínica Vida Leve on BIP: your access
</Copy>

<Copy label="Email Body">
Hi! Agência Pulso has set up the Clínica Vida Leve account on BIP, where the clinic's contacts and campaigns live. There, you can follow every send and its results. To get in, click the link at the end of this message and finish setting up your access. The link is valid for 7 days: {INVITE_LINK}
</Copy>

### New client onboarding checklist

Paste it into your task manager and use one per client.

<Copy label="New client onboarding">
New client onboarding · Agência Pulso

[ ] 1. Namespace: + Create New Namespace, with Account Name (the client's name in full), and the client's Language and Timezone
[ ] 2. Sender: Settings → General → Email From (Name) and Email From (Address) → Save
[ ] 3. Sending domain (paid plan): an Admin adds it in Settings → Email Domains, sends the DNS records to the client, and follows up until Verified
[ ] 4. Fields: Settings → General → Fields, with the fields from the client's spreadsheet (e.g., City, Location type; Birth date, Date type)
[ ] 5. Groups: Settings → Groups, renamed to the agency standard
[ ] 6. Import: Leads → Import Leads, with Default Country Code and the batch tag (e.g., import-2026-10)
[ ] 7. First segment: Tags → Includes any → batch tag, count checked and saved
[ ] 8. Team: two agency Admins, analysts as User, the client's contact person as User
[ ] 9. WhatsApp (paid plan): Connect WhatsApp with the client's number and templates synced
[ ] 10. Test: first campaign saved as a draft and Test Campaign sent to an agency contact
</Copy>

### Naming conventions

**Namespaces**: the client's name in full, with no abbreviations, plus one internal namespace for the agency.

<Copy label="Account Name for each namespace">
Padaria Aurora
Clínica Vida Leve
Studio Kraft
Agência Pulso (internal)
</Copy>

**Groups**: the same names for every client, so the team finds everything in the same place. Use them in **Campaigns Groups**, **Email Templates Groups**, and **Segments Groups**.

<Copy label="Group Name — Description">
Relationship — Welcome, birthdays, and win-back
Promotions — Time-limited offers and launches
Holidays — Christmas, Mother's Day, and the client's own dates
Content — Newsletter and updates
Agency tests — Drafts and tests before they go to the client
</Copy>

**Campaigns, segments, and templates**: the name says what it is, without having to open it.

| Item | Pattern | Example |
| --- | --- | --- |
| Campaign | Year-month · Goal · Channel | 2026-11 · Black Friday · WhatsApp |
| Segment | Audience · Rule | Customers · No update in 60 days |
| Email template | Goal · Client | Welcome · Padaria Aurora |
| WhatsApp template | client_goal, lowercase | `aurora_saturday_bake` |
| Batch tag | source-year-month | `import-2026-10` |

### Access spreadsheet

Keep a spreadsheet of who has access to each client and with which role. Review it every month.

<Copy label="access.csv" code>
person,email,namespace,role
Marina Alves,marina.alves@exemplo.com,Padaria Aurora,Admin
Marina Alves,marina.alves@exemplo.com,Clínica Vida Leve,Admin
Marina Alves,marina.alves@exemplo.com,Studio Kraft,Admin
Marina Alves,marina.alves@exemplo.com,Agência Pulso (internal),Admin
Tiago Pereira,tiago.pereira@exemplo.com,Padaria Aurora,Admin
Tiago Pereira,tiago.pereira@exemplo.com,Clínica Vida Leve,User
Tiago Pereira,tiago.pereira@exemplo.com,Studio Kraft,User
Tiago Pereira,tiago.pereira@exemplo.com,Agência Pulso (internal),User
Rafael Lima,rafael.lima@exemplo.com,Padaria Aurora,User
Rafael Lima,rafael.lima@exemplo.com,Clínica Vida Leve,Admin
Rafael Lima,rafael.lima@exemplo.com,Studio Kraft,Admin
Rafael Lima,rafael.lima@exemplo.com,Agência Pulso (internal),User
Sofia Costa,sofia.costa@exemplo.com,Clínica Vida Leve,User
</Copy>

## How to measure

- **Usage per client**: open the namespace from the selector and check the **Usage** card, with the month's **Used** and **Remaining**. In **Settings** → **Billing**, **Usage Period** shows the current capacity month, and **Billing History** lists each **Capacity Usage** and each **Invoice Payment**.
- **Client report**: in **Campaigns**, open **Campaign Stats** for each send of the month: **Delivered**, **Open Rate**, **Click Rate**, and **Top clicked links**. To bring an audience list into the client's spreadsheet, use **Download CSV** on the segment.
- **Access up to date**: once a month, open **Settings** → **Users** in each namespace and compare it with the access spreadsheet. Each client should have two agency Admins, and no one who has left the team.
- **Standard applied**: in the **Campaigns**, **Emails Templates**, and **Segments** lists, nothing should be left under **Ungrouped**.

## Variations

### The client buys its own plan

Billing is per namespace. The agency can buy the client's paid BIP Lite plan in **Settings** → **Billing** → **Upgrade Now**, or the client can do it in their own namespace. Capacity and invoices stay in that namespace, separate from other clients. See [Plans and limits](/en-us/plans-and-limits).

### A client with more than one brand

Create one namespace per brand. Each namespace has one sending domain and its own WhatsApp, so brands with different domains or numbers each get their own namespace: _Loja Horizonte_ and _Loja Horizonte Outlet_, for example.

### A client who speaks Spanish or Portuguese

Create the namespace with the client's **Language**: the default groups and topics are created in that language. In email templates, choose the same **Language**, and in WhatsApp templates, the **Language** of the text, such as **Spanish (LATAM)**. The dashboard language is a separate setting, chosen in each browser under **Settings** → **General** → **Language**: the agency team keeps seeing the dashboard in English.

### A test namespace

In _Agência Pulso (internal)_, the team tests templates, segments, and campaigns with the agency's own contacts before building them for the client. It also gets 1,000 free sends per month, without touching anyone else's capacity.

## Frequently asked questions

### Can the client see the agency's other clients?

No. The selector shows only the namespaces the person belongs to. Someone who joins Clínica Vida Leve as a **User** sees only the clinic: the other clients' contacts, campaigns, and settings stay in their own namespaces.

### Who pays for each client's sends?

Each namespace has its own plan, capacity, and billing. Every new namespace starts with 1,000 free sends per month, and the paid plan is purchased in each one, by whoever the agency and the client agree on.

### Someone left the agency. How do I remove their access?

In each namespace they belong to, open **Settings** → **Users**, click the trash can next to their name, and confirm. Removing someone only revokes access to that namespace, so repeat it for every client. Before you do, make sure each client still has two Admins.

### Can I use the same domain or the same WhatsApp for two clients?

No. Each sending domain belongs to a single namespace, and a WhatsApp Business account is connected to one namespace at a time. Each client uses its own domain and its own number, in its own namespace.

## See also

- [Account and team: namespaces, invitations and roles](/en-us/account-and-team)
- [Plans and limits: sends, capacity and pricing](/en-us/plans-and-limits)
- [Your own sending domain](/en-us/sending-domain)
- [Email editor: blocks, variables and preview](/en-us/email-editor)
- [Import contacts from a spreadsheet](/en-us/import-contacts)
- [Connect WhatsApp Business to BIP](/en-us/connect-whatsapp)
- [BIP for agencies](https://bip.marketing/en-us/solutions/agencies)