When an Atlas User logs in by a Federated Authentication (like Okta) there is only a "Default User Role" to control its permission, so all users get the same role. And after that, we must manually add to teams, or change their roles. It would be better to allow the IdP to set (and update) the groups/teams for each user automatically.

We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.

The functionality is available via the API:
https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/

However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.

It would be good if users are able to modify their First and Last Name after account creation.

Ability to change your username after registration and be able to re-use it should you need to.

Please consider adding 2FA support for hardware keys (Yubikey). Our company started enforcing this in our compliance policy for accessing production environments.

I would like to be able to change the cloud provider and region of a M10+ cluster.
It would be nice also to have a per-cluster connection string that does not depend on the cloud provider. So we can change the provider and region without changing the application settings.

It would be nice and convenient if lower-tier users could have the cloud backup option available (I believe m5 is the smallest but it's $9/month). I use m0 for one of my projects and I know mongodump is an option but I would much rather pay $1/month extra for backup capabilities. This project is quite small and I don't need much resources, but I would like the ability to scedule daily backups for a small fee.

Hello would you guys implement 2FA when logging in on feedback website(here) without being logged in anywhere else with the password, i really need it for security reasons...thanks