> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/user-guide/digital-experience.md). # Digital Experience The Digital Experience module positions IT leaders at the forefront of strategic decision-making by offering comprehensive insights into the Digital Employee Experience (DEX). This empowers IT executives to shape the future of the digital workplace, aligning DEX enhancements with overarching business goals to drive productivity and effectively manage costs. Rather than focusing on day-to-day operations, this module serves as a pivotal tool for long-term, proactive strategy development in optimizing the digital landscape. * [Getting started with Digital Experience](/platform/user-guide/digital-experience/getting-started-with-digital-experience.md) * [Using Digital Experience](/platform/user-guide/digital-experience/using-the-overview-dashboard.md) * [DEX score](/platform/user-guide/dex-score.md) {% hint style="info" %} Depending on your current licensing model, this capability may require an additional license. Contact your Nexthink representative 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/platform/user-guide/digital-experience.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.