> 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/pricing-plans-and-billing.md). # Pricing, Plans, and Billing A user must have an account to access FieldDoc. Plans are structured at the organization level. Upon registration, each user's organization is started as a **basic plan.** ## How do I upgrade to standard? Organizations that want to expand their use of FieldDoc beyond meeting grant reporting requirements need a **standard plan**. Entities that wish to host funding opportunities or collect record data from many organizations can be considered for our **Aggregator Plan**. Please reach out to to upgrade your organization or learn more. ## Do you offer a free or discounted plan for non-profits? Non-profits and their technical service providers make up the majority of FieldDoc users. The pricing plan is targeted at non-profits. [The Commons](https://www.ourcommoncode.org/), the developers of FieldDoc, is also a 501(c)3 non-profit. We actively fundraise to reduce costs to build and maintain the FieldDoc system. If you are interested in making a donation, please visit our [donation page](https://pages.donately.com/thecommons/form/frm_580d51e59a32). --- # 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/pricing-plans-and-billing.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.