Atlas Roles for Project Management

For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

Atlas Roles for Project Management

MongoDB Atlas Agent Engine is in Public Preview and intended for evaluation and prototyping purposes only. We do not recommend production deployments during preview and expect to communicate breaking changes with you periodically. To learn more about preview feature considerations, see Preview Features.

Overview

In this guide, you can learn about the Atlas roles required to perform agent and project management tasks on the Atlas Agent Engine. Your Atlas role determines your access to both your Atlas Agent Engine settings and the agents in a project.

Your ability to manage the agents in a project depends on your Atlas project role, not your organization role.

Full Access Role Requirement

For full access to Atlas Agent Engine settings and agent management, you must have the Project Owner role on the Atlas project that contains the agent.

Important: Organization Owner Limitations

The Organization Owner role alone does not grant access to agent management. Atlas uses a hierarchical permission model, so the Organization Owner role grants implicit Project Owner access to every project in the organization. Currently, the Atlas Agent Engine doesn't use this model. Instead, the platform checks for an explicit Project Owner assignment on the project.

Role Access

Atlas roles grant access to two separate resources: your organization's or project's Atlas Agent Engine settings, and the agents themselves. The following table describes the Atlas roles and their access to Atlas Agent Engine resources:

Atlas Role Access Available Actions
Project Owner Read and write access to agentsRead and write access to settings You can perform all agent management tasks, including the following actions: Create, edit, pause, resume, and delete agents View agent logs and data Manage project access Create Atlas clusters* Manage triggers and workflowsYou can also view and change Atlas Agent Engine settings.
All other Atlas project roles, such as Project Read Only and Project Cluster Creator Read-only access to agentsRead-only access to settings You can view agents, view agent logs, and read agent data. You cannot create, edit, pause, resume, or delete an agent.You can also view Atlas Agent Engine settings, but you cannot change them.
Organization Owner Read and write access to settings You can view and change Atlas Agent Engine settings for the organization, and you can enable the Atlas Agent Engine on a project. You do not have agent management access within that project.
All other Atlas organization roles, such as `Organization
Group CreatorandOrganization Read Only` Read-only access to settings You can view Atlas Agent Engine settings for the organization, but you cannot change them. You do not have agent management access.

Next Steps

To learn how to enable the Atlas Agent Engine on an Atlas project and provision an Atlas service account, see [Set Up Atlas Resources](https://www.mongodb.com/docs/agentengine/deploy/atlas-setup.md#std-label-agent-engine-deploy-atlas-setup. To learn how to manage users and roles on your Atlas project, see Manage Access to a Project.