Vulnerability with admin permissions

I find it concerning that there is no distinction between the level of access/permission granted to the (primary) admin user who set up the property and the other users made admins by the primary admin. I understand the importance of admins having the same level of access, however options such as deleting a property or changing the property name should have to be confirmed by one designated “primary” admin, be it the one who set up the account or another that’s been otherwise designed as the “primary” admin. This is a concerning vulnerability which might require us to go in a different direction with our live chat platform.

I agree, having a “primary” admin with exclusive rights for critical actions like deleting or renaming a property would enhance security. It’s worth raising this as a feature request with the platform. It could prevent potential issues down the line. compassdollartree

1 Like

@usermane Hi Mark, thanks for sharing your feedback with the community.

We intend to implement granular user permissions in the future, though we can’t give you a timeframe.

Until then, it may be best to go with another platform that meets your requirements.

Regards,
The tawk.to team