Organizations #

Objective and access #

The Settings → Organizations menu manages multi-tenant borders. It is visible to administrators; only the super admin works on multiple organizations.

Screen and operations #

The list shows name, description and status. Create or modify these fields, as well as risk thresholds where they are offered. The deletion is logical in order to preserve history and responsibilities. Always research the target organization before a destructive operation.

Rules and good practices #

All linked resources must belong to the same organization. Avoid deactivating a tenant before verifying users, documents, actions and retention obligations. A resource from another tenant generally responds 404.

Example and links #

A subsidiary can have its own users, thresholds and registers, without access to group data. See Users and Architecture.

Complete procedure #

1. Log in as an authorized administrator.
2. Open Settings → Organizations then create the entry.
3. Use the official name and a description to identify the scope.
4. Leave the status active to allow connections.
5. Save, create tenant administrators and then check the risk thresholds.

Before a change, check exports, procedures and integrations using the name. Before deactivation, check active users, open actions, shared documents, retention obligations and backups.

Checks and errors #

• a tenant administrator can connect;
• no data from another organization is visible;
• the matrix uses the expected thresholds;
• the mutation appears in the log.

A 404 can hide an identifier from another tenant; a 403 instead indicates an insufficient role. Never move a resource between tenants by directly modifying the identifier.