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

# Organisations & Workspaces

> How Velatir structures your account into an organisation and workspaces.

## What Is an Organisation?

An organisation is your company account in Velatir. It holds your members, settings, agent defaults, and subscription in one place. Every customer starts with one organisation that represents their business.

Your organisation stores company-level settings such as your name, industry, country, and data privacy preferences. It also controls who has access and what they can do.

## What Is a Workspace?

A workspace is a space within your organisation for a specific team, department, or project. Workspaces keep activity clearly separated, and each one has its own traces and agent behaviour.

Workspaces can **nest**, so a top-level workspace such as Engineering can contain Platform and Mobile beneath it. This mirrors how your organisation is actually structured.

## How They Relate

<Steps>
  <Step title="Organisation" icon="building">
    Your company account. Holds all members, workspaces, and your subscription.
  </Step>

  <Step title="Workspaces" icon="layout-grid">
    Spaces within your organisation, which can nest. Each has its own activity and agent behaviour.
  </Step>

  <Step title="Members" icon="users-round">
    People join by invitation, or automatically when you map Microsoft Entra security groups to organisation roles. You then assign them to workspaces.
  </Step>
</Steps>

## Creating Workspaces

When you set up your organisation, you choose how workspaces are created. You can change your structure later either way.

<Tabs>
  <Tab title="Manually">
    Create and name workspaces yourself. People are added to, and moved between, workspaces by hand. This suits small and medium organisations where people rarely move between teams.
  </Tab>

  <Tab title="With Microsoft Entra">
    Workspaces are generated from your directory, and people are assigned and moved automatically as their details change. This suits medium and large organisations where people move between departments and teams. See [Microsoft Entra](/platform/microsoft-entra).
  </Tab>
</Tabs>

## When to Use Multiple Workspaces

| Scenario                  | Example                                                        |
| ------------------------- | -------------------------------------------------------------- |
| **Separate teams**        | Engineering, Marketing, and Legal each get their own workspace |
| **Nested structure**      | A Sales workspace with regional workspaces beneath it          |
| **Distinct projects**     | One workspace per product line or client engagement            |
| **Regulatory boundaries** | Workspaces for different jurisdictions or compliance regimes   |

A single workspace works fine if your whole organisation shares one context. Add more whenever you need clear boundaries between groups of activity.

## Agent Configuration Across Workspaces

You create named agents of each type and mark one as the organisation default. Each workspace either inherits that default (or the agent assigned on a parent workspace) or is assigned a specific agent. See [Configuring agents](/agents/configuring-agents).

## Organisation Settings

<AccordionGroup>
  <Accordion title="General" icon="settings">
    Update your organisation name, industry, and country. These details help Velatir tailor its insights to your context.
  </Accordion>

  <Accordion title="Members" icon="users-round">
    Invite members, or map Microsoft Entra security groups so people who sign in with Microsoft join with the right organisation role. From here you also assign members to workspaces. See [Microsoft Entra](/platform/microsoft-entra).
  </Accordion>

  <Accordion title="Data privacy" icon="lock">
    Choose when Velatir stores raw session content (Never, When flagged, or Always), and set your retention period. See [Data privacy](/security/data-privacy).
  </Accordion>

  <Accordion title="Agents" icon="sliders-horizontal">
    Set the default language for agent notifications, or follow each person's browser or OS language. See [Configuring agents](/agents/configuring-agents#localisation).
  </Accordion>

  <Accordion title="Channels" icon="bell">
    Connect Slack, Microsoft Teams, or a text-message number so high-criticality findings reach the right people. See [Escalations](/traces/escalations).
  </Accordion>

  <Accordion title="API keys" icon="key-round">
    Create ingest keys for Velatir for Desktop, the browser extension, and connectors such as [Claude Cowork](/connectors/claude-cowork). Keys are shown once.
  </Accordion>

  <Accordion title="Data exports" icon="download">
    Request an export of your data for your own record-keeping or a data-subject request. See [Data storage & encryption](/security/data-storage-and-encryption).
  </Accordion>

  <Accordion title="Support" icon="life-buoy">
    Grant Velatir's team time-limited access to your organisation, or revoke it immediately. Off by default. See [Data privacy](/security/data-privacy#support-access).
  </Accordion>

  <Accordion title="Subscription" icon="receipt">
    View your current plan and invoices.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Roles & permissions" icon="shield" href="/platform/roles-and-permissions">
    What each role can do at the organisation and workspace level.
  </Card>

  <Card title="Microsoft Entra" icon="users-round" href="/platform/microsoft-entra">
    Assign organisation roles from security groups, or generate workspaces from your directory.
  </Card>
</CardGroup>