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

# Manage

> The Manage administration area is the top-level context for organization administration in Kodexa, gathering organization profile, teams, secrets, intakes, custom modules, subscriptions, the model library, and concurrency in one place.

**Manage** is a top-level context in the Kodexa platform, alongside **Studio**, **Workflow**, and **Knowledge**. It is the home for organization administration: profile and feature settings, team access, secrets, intakes, custom modules, subscriptions, the model library, and execution concurrency.

Manage is served under the `/m` route prefix, and switching to it (from the context switcher) takes you to your organization's Manage home at `/m/o/{organizationId}/home`.

<Note>
  The Manage context is role-gated. It is only visible to users who hold the `MANAGE` role or the `PLATFORM_ADMIN` role. Users without either role do not see the Manage context in the switcher.
</Note>

## Access, Controls and Reporting

The Manage organization home presents a single **Access, Controls and Reporting** grid. Each card opens an administration surface for the current organization:

<CardGroup cols={2}>
  <Card title="Organization Profile" icon="building">
    Manage the organization name, description, and organization-level features (see [Features](#organization-features) below).
  </Card>

  <Card title="Teams" icon="people-group">
    Manage the organization's teams and their access.
  </Card>

  <Card title="Document Tags" icon="tag">
    Define tags used to categorize documents across the organization.
  </Card>

  <Card title="Secrets" icon="key">
    Manage the organization's secrets and credentials used by modules and integrations.
  </Card>

  <Card title="Intakes" icon="inbox">
    Configure document intake endpoints for automated ingestion.
  </Card>

  <Card title="Custom Modules" icon="cube">
    View and manage the custom modules deployed to this organization.
  </Card>

  <Card title="Subscriptions" icon="credit-card">
    Manage billing and subscriptions for the organization.
  </Card>

  <Card title="Model Library" icon="brain">
    Browse the available AI models, providers, and pricing.
  </Card>

  <Card title="Concurrency" icon="scale-balanced">
    View execution concurrency limits and scheduling weight for the organization.
  </Card>
</CardGroup>

<Note>
  These administration surfaces previously lived under Studio's Organization Home. They now live in Manage. Studio's Organization Home retains its project and knowledge-architecture entry points (Projects, Project Templates, Project Status, Activity Plans, Task Statuses, Knowledge Feature Types, and Knowledge Types); the organization administration cards have moved here.
</Note>

## Organization features

Open **Organization Profile** from the Manage grid to reach organization settings. In addition to the **Overview** tab (name, description, and support access), there is a **Features** tab with organization-level toggles.

### Strict team matching

Controls how take-next assigns tasks with respect to team matching.

* **Off (default)** — soft matching. Take-next prefers team-matched candidates and falls back to team-null candidates when there is no team match.
* **On** — strict matching. Only team-matched candidates are assignable; team-null candidates are excluded.

Enabling this sets the organization's `features.teamMatchingMode` to `strict`; turning it off clears the key and returns to the soft default.

### Presence tracking

Controls whether the platform collects per-user presence and activity telemetry for this organization.

* **Off (default)** — no per-user presence or activity telemetry is collected.
* **On** — the UI emits periodic presence heartbeats (active/idle, tab visibility) and task-open events tied to named users, surfaced on the organization's activity dashboards.

This is an opt-in, customer-controlled switch backed by `features.presenceTrackingEnabled`. Enabling it is a deliberate decision by the organization as the data controller and carries the associated responsibilities for the telemetry collected. See [Organizations → Organization Features](/concepts/organizations#organization-features) for the collection detail and legal considerations.