> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/how-to-add-a-member-to-your-team.md).

# How to add a member to your team?

Invite members of your team and give them a role on each project, depending on what they need to do in Batch.

This lets your tech, marketing and editorial teams work together on the same dashboard, each with the right level of access.

{% hint style="danger" %}
Only **Company Admins** can invite members, change their roles and manage saved roles. If you cannot see these options, ask a Company Admin of your account to do it, or to give you the Company Admin role.
{% endhint %}

## Understanding roles <a href="#understanding-roles" id="understanding-roles"></a>

Permissions are set **per project**: a member can have a different role on each project of your company, for example Publisher on one project and Viewer on another.

Any role, predefined or custom, can be applied to one project, a selection of projects, or all projects of your company, including projects created later.

### Predefined roles <a href="#predefined-roles" id="predefined-roles"></a>

On each project, a member can have one of these roles. Each role includes everything the previous one can do.

| Role          | What it grants                                                                                                                                                    |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **No access** | The member cannot access the project.                                                                                                                             |
| **Viewer**    | Read-only access to the project: orchestrations, templates, data and analytics.                                                                                   |
| **Creator**   | Everything Viewer can do, plus creating and editing orchestrations as drafts. Creators cannot launch or stop an orchestration, nor save changes to a running one. |
| **Publisher** | Everything Creator can do, plus launching orchestrations (sending a campaign or activating an automation) and stopping them.                                      |
| **Admin**     | Everything Publisher can do, plus managing the project's settings, data and privacy.                                                                              |

{% hint style="info" %}
The **Creator** role is designed for teams where some members (juniors, agencies…) prepare orchestrations, and someone else reviews and launches them with the **Publisher** role.
{% endhint %}

### Company Admin <a href="#company-admin" id="company-admin"></a>

**Company Admin** is not set per project: it is a toggle in the member's settings. A Company Admin has full access to every project and to the company account: team members, roles, billing and company settings.

### Custom permissions <a href="#custom-permissions" id="custom-permissions"></a>

When no predefined role fits, select **Custom role** in the role list to open the **Custom permission** panel and set an access level line by line for a project.

**Orchestrations**

| Line           | Available levels                 |
| -------------- | -------------------------------- |
| **Campaign**   | No access, View, Create, Publish |
| **Automation** | No access, View, Create, Publish |

Expand a line to set each channel separately:

* Campaign: Email, Push, SMS
* Automation: Trigger (Omnichannel, In-App) and Recurring (Email, Push, SMS)

**Features**

| Line                    | Available levels                |
| ----------------------- | ------------------------------- |
| **Marketing pressure**  | No access, View, Create, Manage |
| **Basic data**          | No access, View, Create, Manage |
| **Advanced data**       | No access, View, Create, Manage |
| **Privacy**             | No access, View, Create         |
| **Settings**            | No access, View, Create         |
| **Contents**            | No access, View, Create, Manage |
| **Analytics**           | No access, View                 |
| **Editorial dashboard** | No access, Publish              |

Some lines can be expanded to set their sub-items separately. For example, **Settings** includes **Project settings**, **Channel settings** and **Test recipients**. When the sub-items of a line have different levels, the line shows **Mixed**.

Custom permissions are useful for teams dedicated to one channel or one type of orchestration, or for profiles who should not work on orchestrations at all, such as developers or DPOs who only need **Settings** or **Privacy**.

### Good to know <a href="#good-to-know" id="good-to-know"></a>

* **Publish** covers both sending a campaign and activating an automation.
* The **Create** level does not allow saving changes to a running orchestration.
* A member only sees orchestrations where **all** channels are within their permissions. If one channel of a journey is out of their scope, the whole journey is hidden from them.
* The level set on **Omnichannel** applies to every channel used in the journey: Create on Omnichannel means Create on all channels of the journey.
* A member cannot save an orchestration that includes a message on a channel they do not have access to.
* The list of permissions is the same on every project: you can set a level on a channel that is not active on a project yet. As soon as the channel is activated, members who have rights on it get access.

{% hint style="warning" %}
Before restricting a member to some channels, check which journeys they work on: they will no longer see multi-channel journeys that include another channel.
{% endhint %}

### Saved roles <a href="#saved-roles" id="saved-roles"></a>

A saved role is a named set of custom permissions (e.g. "Support L2") that you can give to several members, on any project. Saved roles appear under **Custom roles** in the role list.

To create one:

