Hi.

After reviewing another thread on this subject (https://tmsplugins.ticksy.com/ticket/3046957/), it' still not clear to me whether the problem has been resolved, and it seems like the best solution may be simpler than the approach taken.

Here's what we need:

For both existing and new WordPress users, we need them to automatically be able to use Ameila for booking, provided they are logged in to WordPress.

If the user doesn't have a WordPress account, we redirect them to our existing registration page and let WordPress manage the user's identity.

We can manually assign the other roles for employees and admins to our existing staff.

Which begs for this question:

Why not simply provide the option in the settings to grant every user who has the subscriber role in WordPress access to Amelia as a customer? That would accomplish everything being addressed above for both existing and new users. To accomplish that, it shouldn't be necessary to make any significant modifications to your code other than treating the subscriber role as equivalent to your custom role. That could easily be set using a define() for the purpose of configuration rather than hard-coding a role name in your code.

Please let me know your thoughts.

Thank you.

Or... rather than subscriber, allow the option to use a role that exists with WooCommerce such as "Customer" to facilitate access to the Amelia customer facing functionality.

You can ignore this ticket.  I see now that you have an entirely independent identity table (wp_amelia_users) with its own passwords, with the type being the field that assigns the roles for your users.  That would make sense for a stand-alone application, but I'm not sure why you would choose to use this approach for a WordPress plugin. It creates an unnecessary layer of user identity management that  can potentially confuse customers as well as site admins. That's not a good customer experience.  No other plugin that I've seen does this.

Thanks and regards.