> 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/configuration/how-to-configure.md).

# HOW TO CONFIGURE

Before creating passes or connecting external systems, a number of parameters must be set at the platform level. The Configuration section covers everything needed to make The Wallet Crew operational for a brand: from the initial account setup to the visual design of Wallet templates, including the technical credentials required to issue passes through Apple Wallet and Google Wallet under the brand's own identity.

<table data-view="cards"><thead><tr><th>Title</th><th>Summary</th><th data-card-target data-type="content-ref">Target</th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>Platform</td><td>Access tenant settings, user permissions, API keys, domains, and core configuration required to operate The Wallet Crew securely every day.</td><td><a href="/spaces/DJrf9G0l7ArnvuwEH0a8/pages/ZlJuyLbDiH4h9cxJYtI3">/spaces/DJrf9G0l7ArnvuwEH0a8/pages/ZlJuyLbDiH4h9cxJYtI3</a></td><td><a href="/files/ehV2YmdYDdxaCYAEV9JS">/files/ehV2YmdYDdxaCYAEV9JS</a></td></tr><tr><td>Wallet</td><td>Configure Apple Wallet and Google Wallet, design pass templates, secure distribution, and manage imports, exports, and migration workflows at scale.</td><td><a href="/spaces/DJrf9G0l7ArnvuwEH0a8/pages/3hygUQfY4HjbR0PoBiO6">/spaces/DJrf9G0l7ArnvuwEH0a8/pages/3hygUQfY4HjbR0PoBiO6</a></td><td><a href="/files/eo7TEtVZqQTRn7zwmtMb">/files/eo7TEtVZqQTRn7zwmtMb</a></td></tr><tr><td>Enrolment Form</td><td>Build hosted enrolment journeys, collect customer data, control access, and support secure pass creation and retrieval flows for different campaigns.</td><td><a href="/spaces/DJrf9G0l7ArnvuwEH0a8/pages/iPkpzqpCf0liHTb6cyU7">/spaces/DJrf9G0l7ArnvuwEH0a8/pages/iPkpzqpCf0liHTb6cyU7</a></td><td><a href="/files/EuXA3EcgM6gLsYPShlvx">/files/EuXA3EcgM6gLsYPShlvx</a></td></tr></tbody></table>

**Platform settings** are the starting point. This is where the tenant is initialized — general parameters such as the application title, supported languages, and the favicon displayed on hosted pages. User access and multi-factor authentication are configured here, as well as the API keys used to authenticate backend requests to The Wallet Crew APIs. Brands that want to host enrolment and download pages under their own domain will also find the custom domain configuration in this section.

**Wallet settings** cover the credentials that Apple and Google require to issue passes. Each platform has its own authentication mechanism: Apple Wallet relies on certificates and push notification identifiers managed through the Apple Developer account, while Google Wallet requires access to the Google Pay & Wallet Console and dedicated API credentials. Both must be configured before any pass can be created or distributed.

**Template configuration** defines the structure and appearance of the passes themselves — field layout, colors, images, and dynamic content via the DotLiquid templating engine. Templates can be translated into multiple languages and duplicated or imported across tenants.


---

# 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:

```
GET https://docs.thewalletcrew.io/configuration/how-to-configure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.