Organizations
Manage organizations, quotas, and platform-wide configurations. Requires super_admin role.
Overview
An organization is the product boundary that owns devices, users, applications, and network configuration. APIs, request headers, and storage continue to use the technical identifier tenant. PostgreSQL Row-Level Security (RLS) isolates organization data so a user in organization A cannot read organization B's data.
Organization List
Navigate to Organizations to see all organizations in the platform.
Columns: Organization, Plan, Industry, Devices, Users, Owner, and Status.
Creating an Organization
- Click + New Organization.
- Enter the organization name and select its owner.
- Select an initial plan. A new subscription binds to that plan's current published, immutable entitlement version.
- Optionally set the icon URL, industry, and other profile fields.
- Click Create.
The owner is bound as an administrator when the organization is created. Organization administrators add other users through Users → Invite User.
Editing an Organization
Click the ⋮ menu → Edit. You can update the name and icon URL.
Organization Detail
Click an organization row to open its detail page. The page provides Overview, Users, Plugins, Quotas & Limits, and Audit tabs.
Plugins Tab
Shows all built-in plugins and their configuration status for this organization. Click a plugin to open its configuration editor.
Plugin config can be set at two levels:
- Organization default — applies to all device groups without an override
- Group override — per-group config set from Devices → Groups → [Group] → Plugins
Plugin Configuration (Organization-wide)
Navigate to Settings → Plugin Config within an organization to configure plugin defaults.
Available plugins:
Terminal Plugin
| Setting | Description |
|---|---|
| Shell Path | Shell executable (e.g. /bin/bash) |
| Default Columns | Terminal width in characters |
| Default Rows | Terminal height in rows |
| Persistence | Keep session after browser disconnect |
| Enable Color Output | ANSI escape-sequence color support |
Telemetry Plugin
| Setting | Description |
|---|---|
| Collection Interval (s) | How often metrics are collected |
| Enabled Metrics | Which metric categories to collect |
Logs Plugin
| Setting | Description |
|---|---|
| Log Sources | One source per line (e.g. file:/var/log/syslog) |
| Max Lines/Second | Rate limit for log ingestion |
Container Plugin
| Setting | Description |
|---|---|
| Registries | Private Docker registry URLs |
| Command Timeout | Seconds to wait for device response (default: 30) |
| Max Log Lines | Maximum log lines per request (default: 1000) |
WireGuard Plugin
Configured via the Network section. See Network.
Organization Config (Custom Key-Value)
Each organization has an extensible config map. Platform operators can set key-value pairs that plugins and integrations can read at runtime.
Contact your platform administrator to add or update organization configuration values.
Entitlements and Quotas
An organization's device, seat, telemetry-ingest, log-ingest, concurrent-terminal, API-rate, and retention limits come from its bound immutable plan version. Platform administrators can add only finite capacity adjustments with an explicit start, end, source, and reason; they cannot turn a commercial limit into an unbounded value.
When a hard limit is reached, the server rejects the operation before it creates resource cost and returns a structured quota error. The web interface preserves read-only access and directs organization administrators to change plan or contact the platform team. Pending invitations reserve seats and release them when expired or revoked.