> 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 Manage team allows full coordination of your team work on Batch.
## Manage Team **Company Admins** manage your team at the company level. The **Manage team** page lists every member of your company with their role and the projects they can access, and shows how many of your seats are currently in use. You can control access along two axes: * **What a member can do on each project**: their role. * **Which countries and languages they can address**: targeting restrictions. ### Roles You set permissions **per project**: a member can hold a different role on each project of your company. | Role | What it grants | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **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. | | **Project Admin** | Everything Publisher can do, plus managing the project's settings, data and privacy. | | **Company Admin** | Full access to every project and to the company account: team members, roles, billing and company settings. | When you invite or edit a member, you choose their role for one project, a selection of projects, or all projects of your company, including projects created later. {% hint style="info" %} Only Company Admins can invite members and change their roles. {% 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, the dashboard asks you to confirm with your password. {% endhint %} ### Custom permissions When no predefined role fits, select **Custom…** to set an access level line by line for a project. **Orchestrations**: No access, View, Create or Publish * Campaigns: Email, Push, SMS * Automations: Trigger (Omnichannel, In-App) and Recurring (Email, Push, SMS) **Features**: No access, View, Create or Delete * Manage Marketing Pressure, Manage basic data, Manage advanced data, Privacy, Settings, Contents You can set each line as a whole, or expand it to set each channel separately. Good to know: * A member only sees orchestrations where **all** channels are within their permissions. If one channel of a journey is out of their scope, Batch hides the whole journey from them. * The level you set on **Omnichannel** applies to every channel used in 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, and the level applies as soon as the channel becomes active. ### Saved roles In custom permissions, click **Save as a role…** and give the configuration a name (e.g. "Support L2"). Batch adds it to the role list, and you can give it to other members on any project. **Manage roles** lists your saved roles and lets you edit or delete them: * **Editing** a saved role updates every member who has it. 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 same permissions, as custom permissions. ### Reading the team list * **Role**: the role name, **Custom** for unsaved custom permissions, or **Multiple** when the member has different roles across projects. * **Projects**: the number of projects the member can access. Hover it to see the role on each project. ### Moving from previous permissions When Batch activates roles per project for your company, every member keeps the same access as before. Batch does not set any member to Creator automatically. To use Creator or custom permissions, update your members from **Manage team**. ### Authentication methods Members who enabled two-factor authentication show a **2FA** badge next to their name. 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, your identity provider handles sign-in and your organization manages security settings. ### 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 decentralized teams usually combine the two 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. * **Split by responsibility**: Creator for members who prepare orchestrations, Publisher for those who review and launch them. * **Split by channel or orchestration type**: custom permissions for teams dedicated to one channel, or for profiles who only need Settings or Privacy. * **Open in read-only**: the **Viewer** role for stakeholders who need visibility on what is being sent. {% 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 %} {% hint style="warning" %} **If your company still uses the MEP**, roles per project are not available yet. Permissions follow the previous model below. {% endhint %}
Previous permissions model **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 %} **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 %}
## 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 . 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 () 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. ). ### How Can I Delete My Account? Just ask us to delete your account at . 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 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/features/customer-engagement-platform/settings/manage-team.md?ask=&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.