1. Click **Manage roles** on the Manage team page, then **Create role**.
2. In the **Custom permission** panel, set an access level for each line.
3. Click **Save as new role**, enter a **Custom role name**, then click **Save**.

**Manage roles** lists your saved roles and lets you search, edit or delete them:

* **Editing** a saved role updates every member who has it, after a confirmation. From a member's settings, you can also apply the change to this member only.
* **Deleting** a saved role removes no access: members who had it keep the exact same permissions, as custom permissions.

## Inviting new members <a href="#inviting-new-members" id="inviting-new-members"></a>

Open your account's menu in the top right corner of the dashboard, click **Manage team**, then click **Invite member(s):**

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FggaonkHQcCNbBrs3U1Yx%2Fimage.png?alt=media&amp;token=1718d6ae-695e-40e1-83f9-2da7b30e4974" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
To reinforce access control, the dashboard requires administrators to use **multi-factor authentication** (MFA) for sensitive operations such as inviting a user or changing permissions. If your company has no MFA method configured, the dashboard asks you to confirm with your password.
{% endhint %}

Then, choose the new member's access: turn on **Company admin**, or pick a role for each project they need to access.

{% hint style="warning" %}
If one of your teammates already has a Batch account registered with their email address, **contact our support team** (<support@batch.com>) with the following information:

* Email address of their first account.
* Email address of the team they want to join.
  {% endhint %}

## Managing existing members <a href="#managing-existing-members" id="managing-existing-members"></a>

### Reading the team list <a href="#reading-the-team-list" id="reading-the-team-list"></a>

The **Manage team** page lists every member of your company and shows how many of your seats are in use. You can search members, filter them by project or by role, and export the list.

* **Role(s)**: the role name, **Custom** for unsaved custom permissions, or **Multiple** when the member has different roles across projects, with the number of projects they can access.
* A **2FA** badge shows members who enabled two-factor authentication.

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FLKs3RpPXjH67TT2q8l94%2Fimage.png?alt=media&amp;token=febd5fc2-5d3c-45e5-9674-afd25e909f04" alt=""><figcaption></figcaption></figure>

### Changing a member's role <a href="#changing-a-members-role" id="changing-a-members-role"></a>

On the Manage team page, click the **Edit** icon (pencil) next to the member. In the **Edit member** panel, you can:

* Turn on the **Company admin** toggle to give them full access to all projects and organization settings.
* Under **Permissions on projects**, pick a role for each project, from **Basic roles** or **Custom roles**, or use **Apply role to all** to set the same role on every project.

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2Ft0cb2TboVlIEcQacwqvW%2Fimage.png?alt=media&amp;token=3df13df4-d3c0-4c87-b0ac-62ec4aaa85ce" alt=""><figcaption></figcaption></figure>

### Removing a member <a href="#removing-a-member" id="removing-a-member"></a>

Click the **Delete** icon (bin) next to the member on the Manage team page.

{% hint style="info" %}
Removing a member only removes their access to the dashboard. Everything they created or configured (campaigns, automations, templates, settings) stays as it is: running orchestrations keep running, and nothing is deleted, paused or modified.
{% endhint %}

<figure><img src="https://1464139620-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUIK868wiiK9XOVyETGZS%2Fuploads%2FIwrTIiuTBE4Q1YFh6CGU%2Fimage.png?alt=media&amp;token=61ef5772-1fdd-4038-b2c5-ce412bd92b0f" alt=""><figcaption></figcaption></figure>

### Moving from previous permissions <a href="#moving-from-previous-permissions" id="moving-from-previous-permissions"></a>

When roles per project were activated for your company, every member kept the same access as before. Nobody is set to Creator automatically: to use Creator or custom permissions, a Company Admin has to update members from **Manage team**.

## Setting an audience restriction

On top of their role, a member can be restricted to part of your audience, so they can only target, see and analyse what they are responsible for. Two types of restriction are available, and they can be combined:

* **Segments**: the member can only target their authorised segments, and only sees the orchestrations and analytics related to them. See [Segment restrictions](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/manage-team#segment-restrictions).
* **Countries and languages**: the member can only target their authorised countries and languages. See [Country and language restrictions](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/manage-team.md#country-and-language-restrictions).

{% hint style="success" %}
Countries and languages restrictions are configured by Batch: reach out to your Customer Success Manager to have them set up for your team.
{% endhint %}

{% hint style="success" %}
Segments restriction are not enabled by default. Contact your Customer Success Manager to activate them.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.batch.com/getting-started/how-to-add-a-member-to-your-team.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
