# Consent Handling in JENTIS ### Introduction to Consent Handling in JENTIS One major difference between JENTIS and other tag management systems is that **JENTIS actively maintains and manages the consent situation**. This means customers do not need to handle consent logic for individual tools within triggers. JENTIS introduces a dedicated abstraction layer that links each tool to its corresponding vendor. Vendor consents are then mapped by the Consent Management Platform (CMP) implemented on your site. Once your CMP is connected to JENTIS and its decisions are mapped to vendors, **JENTIS automatically determines which tools are allowed to run and which are not**—no extra trigger logic required. This approach significantly **reduces configuration effort** and makes ongoing **maintenance much easier**. In the following section, we will explain: * How JENTIS handles consent decisions in detail * Our caching mechanisms * Reprocessing strategies Our goal is to make it as clear and straightforward as possible how JENTIS manages consents for your tools. --- # Agent Instructions: 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: ``` GET https://docs.jentis.com/consent-center/how-jentis-handles-consent.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.