> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/administration/system-configuration/data-management.md).
# Data management
{% hint style="info" %}
Refer to [Privacy Code 2024](https://docs.nexthink.com/legal/global-privacy-hub/privacy-code-2024) in the [Global Privacy Hub](https://docs.nexthink.com/legal/global-privacy-hub) for more information on how Nexthink complies with applicable data protection standards across its cloud products.
{% endhint %}
Manage and oversee the lifecycle of your organization's employee data. Define the retention period of inventory and operational data, and comply with the data protection regulations for retrieval and deletion of data.
## Accessing the Data Management page
* Select **Administration** from the main menu.
* Click on **Data Management** in the System Configuration section of the navigation panel.
{% hint style="info" %}
Data Management is only visible with **Data management** administrative permission and requires a **none (full access)** data privacy setting. Refer to the [Roles](/user-guide/administration/account-management/roles.md) page for more information.
{% 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.nexthink.com/user-guide/administration/system-configuration/data-management.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.
