NetStacksNetStacks

Organizations (Multi-Tenancy)

Enterprise

Host several teams or customers on one NetStacks Controller with organizations: create tenants, switch between them, move users, and know what is shared platform-wide.

Overview

An organization is a tenant on the Controller. Devices, sites, topologies, connection profiles and their secrets, templates, stacks, MOPs, agents, knowledge, plugins, users and roles all belong to one organization, and users only see the data of the organization they are working in. Secrets are encrypted with a separate key per organization.

Every Controller has a Default Organization. If you run NetStacks for a single team you never need another one; create more when one Controller serves several teams, business units or customers.

Platform Admins vs. Org Admins

Platform administratorOrganization administrator
Granted byThe Platform Administration permission (built-in platform-admin role)A role with All Permissions (for example admin) in that organization
Create, rename, delete organizationsYesNo
Switch into other organizationsYes (header organization switcher)No
Create users in any organization / move usersYesOnly in their own organization
Everything inside the organizationIn the organization they have switched toYes

The built-in admin user is a platform administrator. Keep the platform-admin role to a small number of trusted operators of the Controller itself.

Create an Organization

  1. Open Administration → Organizations (/admin/organizations). This item only appears for platform administrators.
  2. Click Add Organization.
  3. Enter a Name * (for example Acme Corp) and click Create.

Each organization card shows a Default badge for the Default Organization and a count of users and devices, with Edit and Delete buttons. Creating, renaming and deleting organizations is recorded in the audit log.

Set Up a New Organization

A new organization is empty: it has no users, roles, devices or profiles. To make it usable:

  1. Switch to the new organization with the header switcher (next section).
  2. Create its roles in Administration → Roles — at minimum an administrator role with All Permissions and an engineer role with Device Inventory plus the features they need. See Roles & Permissions.
  3. Create users in Administration → Users (as a platform admin you can pick the Organization in the Add User dialog), then assign them the new roles.
  4. Add the organization's connection profiles, sites and devices.

Switch Organization

Platform administrators see an organization switcher in the header, showing the organization currently in context. Click it and choose another organization under Switch organization. The console reloads its data for the selected organization; everything you do afterwards (creating devices, users, roles, and so on) happens in that organization. In the list, a check mark shows the active organization and home marks your own; while you are working in an organization other than your home one, the switcher shows an amber dot.

Header showing the Terminal link, the organization switcher with the current organization, and the connection status pill

The header Terminal link opens the web terminal in the same organization. Switching is recorded in the audit log as auth.org_switched. Signing in again returns you to your home organization.

Move Users Between Organizations

As a platform administrator, open the user in Edit User, change Organization and click Save Changes. Afterwards, assign the user roles from their new organization — roles are per organization. You can't move your own account.

Rename or Delete an Organization

  • Rename: click Edit, change Name in Organization Details, and click Save.
  • Delete: click Delete. The button is disabled for the Default Organization and for any organization that still has users or devices — move or delete those first.

What Is Per-Organization vs. Platform-Wide

Per organizationPlatform-wide (shared by all organizations)
Users, roles, devices, sites, topologies, connection profiles and secrets, SSH and X.509 certificate authorities, templates, stacks, MOPs, scripts, scheduled tasks, agents, knowledge base, enabled pluginsEverything under Settings (authentication, TLS, terminal, AI, integrations and so on), the license and its seats, the dashboard layout, Platform Health and backups
Settings are global

Because Settings are platform-wide, give System Settings only to people who administer the whole Controller, not to tenant administrators.