> 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/configure/advanced-configuration/wallet/template-configuration/general-tab.md).

# General tab

Settings of a pass template shared by Apple Wallet and Google Wallet: download page, stamps, metadata, preview data, console title and advanced options.

The General tab holds the settings that do not depend on the wallet: how the pass is distributed, the data computed for it, how it is named in the admin console and a few technical options. They are kept apart from the Apple and Google tabs so that they are defined once for both wallets.

The tab is the same for every type of template, except the **Stamps** section, which only exists for stamp cards. The preview next to the form can switch between Apple and Google when both are configured (see [Preview and preview data](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/preview-and-preview-data.md)).

<figure><img src="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2Fgit-blob-00527ab16549030812106a456d30afa5aced5a74%2Ftemplate-editor-general-tab-retake.png?alt=media" alt="General tab of a stamp card template with the Basic configuration, Stamps and Metadata sections next to the Apple Wallet preview"><figcaption><p>The General tab, with its sections on the left and the live preview on the right.</p></figcaption></figure>

## Basic configuration

This section sets what defines the template and how its passes are distributed.

* **Type** shows the type of the template, read-only (see [Settings by type](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration.md#settings-by-type)).
* **Download page** (required) is the default download page used to display this pass. **Edit** and **New** next to the field open the selected download page or create a new one.

## Stamps

This section exists only for stamp card templates. It sets the goal, what the card does when it is full, and an optional reward benefit template. The [Stamp card](https://docs.thewalletcrew.io/guides-design/design/stamp-card.md) page describes each setting and the stamp images.

## Metadata

Metadata are values the template computes for each pass at each update and stores on the pass. They exist so that passes can be searched and filtered in the pass list, and so that automations can react to them, without reading the source systems again.

Each entry has:

* a **Key**, the name used in the pass list and automations;
* a **Value**, written as text or as a Liquid expression that reads the pass data (the `</>` button, "Edit as expression");
* a **type**: String, Number, Boolean or Date & time, chosen with the button at the end of the value, which decides how the value is compared and filtered.

New entries are added with **Add metadata**. Metadata are computed again at each update of the pass, so a change of the template applies to existing passes at their next update. Push an update (**Save & push update**, or from the pass list) to compute it for every existing pass right away. The [Liquid templating](https://docs.thewalletcrew.io/developers-guides/integration-guides/wallet/templating-engine.md) page describes the expression language.

<figure><img src="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2Fgit-blob-8fcadf3dd1d502cfebfb251c48d050cda5b2d549%2Ftemplate-editor-expression-editor-retake.png?alt=media" alt="Expression editor with a Liquid value on the left and the Available variables panel grouped by provider on the right"><figcaption><p>The expression editor: the expression on the left with its rendered preview below, the available variables on the right.</p></figcaption></figure>

## Preview data

Preview data are example data used to preview the template with realistic values; see [Preview data](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/preview-and-preview-data.md#preview-data).

## Preview

Despite its name, this section does not change the phone preview. It sets how each pass of the template is named inside the admin console, for example in the pass list and on the pass page.

* **Title** (required) and **Subtitle**: both are localizable and accept Liquid. By default they show the serial number of the pass (`{{ serialNumber }}`).
* A **Language** selector switches between the tenant's languages to enter a translation.

## Advanced configuration

These options change technical behavior. Most templates keep their default values, except **Scannable data**, which depends on how passes are scanned.

### Scannable data

**Persist scannable data (qrcode, barcode values)** stores the barcode and QR code values of each pass in The Wallet Crew, so that compatible systems can find the pass from the value they scan. It is required for Pass Scanner to find a pass: without it, scanning a pass of this template finds nothing. The stored values are then also shown on the pass page. The option is off by default.

{% hint style="warning" %}
A stored barcode value works as an access key: whoever holds it can be identified as the holder of the pass, for example to enter an event. Turn the option on only for templates whose passes are scanned with Pass Scanner or a compatible system.
{% endhint %}

### Other options

| Option                                               | Purpose                                                                                                                              | Default |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------- |
| **Notification settings** — Duration and Unit        | How long the update notification stays visible in wallet apps after it is sent, between 30 minutes and 21 days.                      | 7 days  |
| **Link tracking** — "Enable link tracking"           | Wraps the links of the pass with an analytics redirect, to count when they are opened.                                               | On      |
| **Image optimization** — "Enable image optimization" | Resizes and compresses the images of the pass for wallet display.                                                                    | On      |
| **Data providers**                                   | The providers the passes of this template read their data from: data providers and tenant scripts, added with "Add a data provider". | None    |

With data providers, the section also lists the **identifiers a pass needs**, for each provider: required, optional, or one of several. A pass created without them gets nothing from the providers that read them. Identifiers are described on the [pass page](https://docs.thewalletcrew.io/guides-monitoring/monitor/pass-details.md#overview).

<figure><img src="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2Fgit-blob-61b4f30be65454e255cd73e711aca1058b571857%2Ftemplate-editor-advanced-configuration-retake.png?alt=media" alt="Advanced configuration section with Scannable data off, a notification duration of 1 week, link tracking and image optimization on, and the data providers list"><figcaption><p>The advanced configuration section with its default values.</p></figcaption></figure>

## Expressions and translations

Many fields of the editor, on every tab, accept either fixed text or an expression.

The `</>` button ("Edit as expression") opens the **expression editor**. It lists the **Available variables**, grouped by data provider, searchable and with their type (Text, Number, Yes/no, Date and time, Object or List), and inserts them with **Insert variable**. "Show values of the previewed pass" displays the value of each variable for the selected preview data, and the result of the expression is rendered live. A variable that no data provider of the template declares, and that the preview data does not hold, is flagged; an obsolete variable is flagged with the name to use instead.

Localizable fields carry a translate button, **Edit translations**. With "Use a different text for each language", a value is entered per language, and the field shows how many languages are translated (for example "Translated in 2 of 3 languages") and which are missing. The **Default** value is the unlocalized fallback, used for any language without a translation. "Same text in every language" goes back to one text for all languages. Translating a whole template at once is described in [How to translate a template](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/how-to-translate-a-template.md).


---

# 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.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/general-tab.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.
