Tags & Memberships

Two things decide what a member can see: memberships and tags. They work together, but they answer different questions, and mixing them up is the most common way a membership site gets hard to manage.

Memberships are the ID card

A membership is broad access. It decides which building you can walk into: the members' area, the courses you've bought, the dashboard you see when you log in. Checking "Gold" on a page's protection box means every Gold member gets in, and it keeps working as you add Gold members, without you touching the page again.

Memberships are also the efficient way to control access day to day. A member belongs to a handful of memberships at most, so your protection checkboxes stay short and readable, and your login experience can follow them: each membership can have its own login homepage, so a Gold member lands somewhere different than a Silver member.

Creating a membership is a guided step in the dashboard: give it a name, pick (or let the system create) its access tag, and optionally set up billing-related tags if it's a subscription. The name matters more than you'd think; short, distinct names keep the protection box readable for years.

Tags are the keys

A tag is fine-grained control. It's a label that unlocks one room: a single lesson, a module, a download, a forum topic. Tags are applied and removed one at a time by your automations, which makes them perfect for anything that happens at the individual member's pace. Where tags live and how they sync with your CRM is covered in User Tags.

The classic example is course drip. When a member finishes lesson one, an automation applies the "lesson-2-unlocked" tag, and lesson two opens for that member alone. Other students, on their own schedules, see their own set of open doors. That per-person, per-piece control is what tags are for, and it's exactly what a membership is the wrong tool for: nobody wants a "Lesson 2" checkbox on every page.

Tags also do work that has nothing to do with content access: marking that a member opened your onboarding email, attended a webinar, or asked for support. A tag is just a label; access control is only one of its jobs.

How they work together

Under the hood, a membership is held by a tag too. When you create a Gold membership, it gets a Gold access tag, and holding that tag is what makes you a Gold member. So your CRM keeps one list of labels, and the site's protection box gives you both views: check the membership for broad access, or name specific tags for fine control.

On any page you can combine them. Require the Gold membership and also the "workshop-2026" tag, and you've built "Gold members who registered for the workshop" without creating a third thing to maintain. Multiple memberships on one page are an OR: any one of them gets the member in.

The billing tags: PAYF, SUSP, CANC

Subscriptions introduce a problem a plain access tag can't express: a member whose access should pause, not end. That's what the three billing tags are for. If a member holds the PAYF tag (payment failed), SUSP (suspended), or CANC (cancelled), the site treats them as NOT having the membership, even if the access tag is still on.

Why not just remove the access tag? Two reasons. First, the tag tells you why: a member with CANC cancelled, a member with PAYF needs a card update. Second, each state can have its own login homepage, so a member with PAYF logs in straight to an "update your payment method" page and fixes it themselves. That one page pays for the whole system in reduced support email.

There's a third reason that matters more than it looks. A member by now may hold dozens of tags: lessons unlocked, modules completed, perks claimed. Billing tags interrupt access temporarily without touching any of that. The payment resumes, PAYF comes off, and the member is exactly who they were, in exactly the place they stopped. Rebuilding that tag state by hand after a plain removal is somewhere between tedious and impossible. This is a large part of why the advice is to build access on memberships rather than on tags alone: the membership layer gives you a switch that pauses everything at once, while the tags underneath stay safe.

Your billing system applies these automatically: the payment fails, the PAYF tag lands, access pauses. The card gets updated, PAYF comes off, access resumes. Nobody touches anything.

Memberships, subscriptions, and orders are three different things

People use these words interchangeably, and the confusion costs real money and creates extra complexity when it reaches a billing setup. They answer three different questions.

A subscription is a payment arrangement. It goes on for some amount of time and renews until it doesn't. When the payments stop, access ends with them, arbitrarily, at whatever date the card finally declined. This is the arrangement PAYF exists for: a subscription in trouble is usually fixable, so access pauses instead of vanishing.

An order is a one-time payment (or a short payment plan). The member pays once and either keeps access forever or for a predefined timeframe, like a six-month program. An order can fail too, but there's nothing recurring to rescue, so there's less need for pause states.

A membership level is about access, not money at all. It says what kind of member this person is and what they can reach. The same membership level can be reached by entirely different payment paths.

Once the three are separate in your head, the standard situations make sense:

• Two subscriptions, one membership. You sell a monthly plan at $29 and an annual plan at $290. Same access either way, only the payment differs. You create one membership level and let both plans grant it. Members who upgrade from monthly to annual change nothing about their access; the tag state they've built up comes along untouched.
• A membership with no payment at all. Free tiers, beta groups, inner circles: the member holds the membership, no subscription or order exists, and access control works exactly the same. Nothing about a membership requires money to change hands.
• A subscriber who isn't a member. Amazon Prime isn't a membership; it's a subscription to a service. If someone pays you monthly for coaching calls but never gets site access, they're a subscriber with no membership. The payment and the access are genuinely unrelated.
• A member who isn't a subscriber. Every free member, forever. No card on file, full access to whatever the free membership includes.

The practical rule when you set things up: decide the membership first, because it's what the site actually controls. Then decide how people buy their way into it, and let the billing system do that part. When a product and a membership get welded together (the $29 Gold Plan IS the Gold membership), every future price change, trial, or bundle becomes a small migration. When the payment path and the membership stay separate, those are all just new ways to hand someone the same ID card.

Choosing which to use

Ask one question: does this control describe a group of people who share the same access, or a change happening to one person's access over time?

• A shared group (tiers, products bought, site-wide areas) belongs to a membership. Everyone in the group gets in the same way, today and next year.
• An adjustment over time (lesson unlocked, offer claimed, webinar attended) belongs to a tag. It's one member's access moving forward, on their own schedule.