> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/getting-started/use-cases.md). # Use cases Do you know who has access to your SaaS data? Knowing “who has access” and “to what” is an organizational challenge when one considers the high number of applications and users, together with the large volume of generated events. SaaS applications make it simple for employees to share information and collaborate with external parties, such as vendors, prospective customers, partners, contractors and temporary employees. But this convenience often comes at the cost of security. The complexity of business needs and requirements cannot all be quantified by security teams. The end result is unmanageable data access that poses significant risk to your organization and increases the likelihood of a data breach. By replacing manual work with automation, DoControl reduces the overload of work and complexity that security teams continually struggle with. The DoControl platform addresses a vast number of data access use cases for organizations leveraging SaaS applications. Use case scenarios from major SaaS security domains include: * [Data access governance ](/docontrol-user-guide/getting-started/use-cases/data-access-governance.md) * [Data loss prevention](/docontrol-user-guide/getting-started/use-cases/data-loss-prevention.md) * [Insider risk management](/docontrol-user-guide/getting-started/use-cases/insider-risk-management.md) * [Shadow app discovery and remediation](/docontrol-user-guide/getting-started/use-cases/shadow-app-discovery-and-remediation.md) * [Misconfiguration management](/docontrol-user-guide/getting-started/use-cases/misconfiguration-management.md) --- # 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://docs.docontrol.io/docontrol-user-guide/getting-started/use-cases.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.