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.

Today, MongoDB Atlas does not provide visibility or traceability into the user creation process in the console. When a user is invited or created, there is no clear way to track the status, timeline, or potential failures of that action. This lack of tracking makes it difficult to understand whether the user was successfully created, when the action occurred, and by whom—especially in environments with strong governance and audit requirements.

What would you like to see happen?

Describe the desired outcome or enhancement.

I would like Atlas to provide tracking and status visibility for user creation events, such as:
• A clear status (e.g., pending, completed, failed)
• Timestamped lifecycle events
• Information about who initiated the action
• Optional audit or activity log entries related specifically to user provisioning

The goal is to make the user creation process observable and verifiable from the Atlas console.

Why is this important to you or your team?

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

This feature would improve operational visibility, security governance, and auditability. For teams managing multiple projects, organizations, or regulated environments, being able to track identity-related actions is critical. It reduces troubleshooting time, avoids unnecessary rework, and supports compliance and internal controls around access management.

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

Currently, we rely on manual verification, external communication (e.g., Slack or email), and indirect checks such as confirming login success or reviewing general audit logs that lack sufficient detail. These workarounds are time-consuming, error-prone, and do not scale well as the number of users and environments grows.