Restrict Content Pro ties a membership to a WordPress user, and WordPress ties each user to one login and one email address. On a site selling to individuals that is exactly what you want. On a site selling to families it produces a familiar mess: either the whole household shares one login, or the parent has to invent an email address for a child who does not have one.
This guide is deliberately specific about what you can do on an RCP site today with profiles, and what you cannot. Some of it works with no configuration at all. One part, sharing a single membership across everyone in the household automatically, does not, and it is better to know that up front than to discover it after installing something.
Where families break an RCP site
Two failure modes, and you have probably seen both in your support inbox.
The shared login. One account, one membership, three children taking turns. Access works, but nothing that depends on knowing who is using the site does. If your restricted content includes any kind of course, tracker or progress, the children overwrite each other. Certificates come out with the wrong name. Parents report it as a bug in your site.
An account per child. Correct, and heavy. Each child needs an email address, a password and a separate RCP registration. The parent becomes an administrator of logins, and the shared family tablet gets logged out and back in several times a day. A meaningful share of parents simply do not finish.
What works today with profiles
ProfileSwitch puts a profile picker after login. The household keeps one email address and one password, and every profile behind that login is a real WordPress user. Because RCP attaches memberships to WordPress users, this gives you three things immediately, with no integration and no configuration on the RCP side.
- A membership per child. The parent switches into a child’s profile and registers that child for whichever RCP membership level suits them. RCP records it against that child’s user, because that is genuinely who is checking out. One child can sit on your starter level while another sits on your advanced one.
- Correct content restriction per person. RCP’s access rules evaluate against the active user, so each profile sees exactly what their own membership unlocks and nothing more.
- No email address for a child. Child profiles are created with plus-addressed email addresses derived from the parent’s own, so RCP receipts, renewal notices and expiry warnings all land in the parent’s inbox.
If your restricted content includes courses, this is also where the shared-login problem disappears. Any LMS that stores progress per user, which is all of them, records each child’s work separately once each child is their own profile. That covers Tutor LMS, LearnDash, LifterLMS and LearnPress among others.
What does not work today: automatic membership sharing
If your business model is one family-tier purchase that covers everyone, ProfileSwitch cannot do that automatically on Restrict Content Pro. Membership sharing, where the parent buys once and every child profile inherits that access, exists as a dedicated integration for Paid Memberships Pro only. There is no equivalent RCP integration at the time of writing.
On an RCP site you have two honest options. Either the parent buys a membership per child, which is the flow described above and often earns more per household anyway, or you grant each child profile a membership manually from the RCP admin after the parent signs up. The manual route is fine for a handful of families and does not scale to hundreds.
Setting it up
- Install ProfileSwitch and enter your licence key on the settings page. Your RCP levels, restrictions and gateway are untouched.
- Create the profile switcher page in one click, so logged-in households land on a picker.
- Decide your family pricing before you announce anything: a membership per child, or one purchase plus manual grants.
- Set a PIN on the parent profile from the PINs and parental controls screen, so children cannot reach billing or cancel a membership.
- Leave existing members alone. Accounts with one profile behave exactly as before, so nothing changes for your individual subscribers.
Frequently asked questions
Is there a Restrict Content Pro integration?
Not at the time of writing. ProfileSwitch ships dedicated integrations for Paid Memberships Pro, WooCommerce and BuddyPress. RCP still works with profiles, because each profile is a real WordPress user and RCP attaches memberships to users, but the parent’s membership is not automatically shared with child profiles.
Can each child have a different RCP membership level?
Yes. Each profile is its own WordPress user with its own membership state, so one child can be on a beginner level and another on an advanced level, both under a single household login.
Who receives RCP renewal and expiry emails?
The parent. Child profiles use plus-addressed email addresses derived from the parent’s address, so every RCP notification for every child arrives in the parent’s inbox with no custom configuration.
Does the parent’s card get charged for each child?
Yes, if you charge per child. The parent switches into each child’s profile and checks out, entering their card as normal, so your gateway sees one payer buying several memberships. They can do it in a single session without logging out.
Can I test this before buying?
Yes. ProfileSwitch Lite is free on WordPress.org and supports up to 10 profiles per account, which is enough to confirm on a staging copy that RCP restricts content correctly per profile before you commit. PINs, parental controls and profile managers are in the full version.
Give each child their own membership, not their own password
One household login, a profile per child, and Restrict Content Pro treating each one as its own member. 14-day money-back guarantee.