> 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/essentials/portfolio/pacts-via-portfolio.md). # Pacts (via Portfolio)
IN THIS ARTICLE\ View all Pacts that have been created to share activity records from within this workspace portfolio. Each Pact shares a collection of activity records and gives access to the programmatic metrics for that Pact Opportunity. *** ## Pacts **Pacts** are collaborative agreements available from a workspace portfolio that align an external aggregator, such as a funding partner, with an organization's work. Together, all users can track activity data, including shared modeled outcomes and metrics. Pacts allow users to define a common framework for implementation—such as restoration targets, climate resilience outcomes, or equity commitments—and track collective progress over time. Each pact can include: * A curated set of shared metrics * Target values or thresholds * Assigned contributors or member organizations * Timelines and status indicators Pacts provide a pathway for the workspace members to share activity records from within the portfolio, and bring programmatic metrics into the shared activity records. Remember, activity records can be shared across multiple Pacts. This makes it possible to roll up performance data from individual records to assess overall progress toward the pact’s commitments. Overview pages and dashboards provide visibility into how each organization or partner is contributing to the pact goals. --- # 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/essentials/portfolio/pacts-via-portfolio.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.