> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/control-panel-overview/membership-setup-overview/configure-card-design.md).

# How to Configure Membership Card Design

### Before you begin (Prerequisites)

* **Permissions**: You must be an **Administrator**, **Supervisor**, **Manager**, **Support**, or **Account Rep**. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md).
* **Membership Program**: The program must already exist. See: [How to Create a Membership Program](/products/control-panel-overview/membership-setup-overview/create-membership-program.md).
* **Branding Assets**: Have your club logo ready for upload.

### Instructions

1. Navigate to [**MEMBERS > Manage Membership Programs**](https://control.peoplevine.com/admin_membership_list.aspx).

> **Note (Pro Dash):** Navigate to **REWARD > Manage Membership Programs**.

2. Click **EDIT** next to the target program.
3. Expand the **Membership Card Design** section.
4. Configure the graphic and color scheme:

| Field            | Options                                                        |
| ---------------- | -------------------------------------------------------------- |
| **Graphic Type** | No Graphic / Upload New Graphic / Display Member Photo         |
| **Color Scheme** | Use Default or Create New (set text and background hex colors) |

5. (Optional) Check **Require members to upload a photo to activate their card** if using Display Member Photo.
6. Configure up to **6 card fields** — set each field's label and value source:

| Value Source                 | What It Displays                          |
| ---------------------------- | ----------------------------------------- |
| **(Auto) Member's Name**     | Full name                                 |
| **(Auto) Membership Number** | Assigned membership number                |
| **(Auto) Start Date**        | Membership start date                     |
| **(Auto) Expiration Date**   | Membership expiration date                |
| **Same for All Cards**       | Static text you enter                     |
| **Entered by Member**        | Value entered by the member during signup |
| **No Value**                 | Field hidden                              |

7. Expand the **Options** section. Under **Scan Type**, select **QR Code** or **Barcode** (requires Peoplevine Check-In App).
8. Click **UPDATE MEMBERSHIP**.

### What Happens Next

* **On the system side**: All future card issuances use the new design.
* **Next step**: Verify the card works with check-in by scanning a test code. See: [Scan a Member (Check-In App)](/products/check-in-app-overview/scan-member.md).

*Last updated: 2026-05-24*


---

# 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://help.peoplevine.com/products/control-panel-overview/membership-setup-overview/configure-card-design.md?ask=<question>&goal=<endgoal>
```

`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.