> For the complete documentation index, see [llms.txt](https://help.nightfall.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.nightfall.ai/salesforce/getting-started.md). # Getting Started A walk through of how to install Nightfall's DLP solution for Salesforce. Nightfall's Salesforce integration allows you to scan updates to objects and fields in real-time across sandbox and production organizations in Salesforce. \ \ This getting started guide will walk you through installing and upgrading the components of the solution. {% hint style="warning" %} Salesforce vertical cloud offerings are not supported as of today. {% endhint %} Nightfall's Salesforce integration allows you to scan updates to objects and fields in real-time across sandbox and production organizations in Salesforce. \ \ This getting started guide will walk you through installing and upgrading the components of the solution. Nightfall DLP for Salesforce supports the following Salesforce Sales Cloud editions across both production and sandbox instances: * Enterprise * Unlimited * Developer Salesforce vertical cloud offerings are not supported as of today. You can install and authorize Nightfall DLP app package in Salesforce production environments. You can view and remediate Salesforce DLP policy violations within the Nightfall dashboard and violations monitoring page. --- # 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://help.nightfall.ai/salesforce/getting-started.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.