> 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/quick-start/onboard-docontrol.md). # Onboard DoControl Once you've [set up your DoControl basics](/docontrol-user-guide/getting-started/quick-start/set-up-docontrol-basics.md) and integrated your [SaaS apps](/docontrol-user-guide/getting-started/quick-start/set-up-docontrol-basics.md#integrate-saas-apps-with-docontrol), you're ready to onboard DoControl:
## Prioritize assets Before you get running with DoControl, it's important to filter and inspect your assets: what SaaS apps in your organization require the most attention? From the Assets page, you can gain insight into the exposure for each asset (what is shared, and with whom). DoControl enables you to manage and clean up your assets in various ways: * Filter assets according to app-specific options. * View detailed information about a [specific asset](#individual-assets), including sharing status (for example, shared internally or externally) * Perform [inventory actions](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md) per asset or in [bulk](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md#bulk-actions), such as: * Remove public sharing for a large number of files * Remove specific collaborator * Remove external collaborators * Change asset ownership {% hint style="success" %} Tip: Learn more about the [sharing statuses](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets.md#sharing-status) for each app and how to [filter assets.](/docontrol-user-guide/risk-management/alerts/filter-alerts.md) Continue to the next stage to [configure alerts](#configure-alerts). {% endhint %} ## Configure alerts DoControl will send you notifications when an alert is triggered due to anomalous behavior, or as part of a workflow process, such as Decide or Approve. You can also customize settings for each alert type, and choose whether or not to be notified for each alert type. #### To configure alerts: 1. Enable email and Slack notifications so that your users will receive DoControl alert notifications. See [alert settings](/docontrol-user-guide/system-management/settings/alert-settings.md).

In DoControl, go to Settings > Alerts > General to enable alert notifications

2. Customize these alert settings for each alert type: * **Enable or disable** - Enable or disable all alerts of this type in all your integrated apps * **Severity** - High, Medium, or Low according to the threat model in your organization. * **Exclude actors** - Define actors who will not trigger the alert type. * **Exclude targets** - Define targets who will not trigger the alert type. {% hint style="success" %} Tip: To define alert parameters, see [Configure alerts](/docontrol-user-guide/risk-management/alerts/configure-alerts.md). {% endhint %} 3. Continue to the next stage to [set up keyword lists](#set-up-keyword-lists). ## Set up keyword lists DoControl provides default keyword lists for scanning. You can customize these lists or build your own according to your organization's requirements, and include or exclude them when defining workflows. DoControl keyword lists include: * **Encryption key file** - A set of file extensions that indicate a file has been encrypted. * **Ransomware encryption file** - Common ransomware file extensions. * **Private email domains** - A set of private, non-corporate email domains. These domains can be used to trigger a workflow if assets are downloaded or shared with such domains, or an alert if a company asset is shared with an actor having a private email domain. * **Sensitive keyword list** - A set of words indicating PII (personally identifiable information) or company proprietary information. For example, an alert is triggered if a sensitive keyword is detected in the asset name. {% hint style="success" %} Tip: After you define your keyword lists, you can use them as [conditions](/docontrol-user-guide/workflows/define-workflow-settings/trigger-settings.md#conditions) in workflows. To customize keyword lists, see [Lexical lists](/docontrol-user-guide/system-management/settings/lexical-lists.md). Continue to the next stage to [define a workflow](#define-a-workflow). {% endhint %} ## Define a workflow Workflows are a flexible and visual way to automatically monitor, control and remediate data access across all your SaaS applications. Use DoControl's visual drag-and-drop canvas to set up your first workflow. You can create workflows to support a large number of possible events, user actions, conditions and remediation actions. Alternatively, choose a predefined workflow from a rich catalog of playbooks, and customize it to address the security policies and use cases in your organization. Workflows are flexible and granular enough to detect almost any malicious or anomalous behavior a user is doing, near real-time, in a specific SaaS application. {% hint style="success" %} Tip: When you build your first workflow, think about which use cases in your organization you want to prioritize, and which SaaS assets you want to prioritize for remediation. {% endhint %} {% hint style="info" %} Note: To set up a workflow, you need to: * [Create a new workflow](/docontrol-user-guide/workflows/create-a-workflow.md) * Define [general settings](/docontrol-user-guide/workflows/define-workflow-settings.md) * Define workflow [triggers](/docontrol-user-guide/workflows/define-workflow-settings/trigger-settings.md) and [conditions](/docontrol-user-guide/workflows/define-workflow-settings/trigger-settings.md#conditions) * Define [action settings](/docontrol-user-guide/workflows/define-workflow-settings/action-settings.md) {% endhint %} After you've onboarded, you can fully leverage DoControl capabilities and continue with ongoing DoControl activities: * Define [trusted domains](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-domains.md) and [trusted IPs](/docontrol-user-guide/saas-data-monitoring/inventory/trusted-ips.md) * Create [email templates](/docontrol-user-guide/system-management/settings/email-templates.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/quick-start/onboard-docontrol.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.