> 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/activities/general-settings/pacts-via-activity.md).

# Pacts (via Activity)

<figure><img src="https://2238918414-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FatQfu0bk7aRHUPp2fz19%2Fuploads%2F3BfkYtKx1QR1beMNH0Zj%2FScreenshot%202025-03-26%20at%201.12.01%E2%80%AFPM.png?alt=media&amp;token=c348de37-c7f6-4158-8e2e-25b4c5ec291b" alt="" width="563"><figcaption></figcaption></figure>

IN THIS ARTICLE

Pacts are the feature through which standard users can share their activity records to third-parties. These are typically funding opportunities. Activity records can be linked to multiple Pacts, which should help reduce the threat of duplication for this important work.

***

## Pacts via Edit Activity

**Pacts** are a key feature in FieldDoc that allow standard users to share their **activity records** with third parties—typically organizations managing **funding opportunities** or broader programmatic initiatives.

Think of a Pact as a bridge between your project work and the entities that review, support, and track it.

There are multiple connection points between Pacts and individual activity records. From within the Edit Activity, users can:

1. Check to confirm which Pacts are associated with the Pact.
2. Create a new Pact.
3. Link to an existing Pact.

## Dig In! Interactive Tutorial

{% @arcade/embed flowId="UDnjmKWEXQ8xieCfvvsO" url="<https://app.arcade.software/share/UDnjmKWEXQ8xieCfvvsO>" %}

## Learn more!&#x20;

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Pacts</td><td><a href="/essentials/pacts.md">Pacts</a></td></tr></tbody></table>


---

# 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/activities/general-settings/pacts-via-activity.md?ask=<question>&goal=<user_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.