> ## Documentation Index
> This page is part of the Cloudinary Assets product. Fetch the complete documentation index for Cloudinary Assets at: https://cloudinary.com/documentation/llms-cloudinary-assets.txt?referrer=docpage and then use it to discover all relevant pages before exploring further.
> If your task extends beyond this product, fetch the top-level index covering all Cloudinary products and topics at: https://cloudinary.com/documentation/llms.txt?referrer=docpage

# Agent settings


Safety and trust are very important to us, and we've implemented a series of guardrails to make sure your experience with Cloudinary AI agents is reliable. See [Permissions and safety](dam_ai_agents#permissions_and_safety).

This page covers agent configuration and permissions, which are key guardrails for using AI agents. As an administrator, you can control whether agents are available in the Chat with AI panel, which individual agents are enabled, and who has permission to access them.

> **NOTE**: Make sure you can access [AI agent settings](https://console.cloudinary.com/app/settings/ai-agents) in Console Settings. If the settings area is unavailable, contact an administrator who manages roles and permissions.Cloudinary is gradually rolling out Roles and Permissions. See [Roles and Permissions vs. legacy](dam_admin_users_groups#roles_and_permissions_vs_legacy) to find out which system your product environment uses and the differences between them.If you have Roles and Permissions, you can assign agent permissions via a system role configured with those permissions, or by creating a custom role that contains the necessary permissions (Enterprise customers only). For more information, see [Agent roles and permissions](#agent_roles_and_permissions)In the [Legacy system](dam_admin_users_groups), only Master Admins have access to agents.

## Make agents available in the Chat with AI panel

Use this global control, available on the [AI Agents](https://console.cloudinary.com/app/settings/ai-agents) page of the Console Settings, to make AI agents available in the Chat with AI panel for a product environment.

![Agent settings](https://cloudinary-res.cloudinary.com/image/upload/f_auto/q_auto/bo_1px_solid_grey/agent_settings.png "thumb: w_700,dpr_2, width:700, with_url:false, with_code:false, popup:true")

When **Not available**:

* Agent chat entry points are unavailable from the Chat with AI panel.
* Individual agent toggles don't grant agent access.
* Existing work remains unchanged, but users can't start new agent interactions from the Chat with AI panel.
* The Workflow Agent prompt box isn't available on the MediaFlows home page.

When **Available**:

* Users can access enabled agents from the Chat with AI panel in Console Options.
* Individual agent settings determine which specific agents are accessible.

## Make individual agents available in the Chat with AI panel

Use individual toggles to control which agents your users can access from the Chat with AI panel.

Configure each agent based on operational readiness, team needs, and governance requirements:

* **Taxonomy Agent** for creating, improving, and maintaining taxonomy and metadata quality at scale.
* **Search Agent** for helping teams find the right assets faster using natural-language search.
* **Workflow Agent** for turning operational intent into governed [MediaFlows](mediaflows) automations.

> **NOTE**:
>
> Turning off the **Workflow Agent** toggle also removes the Workflow Agent prompt box from the MediaFlows home page, the same as making agents unavailable altogether. There's no separate MediaFlows setting: users can't start a Workflow Agent conversation from MediaFlows while the agent is switched off here.

## Agent roles and permissions

If your account uses the granular [Roles and Permissions](dam_admin_permissions) system, you can grant access to AI agents using system or custom roles.

### Map system roles to agent permissions

This table shows which agent permissions are included in each [system role](dam_admin_system_roles_permissions). [Assign](dam_admin_role_management#assign_roles) the appropriate system role to grant agent access.

{table:class=no-borders-permissions overview} Permission | Master Admin | Admin | Tech Admin | Media Library Admin | Media Library User | MediaFlow Admin |
|----------------|---|---|---|---|---|---|
| Manage agent settings | ✔️ |  | ✔️ | ✔️ |  |  |
| Use the Taxonomy Agent | ✔️ | ✔️ | ✔️ | ✔️ |  | ✔️ |
| Use the Search Agent | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |
| Use the Workflow Agent | ✔️ | ✔️ | ✔️ | ✔️ |  | ✔️ |

### Agent permission policies

To [create custom roles](dam_admin_role_management#manage_roles_with_granular_permissions) that grant agent access, include the following policies. For more information about policies, see [Permissions, system roles and policies](permissions_system_roles_policies). 

{table:class=no-b small-1stcol small-font-last-col overview} Policy ID | Name | Description | Policy Statement |
|----------|-----|-------------|----------------|
| cld::policy::global::agents::manage | Manage agent settings | View and manage all agent settings. | permit(principal, action == Cloudinary::Action::"update_agent_settings", resource is Cloudinary::ProductEnvironment); |
| cld::policy::global::agents::taxonomy::invoke | Use the Taxonomy Agent | Use the Taxonomy Agent to create, improve, and maintain metadata and taxonomy at scale. The agent can only view content and perform actions permitted to the user. | permit (principal, action, resource == Cloudinary::Feature::"cld::global::agent::invoke");permit (principal, action == Cloudinary::Action::"invoke", resource == Cloudinary::Agent::"taxonomy"); |
| cld::policy::global::agents::search::invoke | Use the Search Agent | Use the Search Agent to find assets with natural-language search. The agent can only view content and perform actions permitted to the user. | permit (principal, action, resource == Cloudinary::Feature::"cld::global::agent::invoke");permit (principal, action == Cloudinary::Action::"invoke", resource == Cloudinary::Agent::"search"); |
| cld::policy::global::agents::workflow::invoke | Use the Workflow Agent | Use the Workflow Agent to create and manage automated MediaFlows using natural-language instructions. The agent can only view content and perform actions permitted to the user. | permit (principal, action, resource == Cloudinary::Feature::"cld::global::agent::invoke");permit (principal, action == Cloudinary::Action::"invoke", resource == Cloudinary::Agent::"workflow"); |

> **See also**:
>
> * [Cloudinary AI agents (Assets)](dam_ai_agents)

> * [Roles and permissions overview](dam_admin_permissions)

> * [Product environment console settings for Assets](dam_admin_product_environment_settings)