> For the complete documentation index, see [llms.txt](https://developers.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.didomi.io/api-and-platform/consents/users.md). # Users Consent users represent end users of your applications or websites that Didomi is storing consent and preferences information for. The `User` entity represents the latest consent status, for a given regulation, of an end user as well as additional metadata. That's the entity that you should query when you want to check if you have consent for a specific data processing or purpose. The [`/consents/users`](https://didomi.stoplight.io/docs/didomi-api/ZG9jOjU2ODQ0NTc-introduction) endpoint of the API exposes the users managed by Didomi for your organizations. A full reference of the endpoint and the resources it returns is available [here](https://didomi.stoplight.io/docs/didomi-api/ZG9jOjU2ODQ0NTc-introduction). If you are importing users already present in your systems and there is no need for these users to be forwarded to your [integrations](https://gitlab.com/didomi/developers-documentation/-/blob/main/docs/api/consents/broken-reference/README.md), you can add the query parameter `$disable_integrations=true` to your request to disable such forwarding. --- # 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://developers.didomi.io/api-and-platform/consents/users.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.