Panel Alpha places a strong focus on collaboration, but we’re encountering an issue with clients using the WP Activity plugin in WordPress. They can see that we log in using their admin accounts, which happens due to how we access WP Admin via Panel Alpha.
Our team consists of Web Developers, Content Writers, Graphic Designers, Technical Teams, and PPC Managers, all of whom need access to various websites. Ideally, Panel Alpha should have a feature that automatically assigns WordPress users to staff members upon login. This way, when a team member accesses a site, it reflects their actual user account instead of a shared admin account.
While manually creating individual users in WordPress is an option, it’s not practical for a large team. This feature would improve security, streamline workflow, and ensure clients can see exactly who is working on their site eliminating confusion where they might think they logged in themselves.
1 Like
Hello Armand
This is a great idea! I am not sure exactly on how would it work technically so we’d need to make a little research here. The few issues that I could think of:
- how would the users be recognized that someone is Web Dev or a Content Writer? Are there separate users in the system or administrators in PanelAlpha?
- what privileges should they get in WP Admin?
- what about cleanup of these users?
It should also become more easy once we introduce a new WP Plugin later this year that will take care of a few other features (like migrations).
1 Like
Hi there,
we’ve come across a similar issue, having clients use the same shared admin account instead of creating WordPress users, then wondering why they have full access to WordPress. Surely, after communicating the correct usage they understand it, but it’s unintuitive for non-techie people to have two users in two dashboards.
I think a good approach would be to allow binding a pa user to a WP user under advanced/wordpress-users which then enforces the SSO into that user. If not set, it’ll just SSO into the default WP admin user.
But then it’s still tricky to simplify / automate this on pa user creation / invitation.