> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/welcome.md). # Welcome This is your central resource for configuring, analyzing, and governing your privacy operations directly from the Didomi console.


Organization and Account	Manage your organization's settings, users, roles, and access controls.
Consent Management Platform (CMP)	Configure and publish consent notices across your websites and apps to collect end-user consent in compliance with global privacy regulations.
Preference Management Platform (PMP)	Set up preferences widgets that empower your end-users to control their communication, marketing, and data sharing choices.
Compliance Report and Advanced Compliance Monitoring	Track and audit your compliance posture across domains, regulations, and vendors.
Privacy Requests	Manage end-user data subject access requests (DSARs) by configuring intake forms, routing requests to the right teams, and tracking their resolution
Analytics	Monitor consent rates, user preferences, and compliance performance through your Didomi Console dashboards.
Integrations	Connect the Didomi console with your existing tools and third-party services to synchronize consent and preferences across your stack.

### **New to Didomi** Start by setting up your organization's account, then follow the guides for the products included in your plan. Each section walks you through configuration steps directly in the Didomi Console. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.didomi.io/welcome.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 `build a script that syncs our docs to a CMS` 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.