<commit_before>---
section: appliance
---

# Auth0 Appliance Administration: Managing the Dashboard

### Accessing the Dashboard

The [Auth0 Dashboard](/appliance/dashboard) uses the Auth0 Appliance to authenticate its users.

Within the list of applications, you will see the Auth0 Application, which represents the Dashboard itself. It uses a connection called `Initial-Connection`, which stores the credentials of the administrators that have access to the Dashboard.

> Changes to the Auth0 application or `Initial-Connection` may result in unexpected Dashboard behavior. Please makes changes with caution.

Because the Dashboard uses the Appliance for authentication, any configured rules will run whenever a user accesses the Dashboard. Because errors in one or more of your rules may result in you losing access to the Dashboard, Auth0 suggests writing rules that exclude the Auth0 application:

```js

function (user, context, callback) {
    if (context.clientName === 'Auth0') {
      return callback(null, user, context);
    }

    // Your code.

    callback(null, user, context);
}

```

> The default user `<EMAIL>` has access to the Appliance and its configuration area. Please remember to reset this user's default password or disable the user via the Auth0 Dashboard.

### Restricting Access to the Dashboard

Because the Dashboard uses the Appliance to authenticate users, the Dashboard is using Connections, [Rules](/rules), and so on, just like any other application you might add in the future.

As a result, you have several options for restricting access to the dashboard, including, but not limited to:

* writing rules to allow users only from a specific IP address;
* writing rules to allow only co-administrators of the Appliance to authenticate using their Active Directory (via either ADFS or AD Connector).
<commit_msg>Add warnings<commit_after>---
section: appliance
---

# Auth0 Appliance Administration: Managing the Dashboard

### Accessing the Dashboard

::: panel-warning
The **Auth0** client in the Root Tenant Authority (RTA) controls access to the Management Dashboard, and the only Connections that you should enable for this client is the built-in Database Connection or an enterprise connection like the AD-LDAP Connector. You should **never** enable a Social Connection for the **Auth0** client.

Additionally, please [disable signups](/appliance/admin/disabling-sign-ups) for the **Auth0** client.
:::


The [Auth0 Dashboard](/appliance/dashboard) uses the Auth0 Appliance to authenticate its users.

Within the list of applications, you will see the Auth0 Application, which represents the Dashboard itself. It uses a connection called `Initial-Connection`, which stores the credentials of the administrators that have access to the Dashboard.

::: panel-warning
Changes to the Auth0 application or `Initial-Connection` may result in unexpected Dashboard behavior. Please makes changes with caution.
:::

Because the Dashboard uses the Appliance for authentication, any configured rules will run whenever a user accesses the Dashboard. Because errors in one or more of your rules may result in you losing access to the Dashboard, Auth0 suggests writing rules that exclude the Auth0 application:

```js

function (user, context, callback) {
    if (context.clientName === 'Auth0') {
      return callback(null, user, context);
    }

    // Your code.

    callback(null, user, context);
}

```

> The default user `<EMAIL>` has access to the Appliance and its configuration area. Please remember to reset this user's default password or disable the user via the Auth0 Dashboard.

### Restricting Access to the Dashboard

Because the Dashboard uses the Appliance to authenticate users, the Dashboard is using Connections, [Rules](/rules), and so on, just like any other application you might add in the future.

As a result, you have several options for restricting access to the dashboard, including, but not limited to:

* writing rules to allow users only from a specific IP address;
* writing rules to allow only co-administrators of the Appliance to authenticate using their Active Directory (via either ADFS or AD Connector).

{'fraction_non_alphanumeric': 0.06248503710797223, 'fraction_numerical': 0.005027531721331099, 'mean_word_length': 4.630727762803234, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 8, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3864832', 'n_tokens_mistral': 1042, 'n_tokens_neox': 990, 'n_words': 565}