Currently, in the API Access List for an API Key in MongoDB Atlas, there is no way to associate metadata or context with each IP address or CIDR block. This makes it difficult to track the purpose or ownership of each entry, especially in environments with multiple users, services, or automation systems.

Please add support for an optional comment (description) field for each entry in the API Access List associated with an API Key. This field would allow users to provide human-readable context, such as:
- Who owns this IP address or range
- What system or service it corresponds to
- When and why it was added

Benefits:
- Improved manageability and clarity of access lists
- Easier auditing and security reviews
- Simplified troubleshooting and coordination across teams

This functionality is already present in other parts of Atlas, such as the IP Access List for project-level IPs in Network Access, so bringing similar flexibility to the API Access List would be consistent and valuable (including Terraform resources).

Additional UX request:
In the Organization Access Manager, when managing API Keys, the Actions menu does not include an explicit Edit Access List option. To modify the access list, the user must click Edit Permissions, then proceed through the next steps before reaching the access list editor. This is less intuitive and inconsistent with the Project Access Manager, where Edit Access List is available directly.
Please consider aligning the UX by adding a direct Edit Access List action in the Organization-level view as well. See attached images.