Introduce permissions into Ngrok Ingress Controller webapp.

[nsgoneape]

Description

Currently, my production and development domains are both running on the same Ngrok account, which may not be ideal. Recently, a developer accidentally deleted my production domains, and I had to go through the lengthy process of restoring them. This incident has highlighted a crucial need for role-based permissions within the Ngrok web app. Having this feature would help prevent accidental modifications or deletions in the production environment by limiting access and actions based on user roles.

Use Case

The primary use case for this feature is to provide administrators with the ability to assign specific permissions to different users, especially in environments where multiple domains (both production and development) are managed within the same account. By implementing user roles and permissions, it would be possible to restrict access to critical configurations and prevent accidental changes or deletions in production, thus minimizing downtime and enhancing security.

Related issues

None known at this time.

[russorat]

@nsgoneape thanks for the issue. Adding true role based access control to the ngrok platform is currently on our roadmap, which would help solve for this issue. I don't have an ETA of when it will be available, but I will add you to our list of alpha/beta users and will reach out as soon as we have something to test out. Thank you!

[nsgoneape]

Hey @russorat, how are you doing?

Is there an update on this feature? My organization is making great use of your product. But as I am adding more people, the riskier running my operations via ngrok is becoming. At any moment a silly developer can completely kill my production domains.