> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/settings/advanced/agreements.md).

# Agreements

Agreements are used for two purposes: 

1. **Loyalty program terms:** Display terms and conditions that customers must agree to in order to participate in your loyalty program.
2. **Referral offer terms:** Present terms that referred prospects must agree to before claiming a [referral offer](broken://pages/GikZbnkjejaMJ5aAROYn). This includes requirements such as opting into text message marketing.

## **Accessing agreements**

Business administrators can access the Agreements feature from the Dashboard by navigating to "Settings" in the left navigation, then selecting "Agreements" on the subsequent page.

**Key features and functionality**

* **Tracking Versions:** Agreements track all agreement versions, ensuring compliance history is maintained. When a customer agrees to an agreement, we capture:
  * Version agreed to
  * Customer's name at the time of agreement
  * Customer's email address at the time of agreement
  * Customer's IP address

## **Creating agreements**

1. Click on the "Create an agreement" button.
2. Fill in the following fields:
   * **Internal name:** Used for internal identification purposes.
   * **Agreement text:** This is the text that customers or prospects will agree to. You can include hyperlinks using the provided format.
   * **Version:** Assign a human-readable version to the agreement (e.g. v1.0).
   * **Applicable referral offers:** Associate the agreement with specific referral offers.
   * **Display to users when they join?:** Toggle to display the agreement when users join the loyalty program.
   * **Active:** Toggle to activate or deactivate the agreement.
   * **Required:** Toggle to make the agreement mandatory or optional.

The customer profile will display the agreements a customer has agreed to.


---

# 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://docs.perkville.com/features/settings/advanced/agreements.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.