Can WordPress approve membership applications without a plugin?

No, WordPress core does not provide a membership application approval workflow. You can manually create users from Users > Add New and assign roles, but core does not provide a pending application queue, application review screen, membership-level access rules, or approval notifications. A membership or LMS plugin is required for a complete workflow.

What happens to a member while an application is pending?

A pending member should remain unable to access protected membership content or paid courses. The exact behaviour depends on your membership or LMS plugin, so test it with a separate account before accepting applications. Do not rely on hiding links alone; check the actual protected page, lesson, download, and member dashboard.

Where do I approve membership applications?

You approve applications in the member-management area provided by your membership or LMS plugin. With Paid Memberships Pro’s approval add-on, the documented path is Memberships > Approvals, where you can filter pending records and choose Approve or Deny. Other plugins use different menu names and may manage approval from Users or a custom applications screen.

Should I charge applicants before approving them?

Only charge before approval if your payment and refund policy supports that arrangement. Some approval systems can collect an initial payment, but denying an application may not automatically refund it or cancel a recurring subscription. If payment should happen only after acceptance, use a separate application level or send approved applicants to the paid checkout stage.

Why can an approved member still not access the course?

An approved user may still lack access because the membership level, course enrolment, role, email confirmation, or content restriction rule was not updated correctly. Check the applicant’s status in the membership or LMS plugin, confirm the correct level is assigned, clear site and page caches, and test while logged in as that user. Also check for conflicting access rules or direct enrolments.

How to approve membership applications on WordPress

Membership & LMS Time About 20–30 minutes 7 steps Updated 4 Oct 2026

The short answer

WordPress core can create users and assign roles, but it does not provide a membership application approval workflow. For a real review process, use the pending-application tools in your membership or LMS plugin, then approve the applicant and verify their protected-content access.

The route

01Define the approval workflow
02Check your existing membership tools
03Use the manual route carefully
04Configure pending applications
05Review and decide on applications
06Verify access after approval
07Take the fast route with an approval add-on

What you need

Administrator access to WordPress
A membership or LMS plugin that controls protected content
A registration or application form
At least one protected page, course, or membership level to test

Define the approval workflow

Decide what happens after someone applies. Keep applicants out of paid courses, private pages, member directories, and other restricted areas until an administrator approves them. Decide who can review applications, what evidence they need, and whether rejected applicants can apply again.

Also decide whether payment happens before or after approval. This matters because some membership systems do not automatically refund an application payment or cancel a subscription when an application is denied.

Check your existing membership tools

Open the settings and member-management screens for your current membership or LMS plugin. Look for terms such as pending, approval, application, moderation, or member status.

WordPress itself provides registration, users, and roles, but not a membership application queue. Its Users screen can create an account and assign a role, so a manual-only setup is suitable for a small, invitation-based site, not for a tracked application workflow.

Use the manual route carefully

If applications arrive by email or an external form, review each one outside WordPress and record your decision. For an approved person, go to Users > Add New, create the account, choose the least-privileged role, and use your membership or LMS plugin to grant the correct membership level or course access. WordPress documents that the user’s role controls their capabilities.

This route has no built-in pending queue, application history, approval email, rejection message, or reliable link between the form and the account. The common Friday failure is creating the WordPress user but forgetting to assign the membership level, leaving the person registered but unable to access the course.

Configure pending applications

In your membership or LMS plugin, enable approval for the relevant membership level, registration form, or course access rule. Set the applicant’s initial status to pending, customise the pending message, and confirm that administrators receive a notification when a new application arrives.

Keep restricted content protected by the membership level or course-enrolment rule, not merely by hiding a menu item. Test the form in a private browser window so you can confirm that a pending applicant cannot view protected content.

Review and decide on applications

Open the plugin’s pending-application or member-management screen and filter for pending records. Check the submitted profile fields, email-confirmation status, requested level, payment status, and any documents or answers your application requires.

Approve only after checking the correct person and membership level. If you deny the application, use the plugin’s rejection action or record the reason privately; do not delete the user until you know whether you need the application history or audit trail.

Verify access after approval

After approving an application, check that the applicant’s membership or enrolment status changed and that the approval email was sent. Open a private browser window, sign in as the applicant, and visit one protected page or lesson.

Then test a denied or still-pending account. It should be blocked from protected content. If access still works, check for cached pages, overlapping membership rules, direct course enrolments, or another plugin granting the user access.

Take the fast route with an approval add-on

For a paid membership site that needs a proper review queue, Paid Memberships Pro – Approvals is the faster route. After installing and activating Paid Memberships Pro and its approval add-on, edit the relevant membership level and set its approval requirement. Administrators can then review applications from Memberships > Approvals, filter by status, and approve or deny each applicant.

The add-on also supports approval notifications, application details, approval history, and multi-step approval setups. Pending members cannot access restricted content until approval, while denied members remain without that access. Confirm payment, refund, and subscription handling separately because denial does not automatically reverse every payment arrangement.

The fast route

Let Paid Memberships Pro do it

Adds application review, approval, and rejection workflows for vetted communities; choose it when paid membership access needs admin approval.

Get Paid Memberships Pro

Sources

paidmembershipspro.com /add-ons/approval-process-membership/?utm_source=openai
wordpress.org /documentation/article/users-add-new-screen/?utm_source=open…

Questions

Can WordPress approve membership applications without a plugin?: No, WordPress core does not provide a membership application approval workflow. You can manually create users from Users > Add New and assign roles, but core does not provide a pending application queue, application review screen, membership-level access rules, or approval notifications. A membership or LMS plugin is required for a complete workflow.
What happens to a member while an application is pending?: A pending member should remain unable to access protected membership content or paid courses. The exact behaviour depends on your membership or LMS plugin, so test it with a separate account before accepting applications. Do not rely on hiding links alone; check the actual protected page, lesson, download, and member dashboard.
Where do I approve membership applications?: You approve applications in the member-management area provided by your membership or LMS plugin. With Paid Memberships Pro’s approval add-on, the documented path is Memberships > Approvals, where you can filter pending records and choose Approve or Deny. Other plugins use different menu names and may manage approval from Users or a custom applications screen.
Should I charge applicants before approving them?: Only charge before approval if your payment and refund policy supports that arrangement. Some approval systems can collect an initial payment, but denying an application may not automatically refund it or cancel a recurring subscription. If payment should happen only after acceptance, use a separate application level or send approved applicants to the paid checkout stage.
Why can an approved member still not access the course?: An approved user may still lack access because the membership level, course enrolment, role, email confirmation, or content restriction rule was not updated correctly. Check the applicant’s status in the membership or LMS plugin, confirm the correct level is assigned, clear site and page caches, and test while logged in as that user. Also check for conflicting access rules or direct enrolments.