Content-protection rules control who can see what on your site. Each rule answers three questions: what to protect, who can pass, and the behavior when a visitor is blocked. Rules are evaluated in priority order by the same resolver that powers page loads, the REST API and the headless /access check — so every surface enforces access identically.
Where: WP Admin → Tiger Membership → Rules.
What to protect
| Target | Protects |
|---|---|
| Post Type | Every item of a post type (all Posts, all Pages, a CPT…) |
| Specific Page / Post | One or more chosen pages or posts |
| Term | Everything filed under a category or taxonomy term |
| Everything Except | Lock the whole site except the items you list — ideal for members-only sites |
| URL pattern (Pro) | Match by URL pattern for pages the other targets can’t express |
Who can pass
A rule’s who condition decides which visitors satisfy it. The free tier includes:
- Has plan — members on one of the selected plans.
- Status is — members in a given membership status (e.g. active, trialing).
- Logged in / Logged out — any authenticated / any anonymous visitor.
- Role — visitors with a given WordPress role.
- Specific users — an explicit allow-list.
Pro adds tenure-based (tenure days), drip (time-since-join) and metering (view-count) conditions.
Behavior when blocked
Decide what a blocked visitor gets:
- Redirect — send them to a login, pricing or restricted page.
- Teaser — show a truncated preview with an upgrade prompt in place of the content.
- Blur — render the content blurred behind an unlock prompt.
- 404 — return a not-found response, hiding that the content exists at all.
Live Preview
The rule editor includes a Live Preview so you can confirm exactly what a blocked visitor sees before saving.
How to create a rule
- Go to Rules → New rule.
- Under What to protect, pick a target (post type, specific item, term, or “everything except”).
- Under Who can pass, choose a condition and the plan(s), status, role or users that grant access.
- Under Behavior when blocked, choose redirect, teaser, blur or 404.
- Use Live Preview to check, then Save.
Troubleshooting
Protected content is still visible to non-members.
Check rule priority — a broader, higher-priority “everything except” or role rule may be allowing the visitor before your restriction runs. Also confirm the visitor isn’t an administrator (admins bypass gating).
A blocked page redirects in a loop.
The redirect target must be a page the blocked visitor can reach (a login or pricing page), not one covered by the same rule — otherwise it redirects to itself.
Changes to a rule don’t take effect immediately.
Rule resolution is cached for speed and busted on save. If you edited data directly in the database, clear the cache by re-saving the rule.