Skip to main content
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.
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.

​
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:

Organization Profile

Manage the organization name, description, and organization-level features (see Features below).

Teams

Manage the organization’s teams and their access.

Document Tags

Define tags used to categorize documents across the organization.

Secrets

Manage the organization’s secrets and credentials used by modules and integrations.

Intakes

Configure document intake endpoints for automated ingestion.

Custom Modules

View and manage the custom modules deployed to this organization.

Subscriptions

Manage billing and subscriptions for the organization.

Model Library

Browse the available AI models, providers, and pricing.

Concurrency

View execution concurrency limits and scheduling weight for the organization.
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.

​
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 for the collection detail and legal considerations.