What’s the issue?Amelia is designed to treat each user role in your WordPress site (Administrator, Amelia Manager, Amelia Employee, Amelia Customer) as a separate user context — and each of these roles has its own set of permissions and responsibilities within the system.
If the same email address is used across multiple roles — for example:
An Admin trying to book an appointment as a Customer
An Employee using their work email to act as a Customer
An Amelia Manager also assigned as a Customer or Employee
— the system will run into permission conflicts and role confusion, such as:
Errors like:
“Email already exists with different name. Please check your name.”
Booking visibility issues — the user may not see their appointments properly
Dashboard access problems or restricted actions based on conflicting roles
Data not being saved or linked correctly between roles
Amelia enforces role separation to ensure that permissions, access rights, and user data are applied and managed correctly.
What’s the solution?Each Amelia-related role must be tied to a different email address.
This ensures clear role separation and prevents permission-related conflicts.
This applies to:
WordPress Admins
Amelia Managers
Employees
Customers
If one person needs to operate under multiple roles (e.g., manage Employees and also book appointments), they must register each role with a separate email address.
You can learn more about proper role setup in Amelia here:
https://wpamelia.com/users-and-roles/
