> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/help-center/account-management/how-do-i-register-for-an-account.md). # How do I register for an account? To use FieldDoc, you must have an account registered to a verifiable work email address and assigned to a verifiable organization. Start by logging in to fielddoc.com/register. You must use your real name and a work email address to register. Once you register, check your inbox to verify your email. Based on your email domain, you will either be invited to join an existing organization or asked to create a new organization. If neither of these options is accurate, please reach out to our support desk at . All users are registered as basic users. If you would like to upgrade your organization and account to a standard or aggregator plan, please reach out to . --- # 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://help.fielddoc.org/help-center/account-management/how-do-i-register-for-an-account.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.