> ## 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](/mcp/tools/teams), [Users & Roles](/mcp/tools/users-roles), [Labels](/mcp/tools/labels), [Scorecards](/mcp/tools/scorecards), [Forecasting](/mcp/tools/forecasting), [CRM](/mcp/tools/crm).

## Tools

### get\_org\_overview

<Note>Scope: `mcp:read`. No parameters.</Note>

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.</Warning>

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.

<ParamField query="call_joining_settings_enabled" type="boolean">
  Enable org-level call joining settings (which controls which meetings the recording bot joins).
</ParamField>

<ParamField query="enforce_org_bot_image" type="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.
</ParamField>

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