> For the complete documentation index, see [llms.txt](https://docs.identomat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.identomat.com/get-started/account-setup.md). # Account setup Create a personal account to get started with Identomat. ### About your personal account Personal accounts for Identomat are set up on [manage.identomat.com.](https://manage.identomat.com/) Through the management platform, you can access the dashboard, view detailed information on KYC (Know Your Customer) and KYB (Know Your Business) sessions, review applicants, create custom workflows, and retrieve your access key. To gain full access to all features on the Manage platform, your account must be verified by our team. ### Requesting an account If you don’t yet have an Identomat account, please [contact our team](https://www.identomat.com/contact-us) to request access. Our team will guide you through the onboarding process and provide credentials for the Manage platform. ### Sign in 1. Go to [manage.identomat.com](https://manage.identomat.com/) 2. Enter your email address and password, and click **Sign In**. > 💡 If your account needs activation and you've been waiting more than one day, please [contact us](https://www.identomat.com/contact-us). --- # 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.identomat.com/get-started/account-setup.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.