> For the complete documentation index, see [llms.txt](https://docs.chatlayer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chatlayer.ai/support/access-control.md).

# Identity & Access

## User Accounts

### Sinch ID

Chatlayer is moving to **Sinch ID**, a unified Sinch sign-in experience that will gradually replace the current account system. The rollout is incremental: **all new accounts now use Sinch ID**, while existing users keep signing in as before. No action is required from existing users.

* **Signing in:** Enter your email address on the sign-in screen. Chatlayer automatically detects whether your account uses Sinch ID or the classic login and redirects you accordingly.
* **New accounts:** When you sign up or accept a team invitation, your account is created in Sinch ID. Password setup, password reset, and email verification are all handled through the Sinch ID sign-in screens.
* **Password policy & brute force protection:** Sinch ID accounts follow Sinch ID's own password requirements and sign-in protection, which are managed and enforced by Sinch ID.

[SAML SSO](/support/access-control/single-sign-on-sso-saml.md) remains available and is unaffected by this change.

### Password Sign-In (legacy)

Existing users who were created before the Sinch ID rollout sign in with their email address and password.

Our password policy is:

* A minimum of 8 characters.
* At least one lowercase character.
* At least one uppercase character.
* At least one special character.

Our platform is protected by a brute force detection system. We allow a maximum of **10 failed sign-in** attempts before locking out the account. The lockout period starts at 1 minute and increments by 1 minute per lockout, up to 15 minutes.

Contact <support@chatlayer.ai> if you need assistance with your user account.

### Other Sign-In methods

If you want more control over team access and user accounts and their sign-in methods we recommend setting up [SAML SSO](/support/access-control/single-sign-on-sso-saml.md).

## Team Access

### Managing Team Members

In the **Settings > Members** module you can add or remove users from your team.

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

When you add a new user to your team, they will receive an invitation email to sign up via Sinch ID. The user appears as **(pending)** in the members list until they accept the invitation and complete sign-up. If the email already belongs to an existing Sinch ID user, they are added to the team directly without an invitation. Users who belong to multiple Chatlayer teams can switch between them using the team selector in the top left of the platform.

<div align="center"><figure><img src="/files/zSX4uMYC0gANnp8hRsL5" alt="" width="369"><figcaption><p>Switch teams by selecting the team from the teams dropdown</p></figcaption></figure></div>

### Team Member Roles

{% hint style="info" %}
Team roles & bot access is only available in the Enterprise pack or higher. Want to upgrade?\
[Get in touch](/support/get-in-touch.md).
{% endhint %}

Chatlayer.ai has a role-based access system that allows you to restrict specific bots for specific users, and give specific rights per bot.

A user can either be an admin or a member of the team. A member's role cannot be edited after they are added. To change someone's role, remove the user from the team and add them again with the new role.

An overview of the differences between both roles:

* **Admins** have access to all bots and can create or delete team members.
* **Members** can only access OPEN bots or RESTRICTED bots to which they have access to. They cannot create or delete new team members.

## Bot access

Bots can either be set as OPEN or RESTRICTED. An OPEN bot can be accessed by all team members. RESTRICTED bots can only be accessed by Admins and approved Members.

You can configure the access to your bot while you're creating the bot:

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

You can change the Bot Access configuration for an existing bot by selecting "Change Access" in the **Bot > Settings > Bot Settings** module:

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

Changing your Bot Access to RESTRICTED enables a new menu entry: **Bot > Settings > Access**.\
You can configure which team members have which access to the bot on this page.

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

A member can have one of five types of permissions to a RESTRICTED bot:

* **Edit:** the member can change all intents, blocks and settings.
* **Read-only:** the member can view the bot, but cannot change anything.
* **NLP-only:** the member can change intents, expressions, entities, etc, but not blocks or settings.
* **Bot Builder:** the member can see and edit everything except for the conversation history in DRAFT and LIVE.
* **Copywriter:** the member can see everything, but can only change the translations (the responses of the bot) in the translations window.

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

Your access level to a bot can be seen on the "My Bots" overview page. Restricted bots will have a locked icon and, on that same line, you will be able to read your type of permission to it:

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


---

# 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://docs.chatlayer.ai/support/access-control.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.
