We're Moving to a New Support Platform – Starting June 1st!
We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.
You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.
While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.
We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.
Thanks for your continued support and trust – we’re excited to bring you an even better support experience!
I just tried to remove an employee which created from existing WP user who has an Amelia-employee role, after delete it and re-add it again, system tells this email is an existing email address and I cannot use it. I think it might not be a good idea. Since removing and re-adding a employee is a very common thing . Even delete a user, system should remove them from Amelia User table clearly. Otherwise, if re-adding again, we have to re-assign them another email, I think it might be a bug. Thanks
Hi Jeffrey,
thank you for reaching out to us
Have you managed to locate and delete the user? This is in case that you still may need the user but not the employee, but I do see the inconvenience now.
Please let me know if you managed to unhook and delete them; if you want I can do so for you.
Thank you for the response, do you mean that I need to delete this WP user and re-add him/her as a WP user, then I add them as an Amelia provider to accomplish my purpose? if so, that may not be a good idea, because sometimes or some faulty operations may cause unexpected results. Hope you guys can consider this small flaw
Hi Jeffrey,
thank you for the kind reply!
This would be technically the safest way to go because the WP user is created first and then an employee; and then you connect them. Did you face any issues in the past (besides now) where deleting a WP user caused some other problems?
Thank you for you guys considering my suggestion, however, I have used WP user role access module to set access for specific user roles for the panel page, other users will be redirected to WP user's login form, in that way, WP employee and Customer will not access Amelia's log-in form and will be forced to log in with WP login form. :)
Hi Jeffrey,
Have you been using the User Role Editor? It's convenient to change around some capabilities of different roles (unfortunately it cannot unify them for the panel, I'm afraid)
Lol, I set up the access for the page to only amelia-employee or amelia-customer roles, other users and guests will be redirected to a page with the login form, so if the amelia-employee and customer will have access to the panels' page, other users will not be there otherwise.
I am not using the User role editor, I am using Gamipress's restrict content addon. and setting access restriction for specific user roles, otherwise, redirect users to another page.
I have tested it many times, it works fine :)
I'm glad it works Jeffrey, thank you for letting me know - asking because Role Editor can be useful but it cannot do a lot in that case (especially because Amelia can't recognize it's "custom" roles).
I have not yet test with User Role Editor, some of the membership plugins may work with these requirements, it is just a redirection if user role match presetting, allow it, otherwise redirect it