> 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/referrals/managing-active-and-inactive-referral-rules-and-offers.md).

# Managing active and inactive referral rules and offers

A broader instruction on activating and deactivating rules and offers can be found in the [Loyalty Program](https://docs.perkville.com/features/settings/loyalty-program.md) settings docs.

Referrals have a few unique restrictions.

1. If you deactivate a referral rule, the rule and all of its offers will deactivate and end up in the Recently Deactivated Perks section.
2. If you only deactivate an offer, only the offer will move to the Recently Deactivated Perks section.
3. When reactivating a rule, determine whether you already have an active referral rule. If so, you may be prompted to override that rule if you wish to use the deactivated one instead. Reactivating a rule *will not* reactivate its previous offers.
4. When reactivating an offer, an active referral rule must exist. If one does not exist, you will receive a warning. Any reactivated offers will attach to the existing active referral rule.


---

# 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/referrals/managing-active-and-inactive-referral-rules-and-offers.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.
