> ## Documentation Index > Fetch the complete documentation index at: https://docs.payglue.io/llms.txt > Use this file to discover all available pages before exploring further. # Labels on a PayGlue member > The four labels and the note PayGlue writes on a Ghost member, what each one means, and how to use them for support and filtering. Open a member in Ghost Admin that came through PayGlue and you get four labels and a note. Between them they answer nearly every support question about a paying reader without opening a provider dashboard. A member in Ghost Admin created by PayGlue, showing four labels and the note underneath ## The four labels ``` source:payglue product:pricing-tier-2 payglue-active payglue-provider:polar ``` | Label | Means | Changes | | ------------------------- | --------------------------- | ------------------------ | | `source:payglue` | PayGlue created this member | never | | `product:` | what they bought | on a new purchase | | `payglue-active` | they have access right now | flips to `payglue-ended` | | `payglue-provider:` | who took the money | never removed | `payglue-active` is the one that matters most: it is what the paywall looks for, and it comes off the moment a subscription ends. Status and provider are two separate labels on purpose. Packing both into one string forces every reader of that data to do prefix matching, which is how an access check ends up comparing a provider name against a product id. ## When a membership ends `payglue-active` is replaced by `payglue-ended`. The provider label stays. ``` source:payglue product:pricing-tier-2 payglue-ended payglue-provider:polar ``` The status flips rather than disappearing, and that is the point. A member with **no status label at all** is ambiguous: it could be somebody who cancelled, somebody whose purchase never granted anything because no rule matched, or somebody who was never a customer. With `payglue-ended` present, the first case is a fact you can read. A member with `source:payglue` but no status label is worth a look. It usually means a purchase arrived and found no rule to apply, which is a failure that leaves no other trace. See [Member did not receive access](/troubleshooting/member-no-access). ## The note ``` Direct via PayGlue | Provider: polar Product: e910af3d-e1d7-450b-8596-2b17a309eab7 Order: 2026-08-14 | Event: 5e38bc88-0ff7-4b56-a379-78f058f853a6 Ended: 2026-08-14 | Event: c583ab77-e7d3-4b77-b33c-b63ba22c28b7 ``` Which provider, the provider's own product id, when they bought and which event said so, and when it ended and which event said that. The product line carries the **provider's** id rather than your access key, because that is the string you paste into the provider's search box. The note is a summary of the current state, not a history. Each purchase rewrites it, and the ending line goes with it, so a member who bought, left and bought again shows the second purchase only. For the full sequence, use **Analytics > Webhook Events**. ## The comped flag is not a label On sites with Stripe connected, PayGlue also sets Ghost's **comped** flag. It does not appear in the labels or the note. That flag is what makes Ghost treat the member as paid, so native gating, tiers and the portal behave normally. Without a Stripe connection there is nothing for Ghost to hang it on, so the flag stays off and the paywall script does the gating instead. See [Zero-amount Stripe subscriptions](/troubleshooting/ghost-stripe-notice) for what that flag creates on the Stripe side. ## Removing access by hand Open the member in Ghost Admin and delete the label. Only if the member shows as comped. Doing both is safe on either kind of site. Leave `source:payglue` and the provider label alone. They record where the person came from, and removing them makes a later question unanswerable for no benefit. A manual change is not permanent. The next purchase or cancellation for that person writes the full label set again, so treat hand edits as a correction for one case rather than a configuration. ## Using labels for real work **Filtering.** Ghost lets you filter members by label. `payglue-provider:kofi` gives you everybody who came through Ko-fi, which is how you find the affected group when one provider has a problem. **Support.** Somebody asks why they cannot read a post: the status label says whether they should have access, the provider label says where to look next. **Reconciling.** Comparing active subscribers at the provider against members carrying `payglue-active` is a rough but fast check that the two are still in step. See also: [When a membership ends](/ghost/member-lifecycle).