Skip to main content

Membership types

Creating and managing the membership types that drive benefits, guest passes, campaign targeting, and card appearance.

A membership type is one tier of membership your organization sells: Individual, Family, Premium, Passport for 2, and so on. Every membership in PassPlay carries a membership type name, and the list of membership types you create in PassPlay is what gives that name meaning: how many people it admits, how it’s displayed in the app, where it links for renewal, and what color card its members see.

Why types matter

Membership types are referenced throughout the rest of PassPlay:

Area

How the type is used

A standard or redeemable benefit can be scoped to one or more types. Matching memberships inherit it automatically.

Pass grants and one-off distributions can target a single type.

Campaigns can be sent to everyone with a given membership type.

Membership type is one of the filters available in the audience builder.

Key aspects of your rewards program can be limited to specific types.

Membership card

The type supplies the display label, and (where enabled) the card and text colors on the Apple Wallet / Google Wallet pass.

Renewal

The type’s renewal URL overrides the org-wide Renew URL for members of that type.

App access

The type can override the default device or app connection limits. See Per-type limits.

The list

Sidebar → Organization → Membership types shows every type for your organization: name, admits, display label, and description.

Order matters beyond this page: it’s the order types appear in the membership type dropdowns elsewhere in the admin, and the order they’re returned to the member app.

Creating or editing a type

Field

Notes

Name

Required. Must match the membership type name exactly as it arrives from your membership system - see below.

Display label

Optional alternative name shown in the app and on the wallet card, when you want members to see something friendlier than the internal name. Click Use custom display label to reveal the field, or Remove label to clear it.

Membership name aliases

Optional. Other names, as they arrive from your membership system, that should be treated as this type. Click Map other membership names to this type to reveal the field. See Mapping other names to a type.

Admits

How many people this type admits. Only shown if your org tracks admit counts.

Description

Optional. Shown in the admin list and available to the app.

URL

Optional. Where to send a member who wants more information about this membership type.

Renewal URL

Optional. Where the expiration banner sends members of this type. Falls back to the org-wide Renew URL when blank.

Disable expiration notice

Suppresses all expiration messaging for this type including the expiration banner in the app and portal, and the renewal reminder on the wallet pass. Useful for lifetime, complimentary, or staff memberships that never really expire.

Card color / Text color

Optional per-type colors for the membership card, overriding your org’s primary colors. Pick a text color with enough contrast against the card color.

Custom limits

Optional per-type device or app connection limit, overriding the default values. See Per-type limits.

Display labels, membership name aliases, per-type card colors, per-type limits, and the admits column each depend on a feature being enabled for your org. If a feature described here isn’t visible, contact us.

Per-type limits

PassPlay allows you to limit how often a membership can be connected in the member app. The limit is set org-wide on the organization details page, and a membership type can override it for just those specific memberships. Use it when one tier should get more (or less) than the rest: a Premium or Household type that covers more people than an Individual, or a Corporate type that must not be limited at all.

The Custom Limits options:

Field

Availability

What it limits

Max App Connections

All orgs

Times a membership may connect from the app before an admin reset is necessary.

Max Devices

Orgs with the device sessions feature

Total devices that may be signed in to a membership at the same time.

Each field has three settings:

Setting

Effect

Organization default

Use the org-wide value. This is the default for every type, and the form shows the current org value below the field.

Limit to

Use the number you enter for this type. The number must be 1 or more - to remove the limit, use No limit instead.

No limit

Memberships of this type are not limited.

The membership types list shows a badge on each type that overrides a limit, so types left on the org default stay unmarked. On a membership’s details page, the device count is shown against the limit that is in force for that membership.

Names have to match your source system

PassPlay links a membership to its type by name, not by an ID. If your membership system sends Family Plus and your type here is called Family+, nothing connects: those memberships get no type-specific benefits, colors, label, or renewal link.

Before creating types, check the membership list or an existing membership record to see the exact names already coming through, and copy them. Capitalization and spacing should match.

If your membership system has several names for what you consider to be the same membership type (e.g. Family, Family - Renew, Family Legacy) you don’t have to create a separate type for each. See Mapping multiple membership types.

If your organization also uses the secondary Membership level on a membership (e.g. type Family, level Gold), only the type name is configured here. Levels are selected alongside the type where they’re relevant, such as on guest pass grants and campaigns.

Restricting imports to known types

Some integrations can be configured to import only memberships whose type has been set up in PassPlay, so unrelated records in your source system are skipped. This is set on the integration rather than here - contact us if you want it turned on. When it’s active, a name that doesn’t match exactly means those memberships stop importing, so add the new type before your source system starts sending it. A name listed as an alias on a configured membership type will also be treated as a match.

Mapping multiple membership types

Membership systems often carry several names for what you think of as one membership type: a term variant (Family - 1 yr), a legacy name kept for renewals (Family Legacy), a free tier (Family - Free), etc. Creating a membership type for each one means configuring the same benefits, colors, and campaigns three times over.

Membership name aliases solve that problem by allowing you to map multiple membership type names to a single membership type in PassPlay.

For example, if Family - 1 yr is set up as an alias for the Family membership type, all Family - 1 yr memberships will include everything configured for the Family type (benefits, colors, etc.), and show as Family in the app.

Adding aliases

On the create or edit form, click Map other membership names to this type and enter one name per line:

Family - 1 yr
Family Legacy
Family (comp)

Important considerations:

  • The names should match exactly as your membership system sends them.

  • Each alias must be unique and can’t be used on multiple membership types.

Existing memberships

Aliases are applied as memberships sync from your system. Memberships already in PassPlay under an aliased name keep that name until their next sync touches them.

Once a type has saved aliases, an Aliased Membership Names panel will be available beside the form with two actions:

Action

What it does

Apply aliases

Updates memberships already associated with one of this type’s aliases immediately instead of waiting for the next sync.

Remove aliases

Removes all aliases from the membership type and resets any affected memberships back to their original membership type name.

Both actions ask for confirmation before making any changes.

You can also remove a single alias by deleting its line and saving. Just that alias stops applying, and the memberships it mapped revert to their original names; the rest stay mapped.

Renaming a membership type that has aliases will also update any associated memberships.

Did this answer your question?