> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/privilege-and-activation.md). # Privilege & Activation
Cover image

:gift:

Privilege

Define customer benefits on each pass, from discounts to tiers, balances, perks, and redeemable rewards./files/adkPI3KmRcKlseRL5ydj/pages/4bApkQ3gFAcacvtGxT7K

:bolt:

Activation

Trigger privileges at scale using segments, schedules, or events, then update eligible passes automatically instantly./files/QuvTlY5wmI6zXKqPLU2E/pages/LXqziHfHXP4KuSPnEDN0
**Privilege** focuses on what a pass *displays*: tiers, statuses, discounts, points balances, or special perks tied to a customer's profile. This is the data layer — how privilege information is computed, stored, and surfaced as visible fields on the pass, and how it updates over time as a customer's status changes (e.g. moving from Silver to Gold). **Activation** focuses on *triggering* those privileges: the mechanism that turns a stored benefit into something the customer can actually use, whether through a manual action, a pass update via the API, or a rule-based condition (purchase threshold, date, event). It likely also covers how activation state is reflected back on the pass (badges, fields, or visual indicators). Together, these two pages explain the loop: a privilege is defined and stored, then activated and reflected on the pass — closing the gap between backend customer data and what shows up in Apple Wallet or Google Wallet. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.thewalletcrew.io/guides-animation/engage-and-animate/privilege-and-activation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.