1. Home
  2. AccessAlly
  3. Tagging: Allow Access to an Offering After Cancellation in AccessAlly
  1. Home
  2. Tags & Permissions
  3. Tagging: Allow Access to an Offering After Cancellation in AccessAlly

Tagging: Allow Access to an Offering After Cancellation in AccessAlly

In this article, we’ll explore how a participant can continue to have access to an offering after they’ve canceled a recurring subscription plan.

There are many ways that you can use tags to control access to your online offerings. This is one example. If you have questions about anything in this article join our next Tune Up call or Contact Support.

Create Separate Offerings

Beginner Friendly!

In the example below there are four separate offerings. This allows each Offering a member receives to have its own unique Revoke Access tag. If the member cancels the membership and the Membership Revoke Access tag is applied, the content they had while a member is not affected!

Offerings They Keep

Why Separate Offerings?

Every Offering has both access tags that allow a user to see the content on the pages and revoke tags that can hide the pages from a user’s view.

  1. A visitor can access this page if they have ANY of these tags – tags a user needs to see this page of content.
  2. A visitor cannot access this page if they have ANY of these tags – tags a user has that will hide or prevent the user from seeing this content.

Tags inside Offerings

About the Revoke Access Tag

Revoke access tags are frequently added to a user on your site when they have failed payment plan payments or have canceled a recurring payment plan.

These tags are designed to keep users from seeing the content.

This can cause friction for you as the site owner if they retain access after canceling within a single offering as the revoke tag is used on all pages. This is why it is highly recommended to use separate offerings as the content is not sharing a single revoke tag.

When are Revoke Access Tags Applied?

In the dropdown below you’ll see popular examples of how and when Revoke Access tags are applied. It’s important to see the flow of each type so you’ll know how these actions impact offerings a user is able to keep upon canceling your membership.

Open to See Examples

1. Revoke Access Tag is Manually Applied to a WordPress User

An admin user has added the tag to a single user. This user is now unable to see everything in this Offering.

Revoke Access Single User

2. The Member Clicks a Self-Cancelation Button

If you have added a Self-Cancelation button custom operation the Revoke Access tag is added after the existing paid time has ended.

Self-Cancelation Button

3. The Member Emails in and Requests to Cancel

An admin is canceling the recurring payment plan by adding the Subscription Paused tag until the end of the paid period and the Revoke Access tag is then automatically applied.

Cancel Pay Period

4. The Member Requests or is Issued a Refund

When the refund has been processed a site admin is applying the Revoke Access tag.

Revoke Immediately

5. The Revoke or Pause Subscription Webhook is Used

These are typically seen at the end of a failed payment automation or cancel automation that happens inside your CRM.

Revoke Pause Subscription Webhooks

Testing Your Setup

It’s important to test what happens when a user purchases your membership and has access to the content and what happens when they cancel, get revoked, or are no longer receiving new content in the future.

See how to test your offerings using the AccessAlly Testing Guide.

Updated on November 15, 2023

Was this article helpful?

Related Articles

NO QUESTION GOES UNANSWERED

If you have any questions, we're just an email away.

We take your success seriously, and you'll always get a speedy reply from a real person during business hours.

Laptop with the AccessAlly demo site

AccessAlly is the most flexible way to sell and elegantly deliver digital offerings. All in one place.

WATCH THE DEMO

You'll get follow-up emails about AccessAlly and new features. Opt out anytime. Full privacy policy here.