> 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/loyalty-activity-controls/allowed-activities-while-inactive.md).

# Allowed activities while inactive

Control limited loyalty activity while a business or location is inactive.

Allowed activities are exceptions that can continue while loyalty is inactive. They do not make the business or location active.

An activity must be allowed at every applicable level. Location settings can be more restrictive than business settings. They cannot be more permissive.

### Available activities

You can allow these activities:

* **Referrals**
* **New sign-ups and registration bonuses**
* **Staff adjustments to customer balances**
* **Staff earning or redeeming on their own accounts**

Allowed activities still require valid transaction dates, agreements, permissions, and eligibility rules.

### Business and location choices

Business settings set the maximum activities available while the business is inactive.

For each location, choose one option:

* **Use business settings** applies the business choices.
* **Choose activities for this location** lets you select a stricter subset, including none.

**No activities allowed** is a valid custom location selection. It does not need a separate mode.

Null or legacy location settings use the business settings. New locations created through the staff setup flow begin inactive with no allowed activities until setup is reviewed.

### Related controls

Use [Business program status](https://docs.perkville.com/features/settings/business/business-program-status.md) for business-wide controls. Use [Location program status](https://docs.perkville.com/features/settings/location-setup/locations/location-program-status.md) for an individual location.


---

# 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/loyalty-activity-controls/allowed-activities-while-inactive.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.
