> For the complete documentation index, see [llms.txt](https://docs.coherence.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coherence.io/2.4/hosting/self-hosting/restricted-mode-and-unlock-token.md).

# Restricted mode and Unlock Token

Running the Replication Server without providing the Unlock Token will make it run in restricted mode. In this mode, the maximum number of connected players is limited to 100.

To avoid this limit, an Unlock Token must be provided for both world and rooms mode using the `--unlock-token` CLI argument.

{% hint style="info" %}
The Unlock Token can also be provided through an environment variable named `COHERENCE_UNLOCK_TOKEN` instead.
{% endhint %}

To get an Unlock Token, you must create an account and a project in the [coherence Cloud](/2.4/hosting/coherence-cloud.md) and then in the *Settings* section of the selected project, generate the token under the Unlock Token.

{% hint style="danger" %}
The Unlock Token is a **private secret** and must never be exposed publicly - do not embed it in client-side code, commit it to version control, or share it in public channels. Anyone with access to the token can use it on your behalf.

Additionally, client-hosted mode should **not** use the Unlock Token and should run in the restricted mode. The Unlock Token should only be used when running the Replication Server in a trusted server-side environment.
{% endhint %}