# Vendor Consent Settings

In **JENTIS Tag Manager**, every vendor has a dedicated **Consent Settings** option.\
These settings determine **how and when** a vendor’s tools are activated, based on your consent configuration.

This allows you to control whether a vendor’s tools require user consent before running, and if so, how they behave in different consent scenarios.

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2F73I1KMbNPuLNCJs2S1xH%2Fimage.png?alt=media&#x26;token=6be6fca5-bbf1-4eb9-95d2-1b957bb3073f" alt=""><figcaption></figcaption></figure>

### Available Modes

#### 1. Consent Mode

* **Behavior:** Tools linked to this vendor activate **only after user consent is received**.
* **Use case:** When you must strictly follow the user’s opt-in decision for compliance.

#### 2. Essential Mode

* **Behavior:** Allows a **split configuration** for each tag in this vendor’s tools:
  * One configuration when **consent is given**
  * Another configuration when **consent is denied**
* **Use case:** When essential functions must still run without full tracking, but enhanced features should only run after consent.

#### 3. No Consent Mode

* **Behavior:** The tool activates **immediately**, regardless of user consent.
* **Use case:** For tools that are legally permitted to run without consent (e.g., certain strictly necessary services).

✅ **Tip:**\
Carefully review the legal requirements in your jurisdiction before choosing **No Consent Mode**. This ensures that your configuration remains compliant with applicable data protection regulations.