Revoking Access

Revoking access removes a subscriber’s Benecaster feed token immediately. Gated episodes stop reaching them the next time their podcast app polls. By default the feed URL itself keeps working and falls back to your public feed, so nothing visibly breaks on their end — see What Happens When a Token Is Revoked.

Revocation does not cancel their subscription in your membership plugin — that remains active unless you cancel it there separately.

When to Revoke

The subscriber cancelled but keeps accessing the feed. If a subscriber cancels their membership but their bridge event hasn’t fired yet (or if your bridge has a grace period that’s still running), revocation is the immediate fix.

Abuse or content sharing. If you have reason to believe a subscriber is distributing their feed URL, revoke first and investigate after. A revoked token can’t be used — revoking is clean and reversible.

Duplicate accounts. If a subscriber has two active tokens (see Subscriber Dashboard — Duplicate Subscriber Detector), revoke the token they’re not using to clean up the duplicate.

Manual housekeeping. On plans with subscriber limits, revoking dormant access frees up a slot.

Revoking a Single Subscriber

From the subscriber detail panel, click Revoke access. A confirmation dialog appears:

Optionally tick Send notification email to send the subscriber an email informing them their access has been removed
Confirm

Access is removed immediately. What the subscriber’s podcast app sees on its next poll depends on that show’s revoked-token setting.

By default their feed URL keeps working and serves your public feed — their app carries on, and gated episodes simply stop appearing. If you have turned that setting off for the show, the URL returns a 403 instead and their app shows an error. See What Happens When a Token Is Revoked.

If the Listener Bought Episodes

Remove and the bulk revoke action end all feed access, including episodes the listener bought. That is intended: you use that button to cut one person off. Every automatic ending, by contrast, leaves a buyer’s feed intact. Nothing on the Subscribers screen warns you that a listener bought episodes, and the confirmation does not mention it, so this page is the only warning you get. Removing a listener who paid for episodes is usually a refund conversation.

Bulk Revoke

From the subscriber list, check the rows and select Revoke access from the bulk action bar.

A confirmation dialog lets you:

Review how many subscribers will be affected
Choose whether to send notification emails

Maximum per operation: 200 subscribers.

After Revocation

The subscriber’s record remains in the subscriber list marked as revoked (no longer in active counts)
Their subscription in your membership plugin is unaffected
If their membership plugin subscription is still active and fires a subscription event (renewal, plan update), Benecaster will regenerate a token automatically

If you want access to stay revoked regardless of bridge events, you’ll need to cancel their subscription in the membership plugin as well.

Notification Email

The notification email tells the subscriber their access has been removed. It does not include their feed URL or any way to recover access — that’s intentional. If you revoke and later want to restore access, generate a new token manually or let the bridge re-issue one on the next subscription event.