> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/settings/enterprise-security.md). # Enterprise Security Learn about DoubleTick enterprise security controls and related configuration options. **Available on:** Enterprise plan\ If you're on the **Pro plan**, you can purchase the **Enterprise Security add-on**. Contact your Account Manager or go to **Billing & Invoices → Purchase Add-on** to purchase it directly for your Pro plan. Enterprise Security in DoubleTick is designed to help organizations protect sensitive data and control access to their workspace. It includes advanced security capabilities such as **PII Protection** and **IP Access Control**. PII Protection allows businesses to detect and handle sensitive customer information in conversations by masking or blocking it using their own Security API. IP Access Control strengthens account security by allowing access only from approved networks or IP addresses. Together, these features help organizations safeguard customer data, enforce internal security policies, and maintain stronger control over how their DoubleTick workspace is accessed and used. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.doubletick.io/settings/enterprise-security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.