> 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/getting-started/quickstart/create-an-organization-and-account.md). # Create an organization and account ### Create Your User Account To use FieldDoc or any FieldDoc-powered application, you need to create an individual user account. Each person must have their own login. Do not share your username, password, or account access with anyone else. When creating your account, please use accurate information, including your real name and a valid work email address. You are responsible for keeping your account details, including your email address, up to date. ### Join the Correct Organization All FieldDoc users must be connected to a verified Organization. You should only join an Organization if you are authorized to act on its behalf. This usually means you are an employee, officer, member, or direct representative of that Organization. External partners, such as contractors, consultants, collaborators, technical assistance providers, funders, agency partners, or volunteers, should not join another Organization’s account as a member. Rather, external partners may have their own Organization account and collaborate can through FieldDoc features such as workspaces, Pacts, shared records, application-specific permissions, or other available tools. ### Collaborate Across Organizations FieldDoc welcomes collaboration! If you work with more than one Organization, use FieldDoc’s collaboration features instead of joining multiple Organization accounts. As explained above, each user account can only be a member of to one Organization at a time. However, users can access records, workspaces, or other shared areas across Organizations when they are invited through the appropriate FieldDoc permissions. Organization Owners and authorized administrators may invite external users to collaborate within an Organization workspace only through the permissions available in FieldDoc and only when they are authorized to provide that access. --- # 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/getting-started/quickstart/create-an-organization-and-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.