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

# Organization settings

> Your Organization is the top-level home for your whole company in Cura — every workspace, channel, and team member lives inside it.

Your **Organization** is the top-level home for your whole company in Cura — every workspace, channel, and team member lives inside it. This guide shows you where to find your organization settings and what each one controls.

By the end, you'll have named your organization, chosen who handles escalations, and set the language Cura uses.

## Before you begin

* You'll need **Admin** access — organization settings are managed by an admin (you'll see who under the organization name as *Managed by*).
* Decide which admin should receive escalations when the AI hands a conversation to a person.

<Note>
  Organization settings apply to your *whole* account. Details that change per location — location, timezone, contact details, Quiet Hours — live in [Workspace settings](/settings/workspace-settings) instead.
</Note>

***

<Steps>
  <Step title="Open organization settings">
    * Go to **Settings → Organization**.
    * You'll see the organization name at the top, with the admin who manages it shown beside it.
  </Step>

  <Step title="Set your organization name and description">
    * **Organization name:** use your company or brand name. This is how your business is identified across Cura.
    * **Description:** a short line describing your business. Optional, but it helps keep things clear when your team grows.
    * **Click Save** to apply your changes.

    <Check>Your organization is named and ready for the rest of your team.</Check>
  </Step>

  <Step title="Choose your escalation manager">
    When the AI flags a conversation for a human (an **escalation**), Cura needs to know who to route it to.

    * **Escalation Manager:** pick an admin from the list. This admin receives escalated conversations when no workspace manager is assigned to handle them — so they're the organization-wide fallback.
    * The list shows each admin's name and email so you can pick the right one.
    * Your choice saves the moment you select it — there's no separate Save step for this field.

    <Note>
      You can also set an escalation handler **per workspace**, which takes priority over this organization-level fallback. See [Escalation contacts](/team/escalation-contacts).
    </Note>

    <Tip>
      Choose someone who's usually reachable during business hours. If escalations sit unanswered, customers wait — and that's exactly what Cura is built to prevent.
    </Tip>
  </Step>

  <Step title="Set the language">
    * **Language:** choose **English** or **ไทย (Thai)** as the default interface language for your organization.
    * **Click Save** to apply your name, description, and language together.

    <Check>Your organization is configured. Naming, escalation routing, and language are all set.</Check>
  </Step>
</Steps>

***

## What lives where

It's easy to mix up the two levels of settings. A quick guide:

* **Organization settings** — company-wide: name, description, escalation manager, default language.
* **Workspace settings** — per location: location, timezone, contact details, Quiet Hours, and the Knowledge Base.

<Frame>
  <img src="https://mintcdn.com/cura-2d9288ab/pPBYeI1qPGlrN2Ia/images/settings/organization-settings.png?fit=max&auto=format&n=pPBYeI1qPGlrN2Ia&q=85&s=fb073aeb63bcf688d2074667ff1a20cd" alt="Organization settings in Cura with the organization name and escalation contact" width="2880" height="1560" data-path="images/settings/organization-settings.png" />
</Frame>

***

### Related articles

* [Workspace settings (location, timezone, contact details)](/settings/workspace-settings)
* [Your profile](/settings/your-profile)
* [Knowledge settings](/settings/knowledge-settings)
* [Workspaces explained](/team/workspaces-explained)