> 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/saas-data-monitoring/inventory/inventory-domains.md). # Domains DoControl displays your organization's shared assets across different domain types: * [External domains](#external-domains) * [Internal domains](#internal-domains) * [Trusted domains](#trusted-domains) You can define workflows for each domain where assets are shared. By not sharing assets with untrusted domains, you limit your organization's external exposure and mitigate the external risk of multi-SaaS data and permissions sprawl. You can leverage these functions in domain pages:
ButtonFunctionDescription
Add filter

Display your internal domains according to:

  • Domain
  • Environment that manages domain
Sort Sort column according to alphabetical order.
SearchSearch in current loaded results. You can load more pages if needed.
DownloadDownload displayed domains to a CSV file.
View eventsOpens the Events page showing user activities in the specified domain.
{% hint style="info" %} Learn more about configuring trusted domains with [DoControl videos](/docontrol-user-guide/help/videos.md#domains-and-trusted-ips). {% endhint %} ## **External domains** External domains are domains with external users who have access to assets in your organization. For external domains, DoControl displays these columns:
ColumnDescription
DomainName of the external domain
AppsAll apps that external users have access to
Total collaboratorsNumber of external users with access to your organization
Total collaborationsNumber of external shares on all assets within a specific domain
{% hint style="info" %} Currently DoControl supports external domains for Google Workspace and Slack apps. {% endhint %} ### Total collaborators Total collaborators is the number of external users with access to your organization's assets. For example: * Asset A is shared with * Asset B is shared with The total number of collaborators is 1. ### Total collaborations Total collaborations is the number of external shares on all assets within a specific domain. For example: * Asset A is shared with and * Asset B is shared with and The total number of collaborations is 4. ## Internal domains Internal domains are managed by your organization. For each internal domain, DoControl displays the environment where the domain is managed, such as Google Workspace, Office 365, or DoControl. {% hint style="warning" %} You can't remove internal domains, since they are trusted by definition. {% endhint %} ## Trusted domains Trusted domains are a subset of internal and external domains that are considered safe for sharing. All internal domains are automatically listed as trusted domains. {% hint style="success" %} Tip: You need to define a list of trusted domains before creating [workflow conditions](#use-trusted-domains-in-workflow-conditions) that refer to trusted domains. {% endhint %} For each trusted domain, DoControl displays the environment where the domain is managed, such as Google Workspace, Office 365, or DoControl. There are two ways to add trusted domains: * [Add external domains as trusted](#add-external-domains-as-trusted) * [Add domains from other sources](#add-domains-from-other-sources) ### Add external domains as trusted External domains that were added to your trusted domains are tagged with the **trusted domain** icon. 1. Select **Inventory > Domains and IPs > Domains > External**. 2. Select the relevant external domain(s). 3. Click the **Mark as trusted domains** button.\ The selected domains now appear in both the **External** and the **Trusted** domain tabs.
### Add domains from other sources You can add a single domain or a list of external domains that are managed elsewhere, such as a spreadsheet. {% hint style="info" %} You can add up to 1000 trusted domains. {% endhint %} 1. Select **Inventory > Domains and IPs > Domains > Trusted**. 2. Click **+Add trusted domains**. 3. Enter or paste domains in one of these formats: * domain.com * sub.domain.com 4. For multiple domains, you can paste comma-separated values or values from a spreadsheet. Use the **Tab** or **Enter** keys to separate between domains. 5. Click **Save**. The new domains now appear in the **Trusted** tab.
### Remove trusted domains You can remove a domain from the list of trusted domains. For example, if your organization stops working with a specific vendor, you can remove the vendor's domain from the list of trusted domains. 1. Select **Inventory > Domains and IPs > Domains > Trusted**. 2. Select the domains to remove. 3. Click **Remove from trusted domains**. After confirmation, the selected domains are removed from the Trusted domain tab.
### Use trusted domains in workflow conditions After you define your list of trusted domains, you can use them as conditions in workflows. 1. Define your organization's list of trusted domains. See [trusted domains](#trusted-domains). 2. Create a workflow; for example with a change user access event. 3. Add a condition that checks if the asset was shared with a domain from the non-trusted domains list. 4. Use either one of these comparators to filter specific domains: * In trusted domains: True or false * Not in trusted domains: True or false --- # 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/saas-data-monitoring/inventory/inventory-domains.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.