If you’ve ever needed to support family or household accounts in WordPress, you’ve probably relied on email aliases, often implemented using plus addressing (for example, [email protected]).
This approach is extremely common. It works with WordPress core, it keeps LMS and membership plugins happy, and it lets multiple users share a single inbox. But while email aliases solve a technical limitation, they also introduce user-facing complexity that tends to surface over time. This article looks at why plus addressing is so widely used in WordPress, its limitations, and how that complexity can be handled more cleanly.
Why email aliases are so common in WordPress
WordPress is built around a simple assumption:
One user = one email address = one person
That assumption works well for blogs and personal sites, but it falls apart for real-world use cases like:
- Families with multiple children taking courses
- Households sharing a membership
- Youth programs where parents manage multiple participants
In these cases, each individual needs:
- Separate progress and activity data
- Independent access and reporting
- Compatibility with existing plugins
At the same time:
- Children may not have their own email addresses
- Parents don’t want to manage multiple inboxes
- Site owners want to avoid custom user models
Email aliases are the compromise that makes all of this possible.
How plus addressing solves the problem (technically)
Plus addressing allows variations of the same email address to all deliver to one inbox:
From WordPress’s perspective, these are distinct users. From the parent’s perspective, everything goes to one inbox.
This makes plus addressing attractive because it:
- Requires no changes to WordPress core
- Works with LMS and membership plugins
- Keeps user data cleanly separated
- Avoids building custom account systems
From an implementation standpoint, it’s a practical and reasonable solution.
Where email aliases start to cause problems
The issue with plus addressing isn’t technical — it’s experiential. Over time, these issues lead to friction in places that aren’t obvious at first.
Login confusion
Parents forget which alias belongs to which child. Logging in becomes trial and error, especially on shared devices.
Password resets feel ambiguous
All reset emails go to the same inbox, but it’s not always clear which account they apply to.
Support tickets increase
Support teams end up untangling questions like:
- “Which email did we use for this child?”
- “Why is progress missing?”
- “I logged in but I’m seeing the wrong data”
Admin context is weak
In the WordPress dashboard, it’s difficult to tell which users belong to the same household without strict naming conventions or notes.
None of this means email aliases are a bad solution. It means they were never intended to be a user-facing abstraction.
The core issue: abstraction leaking to humans
Plus addressing is a technical workaround that works because WordPress needs distinct users.
The problem is that the workaround becomes part of the user experience.
Parents are asked to think in terms of:
- Multiple logins
- Email syntax
- Account mapping
What they actually want:
- One login
- Multiple people
- Separate data
This gap between implementation and experience is where friction appears.
A different approach: keep the alias, hide the complexity
This is the problem ProfileSwitch was designed to address.
Instead of asking families to manage email aliases and multiple logins themselves, ProfileSwitch:
- Maintains one primary account
- Creates multiple profiles under that account
- Keeps each profile’s data, progress, and access separate
- Remains compatible with existing WordPress plugins
Important transparency note
ProfileSwitch still relies on standard WordPress users and email addresses under the hood (including plus-addressed aliases) because that’s the most reliable way to integrate with the WordPress ecosystem.
The difference is where the complexity lives.
With ProfileSwitch, the system manages the aliases. Users never have to see or think about them.
How the two approaches compare in practice
| Manual Email Aliases | ProfileSwitch | |
| Single inbox | ✅ | ✅ |
| Separate User Data | ✅ | ✅ |
| Single login to manage | ❌ | ✅ |
| Profiles linked in admin dashboard | ❌ | ✅ |
| Plugin compatibility | ✅ | ✅ |
Both approaches are valid. One just treats plus addressing as an internal detail instead of a user responsibility.
When managing aliases manually is fine
Manual email aliases may be sufficient if:
- You have a small number of families
- Users are technically comfortable
- Support requests are rare
- The system isn’t growing quickly
In those cases, the workaround may never become painful.
When hiding the workaround matters
Abstracting email aliases away becomes valuable when:
- Parents regularly contact support
- Progress or access issues are common
- The site is growing
- The workaround starts to feel fragile
At that point, the question isn’t whether plus addressing works — it’s whether users should be exposed to it.
Final thoughts
Email aliases and plus addressing are a clever and widely used way to support multiple users under one email in WordPress. They exist because WordPress doesn’t natively support family or household accounts.
ProfileSwitch doesn’t replace that foundation. It builds on it by turning a technical workaround into a clean, intentional user experience. If you’re ready to explore how it could simplify multi-profile accounts on your site, you can check out our pricing and get started here.
Leave a Reply