> 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/organization-and-account-settings/account-settings-and-support/access-customer-portal.md).
# Access customer portal
{% hint style="success" %}
**Access Type**: Available to all users
{% endhint %}
The customer portal enables your organization to view and manage your Didomi support tickets (that have been submitted by you or other members of your organization). In this article, we will cover how to create an account with the Didomi customer portal so that you can access support tickets.
Navigate to the upper right-hand corner of the Didomi product documentation site and click **Customer Portal**.
You will be redirected to the login page for the Didomi customer portal. Click **Register here**.
Use the subsequent modal to input the required information in the appropriate fields and click **Save password** when finished.
A verification email will be delivered to your email address to confirm the account creation.
---
# 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.didomi.io/organization-and-account-settings/account-settings-and-support/access-customer-portal.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.
