> This page is for Applications Protection.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.humansecurity.com/llms.txt.

# Manage applications

After you [add an application,](/applications/add-applications) you can manage its settings and view its information from its **status and settings.** You can learn more about the information available with this article.

## View an application's settings

1. Navigate to **Platform Settings > Applications > Overview.**
2. Click on the application you want to manage.

## Application status

The **Application status** section provides the application's name and

Application ID

, which you can use to reference quickly as needed.

## Application settings

**Application settings** has configurable fields that you can update as needed.

### Application details

**Application details** has basic information about the application. You find the following information here:

* **Application name:** The name of the application and how it appears in HUMAN. You can change this as needed. Be sure to click **Save changes** after updating it.
* **Description:** A description of the application. You can update this as needed. Be sure to click **Save changes** after updating it.
* **Application ID:** The application's unique identifier assigned by HUMAN. This ID is used for other configurations related to your application, such as the Enforcer. You can **copy** this ID as needed.
* **Application type:** The type of application its assigned, either production or staging.

### Integration details

**Integration details** provides information about the application's Sensor and Enforcer configurations.

#### Integration

The **Integration** section has details about the JavaScript snippet that should be deployed to your application. It has the following information:

> **Note**
>
> See [Getting started](/applications/getting-started-with-sightline-cyberfraud-defense#2-integrate-the-sensor) for more on deploying the Sensor snippet.

* **Integration type:** The type of snippet, either 1st party or 3rd party, currently used by your application. Click **Change to 1st/3rd Party Integration** to switch the type as needed. If you're not sure which type to use, [contact us](/applications/human-customer-support) for assistance.
* **Snippet:** The 1st or 3rd party JavaScript snippet to deploy to your application's `<head>`. You can **copy** the snippet for convenience.

#### Enforcer/Sensor

The **Enforcer/Sensor** section has details about the application's deploy Enforcer and Sensor as well as their versions.

* **Enforcer:** Lists your deployed Enforcer and its version. You can click on the Enforcer to navigate to its [configuration settings.](/applications/enforcers)
* **JS Sensor:** The Sensor version and type deployed to your application.

### Server token

The **Server token** section lists all your server tokens for the application. Server tokens identify your server when using API calls between your server and HUMAN's. You can hover over a token to **copy** it. You can have up to three tokens per application.

To add a token:

1. Navigate to **Application settings > Server token.**
2. Click **+ Add server token.** This generates a new server token for you.

To delete a token:

> **Warning**
>
> If you have an existing Enforcer configuration for this application, ensure that the Enforcer is **not** using the server token you're deleting. Deleting a server token that's currently in use may disrupt Enforcer functionality. To swap your Enforcer's current token with a new one, see [Rotate application server tokens & cookie keys.](/applications/rotate-server-tokens-and-cookie-keys)

1. Hover over the token you want to delete.
2. Click the **more options** icon.
3. Click **Delete token.**
4. In the confirmation dialog that appears, click **Delete.**