> 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/features/customer-engagement-platform/settings/manage-team.md).

# Manage Team

<figure><img src="/files/JHaL9xRmer10w3HxfS2P" alt=""><figcaption></figcaption></figure>

## Manage Team

Team management is handled at the company level, by users with the **Administrate** permission. The **Manage team** page lists every member of your company with their authentication method, their permissions and the apps they can access, and shows how many of your seats are currently in use.

You can control access along three axes:

* **What a user can do** — the permissions granted to their account.
* **Which apps and projects they can see** — app-level access.
* **Which countries and languages they can address** — targeting restrictions.

### Managing permissions

Batch lets you set specific permissions at the user level to facilitate team collaboration. Permissions are cumulative: a user can hold several of them.

| Permission       | What it grants                                                                                                                                     |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Administrate** | Full access to the company account: team members, user permissions, billing and company settings. An account can have more than one administrator. |
| **Review**       | Read-only access to the dashboard. Review users can browse orchestrations, templates and analytics, but cannot create, edit or launch anything.    |
| **App**          | Rights to edit and manage the projects and apps the user has access to, including in-app templates and themes.                                     |
| **Campaign**     | Rights to create, edit, launch and delete orchestrations — both Campaigns and Automations — across the channels enabled on the project.            |
| **Privacy**      | Rights to manage GDPR settings and handle data subject requests.                                                                                   |

{% hint style="info" %}
Permission names in this page match the labels shown in the dashboard. **Campaign** covers every type of orchestration, one-shot Campaigns as well as Automations.
{% endhint %}

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

### Scoping access to apps and projects

A user with **Administrate** rights can grant another user access to a selected set of apps rather than to the whole account. The **Apps** column of the team list shows the current scope of each user.

Granting a user every app of a project gives them access to that project. This is how you make sure a team only sees the perimeter it is responsible for — one project per brand, per market or per business unit is the most common setup.

The user holds the same permissions on every app assigned to them.

To check who currently has access to a given app, open the Team tab in the settings of the corresponding project.

{% hint style="info" %}
Permissions cannot differ between the channels of a single project. A user has the same rights on the iOS, Android and Web apps of a project, and those rights automatically apply to the Email, SMS and Universal Channel orchestrations of that project.
{% endhint %}

### Authentication methods

The **Authentication** column shows how each member signs in — `Standard` for email and password, `2FA` when two-factor authentication is enabled on their account. Use it to check the security posture of your team at a glance.

Members enable two-factor authentication themselves from their own account settings. If your company uses Single Sign-On, sign-in is handled by your identity provider and security settings are managed by your organisation.

### Country and language restrictions

On top of project-level access, a user can be restricted to a set of countries and/or languages. Restricted users can only work on the part of your audience they are responsible for — typically local marketing managers in a decentralised organisation.

Once a restriction is set:

* **Visibility** — the user only sees orchestrations that target their authorised countries and languages, plus drafts that have no targeting defined yet.
* **Targeting** — in the targeting block, the user can only select the countries and languages they have rights on.
* **Guardrails** — the user cannot save or launch an orchestration that does not include at least one of their authorised values. A user restricted on both a country and a language must include both: a user restricted to France/French cannot address French-speaking profiles in Belgium.
* An orchestration mixing authorised and unauthorised countries is not visible to the restricted user.

{% hint style="info" %}
Country and language restrictions are configured by Batch. Reach out to your Customer Success Manager to have them set up for your team.
{% endhint %}

### Designing your governance model

Large or decentralised teams usually combine the three axes above:

* **Split by perimeter** — one project per brand, market or business unit, and project-level access granted accordingly. Assets (orchestrations, templates, segments, analytics) are naturally scoped to their project.
* **Split by market inside a shared perimeter** — a single project, with country and language restrictions to keep each local team within its own audience.
* **Open in read-only** — the **Review** permission for stakeholders who need visibility on what is being sent without the ability to change it.

{% hint style="info" %}
Your Customer Success Manager can help you map your organisation onto Batch and set up the right combination for your team.
{% endhint %}

## Troubleshooting

### I didn't receive my invite

Here are some suggestions to find the issue:

1. **Check your spam folder** and look for an email sent by <hello@batch.com>.
2. **Resend the invite**: Ask the administrator of Batch account to double-check the email address they used or resend the invite.
3. **Validation link**: If none of the above work, your manager can send you the confirmation link he will see after inviting you.

### I Get "\[Email Address] Is Already Registered On Batch.Com"

If one of your teammates already has a Batch account registered with his email address, he needs to contact our support team (<support@batch.com>) with the following information:

* Email address of his first account.
* Email address of the team he wants to join.

We will add him to your team with all the apps he created with his previous account.

### Can I Manage Several Accounts With The Same Email Address?

You cannot manage more than one account with the same email address.

If you have a Gmail account or use Google Apps, you can add a "+" at the end of your username to benefit from dynamic alias (e.g. <andrew+secondaccount@gmail.com>).

### How Can I Delete My Account?

Just ask us to delete your account at <support@batch.com>. Our team will let you know when it's done.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/manage-team.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.