> ## Documentation Index
> Fetch the complete documentation index at: https://docs.motion.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent permissions

Agent permissions control what the agent may do. They do not grant a person access to a workspace, a chat or a connected account.

For example, enabling Getty as a tool does not connect a Getty account. The workspace needs an accessible connection, and the agent must be allowed to use it.

## Actions and connections

The permissions panel groups controls into **Actions** and **Connections**. Actions include finding web assets, generating media and social posting. Connections cover the services available to the agent, including whether personal connections may be used.

Owners and Admins set organization restrictions. Workspace Managers can add restrictions in their workspace. A template or brand kit can narrow the permissions used with that resource. Message-level choices can narrow them again for a particular request.

## A lower level cannot reopen a blocked action

Permissions combine by restriction. An action must be allowed at every applicable level:

* Organization
* Workspace
* Selected brand kit
* Selected template
* Current message

A template and a brand kit are separate inputs to the run; one does not automatically override the other. If either blocks an action, that action stays blocked. Selecting a different resource can change the applicable restrictions, but cannot bypass the organization or workspace.

| Example | Result |
| - | - |
| Organization blocks image generation; template allows it | Image generation stays blocked |
| Workspace allows video generation; template blocks it | Video generation is blocked for that template |
| Workspace allows Getty; message turns it off | Getty is unavailable for that message |
| Organization blocks personal connections; participant turns theirs on | Personal connections stay blocked |

Disabled controls show where the restriction comes from, such as **Disabled by organization** or **Disabled by workspace**. Change the policy at that level if you have permission. Turning a child control on cannot lift the restriction.

## Web assets and allowed websites

The web-assets control chooses whether the agent may pull assets from the internet. If web assets are blocked, an allowed-websites list does not turn them back on.

When web assets are allowed, you can restrict their source domains. Use an exact domain such as `example.com`, or a subdomain wildcard such as `*.example.com`. A wildcard covers subdomains; include `example.com` separately if the root domain should also be allowed. These rules are domains, not regular expressions or URL-path patterns.

When several levels supply website restrictions, a source must satisfy all applicable lists. A broad list on a template cannot expand a narrower workspace list.

## Generated media and posting

Video, image, voice and music generation have category controls and model restrictions. Blocking a category prevents use of its models. Social posting is also an agent permission; it still requires the person's publishing authority for the destination account.

The agent receives a concise summary of active restrictions and their source when working on the request. The summary helps it plan around unavailable tools. The permission checks still apply when a tool is called; asking the agent to ignore a restriction does not remove it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.