> 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/program-management/program-management-overview.md).
# Program Management Overview
## Program Manager Documentation
Page actionsCommentShare feedback on the editor**FieldDoc takes the complexity out of managing your funding program, so you can spend less time wrangling grantee data and more time measuring real impact.**CommentShare feedback on the editorProgram Managers unlock a different set of tools in FieldDoc—not just because they oversee the big picture, but because they help shape it. While grantees and standard users enter data from the field, Program Managers define the structure of that data—setting the metrics, activity types, and standards that make it all measurable. By standardizing inputs across many users, they turn scattered details into actionable insights and track progress toward shared goals.CommentShare feedback on the editor
### Aggregator Subscription
Program Managers gain access to FieldDoc through an Aggregator subscription. All of the Documentation in the help center for free and standard users applies to Program Managers when you are buiding out your own porfolio of nature-based records. The pages in this section are geared toward setting up and managing Programs to collect data from other FieldDoc users.CommentShare feedback on the editor**Ready to streamline reporting and maximize your program’s potential?**CommentShare feedback on the editorLet's dive into building and managing your program!
---
# 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/program-management/program-management-overview.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.