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

# Organization

> Get an overview of your organization and update org-level settings.

These tools surface and configure organization-level state — high-level structure (teams, roles) and a small set of org-wide settings. Most workspace administration lives in the more specific groups: [Teams](https://docs.attention.com/mcp/tools/teams.md), [Users & Roles](https://docs.attention.com/mcp/tools/users-roles.md), [Labels](https://docs.attention.com/mcp/tools/labels.md), [Scorecards](https://docs.attention.com/mcp/tools/scorecards.md), [Forecasting](https://docs.attention.com/mcp/tools/forecasting.md), [CRM](https://docs.attention.com/mcp/tools/crm.md).

## Tools

### get\_org\_overview

> [!NOTE]
>
> Scope: `mcp:read`. No parameters.

Get a summary of your organization: available roles and team structure. Useful as a first call when an assistant needs context about how the workspace is organized.

**Returns:** A Markdown summary listing roles (with type and UUID) and the team hierarchy.

**Example prompt:** *"Give me an overview of how my organization is set up in Attention."*

***

### update\_org\_settings

> [!WARNING]
>
> Scope: `mcp:write`. Requires admin role.

Update organization settings. Only the customer-facing settings are exposed via MCP — internal flags and vocabulary are managed elsewhere. At least one field must be set.

**call\_joining\_settings\_enabled** `boolean`

Enable org-level call joining settings (which controls which meetings the recording bot joins).

**enforce\_org\_bot\_image** `boolean`

Force all users to use the organization's bot image. When enabled, all users see the org bot avatar instead of their personal one.

**Returns:** A confirmation including the org name, ID, and the applied settings.


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