Organization Management

Scope

Organization design is what keeps technicians, assets, and service work inside the right boundary. This guide keeps the operating model and removes private implementation detail from the internal manual.

Single Source of Truth — Cadres Organization Management Manual Covers: creating organizations, managing organizations, location management, support access management

Creating Organizations

Each organization gets a unique secret for agent registration (auto-generated). When an organization is created, the backend also seeds a default Location so the org is immediately usable and runs the onboarding seeders for default alert/compliance data.

Managing Organizations

Listing Organizations (Server-Side Pagination)

The organization list is fully server-side paginated. The API supports:

Parameter	Type	Default	Description
skip	int	0	Offset for pagination
limit	int	100	Page size (max 1000)
search	string	null	Search by name or description
region	string	null	Filter by exact region
active_only	bool	true	Legacy filter: show only active orgs
is_active	bool	null	Explicit active filter (overrides active_only when set)
include_stats	bool	true	Include host online/offline/stale stats

The response includes X-Total-Count header with the total matching count for pagination controls.

Regions endpoint (for populating filter dropdowns): Returns a sorted list of distinct non-null region values across accessible organizations.

Updating Organizations

Update:

Automation levels (consumed by patch engine, workflow engine, drift correction, and alert auto-remediation): - manual — all approvals required, no automatic actions - semi_auto — auto-approve security/critical patches, runbooks need approval - full_auto — all auto-approve, auto-deploy

Kill switch (settable via API and UI):

Deleting Organizations

Hard delete (requires organizations.hard_delete permission): Without the hard_delete query parameter, the organization is soft-deleted (deactivated). Hard delete permanently removes the organization and all associated data. Organizations with hosts cannot be hard-deleted – hosts must be removed first.

Location Management

Locations are physical or logical groupings within an organization.

Create location with subnet:

Setting subnet_cidr enables automatic agent location assignment based on the agent’s IP address.

Support Access Management

Enabling Support Access (Customer Admin)

This creates a time-bound view-only access grant for the support team.

Checking Support Access Status

Returns whether support access is currently active and when it expires.

Disabling Support Access

Normal disable:

Emergency disable (deactivates ALL support access immediately):

Reviewing Support Access Requests

When a support engineer requests access to your account:

List pending requests:

Approve/deny:

On approval, the support user receives time-bound view-only access (duration from the original request, default 24 hours).

Audit Trail

All support access changes are logged:

Major Incident Auto-Workflow

Organizations can bind an auto-launch workflow for major incidents. This setting is configurable both via API and through the organization edit modal in the UI (under “Major Incident Auto-Workflow”).

API:

UI: Open the Edit Organization modal and select from the “Major Incident Auto-Workflow” dropdown. Only active workflow definitions for the organization are shown. Select “None (disabled)” to clear the binding.

When configured, P1 incidents with 3+ affected hosts auto-launch the referenced workflow definition. Requires organizations.edit permission.

Organization Secret Management

Each organization has a secret used for agent registration. Both viewing and regenerating secrets require organizations.edit permission. The secret view button in the organization table is disabled for users without this permission.

View secret:

Regenerate secret (invalidates existing agent connections):

Warning: Regenerating the secret will require reconfiguring all agents registered with this organization.

Recording Governance

Recording Policy

Control what session data is captured per organization:

Recording Retention

Override the account-level retention period per organization:

Set to null to inherit from account default (which defaults to 90 days).

Legal Hold

Activate legal hold to prevent all recording deletion for an organization:

When active, neither user action nor the retention cleanup scheduler can delete recordings.

GDPR Data Management

Data Deletion (Art. 17)

Anonymize all PII and deactivate an account:

This is irreversible. Replaces emails/names with anonymized placeholders and clears password hashes.

Data Export (Art. 20)

Covers last 90 days, capped at 10,000 records per section. Excludes passwords, secrets, and encrypted credentials.

Cross-References

Topic	Document
Getting started	getting-started.md
User management	user-management.md
Host & agent management	host-agent-management.md
Roles & permissions	roles-permissions.md
Troubleshooting	troubleshooting-core.md
Multi-tenancy architecture	docs/architecture/multi-tenancy.md
Multi-tenancy functional specs	docs/functional/multi-tenancy.md