Multi-Tenancy

Multi-tenancy allows a single ProxCenter instance to serve multiple isolated organizations or teams. Each tenant has its own set of connections, users, and resources -- completely separated from other tenants. This is essential for MSPs managing multiple clients and for enterprises with distinct teams sharing infrastructure.

Overview

Without multi-tenancy, all users in a ProxCenter instance see the same connections and resources. With multi-tenancy enabled, resources are partitioned by tenant. A user assigned to "Client A" only sees Client A's Proxmox connections, VMs, backups, and events -- never Client B's.

Enabling Multi-Tenancy

1. Navigate to Settings > Tenants (requires super_admin role)
2. Toggle Enable Multi-Tenancy
3. The default tenant is created automatically, containing all existing connections and users

warning

Enabling multi-tenancy is a significant architectural change. Plan your tenant structure before enabling it. All existing resources are assigned to a default tenant, which you can then reorganize.

Managing Tenants

Creating a Tenant

1. Go to Settings > Tenants
2. Click Add Tenant
3. Provide a name and optional description
4. The tenant is created with no connections or users -- assign them in the next steps

Assigning Connections

Each Proxmox connection belongs to exactly one tenant. When you add a new connection, you select which tenant it belongs to. Existing connections can be reassigned from the tenant management page.

A tenant's users can only see and interact with connections assigned to their tenant.

Assigning Users

Users are assigned to one or more tenants. A user's role and permissions are scoped to their assigned tenant(s).

User Type	Tenant Access
Super Admin	Can access all tenants and manage tenant configuration
Tenant Admin	Full access within their assigned tenant(s)
Tenant User	Access based on their RBAC permissions within the tenant

Data Isolation

Multi-tenancy enforces strict data isolation at the application level:

• Connections -- Each connection belongs to one tenant. API calls only return data from the current tenant's connections.
• VMs and Containers -- Only visible to users of the tenant that owns the connection.
• Backups -- Backup data and schedules are scoped to the tenant's connections.
• Events and Tasks -- Filtered to show only events from the tenant's connections.
• Reports and Alerts -- Generated per tenant, never cross-tenant.
• Audit Logs -- Tenant-scoped, though super admins can view logs across all tenants.

Switching Tenants

Users assigned to multiple tenants can switch between them using the tenant selector in the top navigation bar. Switching tenants immediately changes the visible connections, resources, and data to those belonging to the selected tenant.

Use Cases

MSP (Managed Service Provider)

Create one tenant per client. Each client's Proxmox infrastructure is isolated. Your support team can have super admin access to manage all tenants, while client users only see their own environment.

Enterprise Teams

Create tenants per department or project. The infrastructure team manages all tenants, while development and operations teams are scoped to their own resources.

tip

Combine multi-tenancy with white-label branding to give each tenant a fully customized experience -- their own branding, their own isolated environment.

Enterprise Feature

Multi-Tenancy is available in the Enterprise edition and requires the MULTI_TENANCY feature flag in your license.

Permissions

Permission	Description
super_admin	Required to enable multi-tenancy and manage all tenants
tenant.manage	Create, edit, and delete tenants (super admin only)
tenant.view	View tenant configuration and user assignments