What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

Some teams may integrate users management with external tools/systems. This may cause conflict if a user is directly created via Atlas UI and not via the external system.

What would you like to see happen?

Describe the desired outcome or enhancement.

The ability to lock these GUIs so it will be available only for read-only.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

For big distributed organizations this would help to avoid creation of users directly. As part of the requirement one could be able to add a banner message when locking the GUI so users can read it for awareness and further instruction.

What steps, if any, are you taking today to manage this problem?

Users created by mistake are eventually revoked from the external system and they will contact MongoDB support, or the internal organization support who will be aware of the situation and fix it by creating from the correct path. When it is MongoDB support, it can take a while until the scenario is fully understood to then find internal directions in the customer IT side.