> 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-users.md).

# Users

DoControl inventory displays all users who can access, share, and manipulate data stored in your organization's integrated SaaS apps for these user types:

* **Internal users** - Users who belong to your organization and operate within the organization domains or subdomains.&#x20;
* **External users** - Users who are outside your organization, but have access to your files. For external users, you can view user details, asset and event data for these SaaS apps:
  * [Google Workspace](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/google-workspace-users/external-users.md)
  * [GitHub](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/github-users.md#github-external-users)
  * [OneDrive](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/onedrive-users/onedrive-external-users.md)
  * [SharePoint](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/sharepoint-users/sharepoint-external-users.md)
  * [Slack](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/slack-users/slack-external-users.md)
  * [Teams](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/teams-users/teams-external-users.md)

From the Users page you can filter by SaaS app, and then by internal or external users. Drill down to get information about a specific user, and perform **inventory actions** to remediate any potential exposure issues.&#x20;

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fj044XBTvphSusg0i6FXG%2FInternal%20users.png?alt=media&amp;token=6437938f-0b2f-415a-a847-8054d8a860da" alt=""><figcaption><p>Filter users by SaaS app</p></figcaption></figure>

Users are displayed according to SaaS app:

* [Google Workspace](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/google-workspace-users.md)
* [Slack](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/slack-users.md)
* [Box](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/box-users.md)
* [GitHub](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/github-users.md)
* [HRIS](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/hris-users.md)
* [OneDrive](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/onedrive-users.md)
* [SharePoint](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/sharepoint-users.md)
* [Teams](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/teams-users.md)
* [Zoom](/docontrol-user-guide/saas-data-monitoring/inventory/inventory-users/zoom-users.md)

{% hint style="info" %}
The **Google Workspace > Internal users** tab is displayed by default. You can customize which user view is displayed in [inventory views](/docontrol-user-guide/saas-data-monitoring/inventory.md#inventory-views).
{% endhint %}


---

# 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-users.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.
