How to restrict content based on points and achievements

Write the rule in plain language before configuring anything. For example: a member needs 500 course points, the Module 1 complete achievement, or both. Decide whether requirements are cumulative, whether guests should see a login message, and whether members can pay or spend points to bypass the rule.

Keep each rule easy to explain. Combining several achievements and point thresholds can make support requests difficult when a member believes they have qualified.

WordPress alone does not provide a points ledger, achievement engine or achievement-based content gate. A genuine manual implementation therefore means building a small plugin that records each user’s points and achievements, checks the current logged-in user, and replaces or withholds protected content when the rule is not met. WordPress recommends keeping site functionality in a plugin rather than relying on a theme.

You would normally expose the check through a custom enclosing shortcode or a block, then place the protected material inside it. WordPress shortcodes are designed for dynamic content and must return their output rather than print it.

This route is fine for a bespoke site with one or two simple rules, but you must also build point-awarding events, achievement administration, audit history, reset rules, access messages and security checks. Do not put the whole system in a theme’s functions.php; changing themes can remove the functionality.

With a gamification plugin, create the points type and decide how members earn it, then create the achievement types and the individual achievements that qualify users for access. Use names members will understand, such as Completed quiz 1 rather than an internal identifier.

Check the award rules carefully. Duplicate triggers, imported orders or repeated lesson views can award points more than once, which may give access earlier than intended. Keep an activity or earnings log so you can investigate disputed access.

Open the post, page, lesson or other public post type you want to protect and enable its content restriction settings. Add requirements for points earned, a particular achievement, an achievement type, or all achievements in a type. The Restrict Content documentation describes these requirement choices and notes that users must meet all configured requirements.

For an entire lesson, choose access restriction or replace the full content. For a teaser, explanation or bonus section, use an inline restriction instead. Whole-post access and partial-content restriction are different jobs, so do not use a section shortcode when the lesson URL itself must be protected.

Decide what an unqualified visitor sees: a login prompt, an excerpt, a trimmed preview, a custom message or a redirect to a course-prerequisite page. Restriction tools commonly separate access, content, links and images; access restriction is the strongest option because it prevents direct viewing of the post.

Test four cases before publishing: a logged-out visitor, a logged-in member below the threshold, a member who has just qualified, and an administrator. If the result is wrong after an award, clear the site and browser cache and check that your page cache is not serving an anonymous copy to a logged-in user. Cached membership pages are a recurring source of stale restriction messages.

For the quickest no-code setup, use GamiPress with its Restrict Content add-on. Create the points and achievement rules, edit the target post, enable the GamiPress – Restrict Content box, add the requirements, and choose the replacement or redirect shown to users who do not qualify. It supports whole posts and pages as well as inline content restrictions.

If you want optional pay-to-unlock access, configure the restriction to allow access by expending points, or use points as the only unlock condition. For inline content, use the documented restriction shortcode and close it properly; an unclosed enclosing shortcode can make the rest of the page behave unexpectedly.

GamiPress is a sensible recommendation when you need achievement- and points-based gates across membership pages, lessons or custom post types without maintaining the tracking and access logic yourself.