> 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/overview/how-does-it-work.md).

# How it works

DoControl is an agentless automated solution that operates behind the scenes on your behalf.

## SaaS application security insights and management

DoControl opens a window that provides comprehensive visibility of all the [assets](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets.md) that you have in the connected SaaS apps. DoControl also visualizes all [users](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users.md): employees, admins, and external users who access, share, and manipulate data stored in multiple SaaS applications.

After your SaaS apps have been [integrated with DoControl](/docontrol-user-guide/getting-started/quick-start.md) (it only takes a few clicks), DoControl starts collecting ongoing snapshots of various types of SaaS apps asset data, such as users, files, applications, domains and more.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F7fTG3PG5eis4BtLE367y%2Fnewposture.gif?alt=media&amp;token=6795746d-17d2-4412-9aee-c3b7f9ec4ffd" alt=""><figcaption><p>Google Workspace posture page</p></figcaption></figure>

## Continuous monitoring of near-realtime events

After your SaaS applications have been integrated with DoControl, various end-user activity events (share, download, create, view, edit and so on) are pushed directly to DoControl in near-realtime by the connected SaaS applications. DoControl enriches incoming events’ metadata, without accessing raw content. &#x20;

DoControl comes with a rich variety of anomaly detection capabilities in order to automatically detect various suspicious user activities and trigger alerts, such as –

* Sharing numerous assets to a personal Gmail account
* Publicly sharing certain assets
* Sharing large quantities of assets
* External sharing last day
* Extensive sharing in a short period (Burst)
* Public sharing last day
* Extensive public sharing&#x20;
* Share with private email
* Share with personal email
* External user share with private email
* Share with 4th party
* External user share public
* Extensive download

DoControl provides in-depth, drill down detailed information that enables you to analyze and investigate each event. DoControl also sends you a weekly summary report describing the latest SaaS application data exposure status and user activity, such as public sharing, external sharing, user activity and more.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F3UpouhR2gI8kuwc0uTmf%2Fminidashboard.gif?alt=media&amp;token=d2aefc86-e55d-41a7-9090-ad670577dc52" alt=""><figcaption><p>DoControl alerts page with mini-dashboard</p></figcaption></figure>

## Automated policy-based workflows&#x20;

In addition to the automatically detected and alerted anomalies, DoControl enables you to define policy workflows that monitor SaaS application user activities and that automatically perform a series of actions when the conditions of the policy are matched, such as **Wait**, **Notify**, **Enforce** and **Approve**. These policies enable you to automate consistent controls across all the SaaS applications that you integrate with DoControl and provides additional security capabilities that don't exist in many SaaS applications.

DoControl makes it easy to define these policies by providing a variety of templates for handling various security situations. For example –

* DoControl enables you to define different levels of exposure for sharing. For example, you can define different sharing policies for internal employees, external collaborators/partners/vendors and for the general public.
* Upon a matching incoming event, DoControl will proactively make API calls to the relevant SaaS applications in order to enforce policies. Notifications are pushed to popular platforms, such as Slack.
* DoControl makes it easy to create tickets, incidents, and compliance evidence in existing IT tools.
* DoControl enables you to define various policies for automatic permission control of assets according to their age. For example, to specify that a certain asset’s access permissions are removed after a week.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FFqS2sj72kqs7r0BeGfHz%2F30daysgraph.gif?alt=media&amp;token=3de55ede-213d-480a-8550-047349c600e9" alt=""><figcaption><p>DoControl workflows automatically monitor and remediate risky SaaS activity </p></figcaption></figure>


---

# 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/overview/how-does-it-work.md?ask=<question>&goal=<user_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.
