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

# Box users

Internal users belong to your organization's Box platform and operate within the organization domains or subdomains. 

After you filter a specific user's assets, you can [generate a CSV report](#generate-csv-report) or [remediate exposure](#remediate-asset-exposure) for specific assets. The internal users page displays the following data:

* [Internal user list](#internal-user-list)
* [Internal user details](#internal-user-details)
* [Assets](#assets)
* [Events](#events)

{% hint style="info" %}
Data is displayed only for internal users in Box, not external users.
{% endhint %}

## Locate an internal user

To view personal details, asset and event data for a specific internal user in Box:

1. From the DoControl side menu, click **Inventory** > **Users**.
2. Select **Box**.<br>

   <div align="left"><figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F3S9tYCQVQKtwiCkAN300%2Fselect%20user%20app.png?alt=media&amp;token=f22a5f98-aa47-45aa-968b-86b8da1fbf1f" alt="" width="221"><figcaption></figcaption></figure></div>
3. Filter for a specific user.
4. Click the user's **email address** to open the internal user details.
5. Click any **app** icon to display user details, assets and events for that SaaS app.

## Internal user list

All internal users in your Box platform are displayed with these parameters:

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FRh4AwGV60I7jADzby24Y%2FBox%20users.png?alt=media&amp;token=8e9fbab3-aa47-4d3d-a1b5-abf7983d02be" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="223.87890625">Internal user parameter</th><th>Description</th></tr></thead><tbody><tr><td>Email</td><td>Internal user's email address. Click the email to open the internal user details with asset and event data. </td></tr><tr><td>First name</td><td>Internal user's given name</td></tr><tr><td>Last name</td><td>Internal user's surname</td></tr><tr><td>Role</td><td>Indication if the user is a Box admin or co-admin user</td></tr><tr><td>Created on</td><td>Date when the user was created in Box</td></tr><tr><td>Updated on</td><td>Date when the user was updated in Box</td></tr></tbody></table>

{% hint style="success" %}
Click **Export to CSV** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FPWdaV30qx1aefHNdGX9C%2Fdownload%20icon.png?alt=media&amp;token=16257bf4-2b68-4417-91e6-78c5db741fdc" alt="" data-size="line"> to download a consolidated report of internal Box users in CSV format.
{% endhint %}

## Internal user details

Metadata for a specific internal user in Box is displayed as follows:

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FT216pV3fsF2KpzZyrKpH%2FBox%20internal%20user%20details.png?alt=media&amp;token=30437c8b-ebfd-4876-9a46-06705ff92609" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="271">Internal user detail</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Internal user name</td></tr><tr><td>Email </td><td>Email of internal user</td></tr><tr><td>Phone</td><td>Phone number of internal user</td></tr><tr><td>Related active alerts</td><td>Number of active alerts where this user is the actor. Click <strong>View</strong> to open the Alerts page filtered for this user's alerts.</td></tr></tbody></table>

## Assets

View and filter metadata for an internal user's Box assets.

1. From the DoControl side menu, click **Inventory** > **Users**.
2. Select **Box**.
3. Filter for a specific user.
4. Click the user's **email address** to open the internal user details.
5. Scroll down to view metadata for the user's Box assets.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FanJXaMd1p2bWysWD9hSA%2FBox%20asset%20details.png?alt=media&amp;token=07c52dd4-6cb6-4a26-8bdd-70115c7ab61d" alt=""><figcaption><p>Asset details for a specific internal user in Box</p></figcaption></figure>

The metadata displayed for an internal user's Box assets includes these parameters:

<table><thead><tr><th width="189.2265625">Asset parameter</th><th>Description</th></tr></thead><tbody><tr><td>Name</td><td>Name of file in Box. Click the link to open the individual asset page.</td></tr><tr><td>Owner</td><td>Email address of asset owner. Click the link to open the user page.</td></tr><tr><td>Collaborators</td><td>Internal or external collaborators who have access to assets in your organization</td></tr><tr><td>Sharing status</td><td><p>If the asset is shared or not: </p><ul><li>No sharing link</li><li>Invited people only </li><li>People in your company</li><li>People with the link </li><li>Internal</li><li>External</li></ul></td></tr><tr><td>Last viewed by</td><td>Email address of the internal or external actor who last viewed the asset</td></tr><tr><td>Last viewed at</td><td>Date when the asset was last viewed</td></tr><tr><td>Modified at</td><td>Date when the asset was updated</td></tr><tr><td>Last modified by</td><td>Email address of person who updated the asset</td></tr><tr><td>Asset path</td><td>Relative path of the asset owner in Box</td></tr></tbody></table>

### Generate CSV report

You can generate a report for selected asset metadata in CSV format.

1. Select the relevant assets.
2. Click the **Export to CSV** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FPWdaV30qx1aefHNdGX9C%2Fdownload%20icon.png?alt=media&amp;token=16257bf4-2b68-4417-91e6-78c5db741fdc" alt="" data-size="line"> icon.\
   A consolidated report of asset metadata is downloaded in CSV format.

### Remediate asset exposure

Inventory actions are supported for assets with sharing links or that are externally shared.

You can apply [inventory actions](/docontrol-user-guide/workflows/inventory-actions-quick-actions.md) to Box assets, in order to manually trigger on-demand remediation actions to resolve specific issues. Click **Remediate** to apply these inventory actions to selected Box assets:

* [Remove sharing link](/docontrol-user-guide/workflows/inventory-actions-quick-actions/box-inventory-actions.md#remove-sharing-link)
* [Remove external collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/box-inventory-actions.md#remove-external-collaborators)
* [Remove all collaborators](/docontrol-user-guide/workflows/inventory-actions-quick-actions/box-inventory-actions.md#remove-all-collaborators)

## Events

DoControl monitors real-time events of user activities in Box. If no date range is selected, events are displayed from the last 30 days.

#### To view events for a specific internal user:

1. From the DoControl side menu, click **Inventory** > **Users**.
2. Select **Box**.
3. Filter for a specific user.
4. Click the user's **email address** to open the internal user details.
5. Scroll down to view metadata for the user's events in Box.

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FJQAmb1KdQwihBO59jeGt%2FBox%20event%20details.png?alt=media&amp;token=a6b1dac5-0344-4a3c-a1ae-9ecb7fcf9421" alt=""><figcaption></figcaption></figure>

The metadata displayed for a user's events in Box includes these parameters:

<table><thead><tr><th width="271">Event parameter</th><th>Description</th></tr></thead><tbody><tr><td>Date and time</td><td>When the event occurred</td></tr><tr><td>Actor </td><td>The user who triggered the event</td></tr><tr><td>Target</td><td>The user whom the actor shared data with</td></tr><tr><td>App</td><td>App involved in the event: Box</td></tr><tr><td>Asset</td><td>Name of the asset involved</td></tr><tr><td>Event type</td><td>Type of event as defined in Box (Copy, Content access, etc)</td></tr><tr><td>Triggered</td><td>Number of workflows or alerts that were triggered by this event</td></tr><tr><td>Event ID</td><td>Unique identifier for the event</td></tr><tr><td>Event JSON</td><td>Click to open the JSON file with raw details about the event</td></tr></tbody></table>

{% hint style="success" %}
Click **Export to CSV** <img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FPWdaV30qx1aefHNdGX9C%2Fdownload%20icon.png?alt=media&amp;token=16257bf4-2b68-4417-91e6-78c5db741fdc" alt="" data-size="line"> to download a consolidated report of event metadata for a specific Box user.
{% 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/box-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.