Multi-tenancy Overview

 

Alpha Testing: This feature is currently in testing and has not yet been widely released. Keep an eye out on the in-product release notes for public availability.

Multi-tenancy enables you to logically separate the devices in your organization into multiple tenants. This allows you to optimize each tenant environment for the specific needs of different teams or customers. Whether you're managing devices for internal departments or external clients, this feature provides better structure, clarity, and operational efficiency.

When multi-tenancy is enabled, your Connect account becomes a parent organization under which you can create multiple child tenants. Each tenant functions independently with its own settings and assets.

Creating and Managing Tenants

  1. In the bottom left of the PDQ Connect console, click the Settings button.
  2. Click on the Tenants section.
  3. Click Create Tenant to add a new tenant under your parent organization.
  4. Give the Tenant a name (may be edited later) and optionally set an icon and note/description.
  5. Click Create. Upon creation, you'll be directed through the initial setup of the new tenant.

1.png

You may also create a tenant using the tenant/org switcher found in the upper left of the console.

Also on the Tenants section of the Settings page, you have the ability to Edit and Delete existing tenants using the kebab menu found to the right of the tenant name.

 

Warning: Deleting a tenant will remove access to a tenant's data, including devices, groups, packages, custom fields, variables, deployment history, scan data, and automations. The Connect agent will be automatically uninstalled from devices within a deleted tenant.

Switching Between Tenants

To switch tenants within your current organization:

  • Click on the tenant/organization name found in the upper left of the console to open the Tenant Switcher.
  • Select the tenant you want to access.

You can have multiple tenants open in separate browser tabs simultaneously.

If you have access to multiple Connect organizations, you can also switch between them, though only one organization can be active per browser session.

Managing Devices Within Tenants

To add devices to a tenant:

  1. Navigate to the tenant where you want the devices managed.
  2. Download the agent from that specific tenant.
  3. Install the agent on the target devices.
 

Note: Devices are bound to the tenant from which the agent was downloaded. While there is currently no support for seamlessly migrating devices between tenants, this capability is on the roadmap. For now, you may uninstall the agent and reinstall the agent from another tenant to move a device.

Permissions and Access

All members of your organization have access to all tenants, and retain the same role across each tenant. At this time, it is not possible to restrict access to specific tenants or assign unique roles per tenant. These features are also on the roadmap.

There is however a configurable role for managing multi-tenancy where access to create, edit, and delete tenants within an organization may be restricted. This may be found in Settings > Roles > Manage multi-tenancy.

Data Separation

Each tenant operates as a fully isolated environment. This includes:

  • Devices
  • Groups
  • Packages
  • Automations
  • Reports
  • API access

There is currently no data sharing or global device management across tenants or from the parent account. Global management and object sharing from parent to child tenants is also planned for a future release.

FAQ

Can I move a device from one tenant to another?

No, not without uninstalling the agent and then reinstalling an agent from another tenant. A more seamless experience to move devices between tenants is on our roadmap.

Can I restrict user access to specific tenants?

No. At this time, all users in your organization have the same role across all tenants and access to each one. Role-based access control per tenant is planned for a future update.

Can I manage devices globally from the parent organization?

Not yet. Right now, device and object management is scoped only to the individual tenant level. We plan to support global management features in the future.

How does billing/licensing work with multi-tenancy?

Billing and licensing are still managed at the parent organization level. For example, if your organization has 500 devices licensed, you can distribute those devices across tenants in any way you choose. Creating additional tenants does not affect your licensed device count or increase your minimum.

Still have a question or want to share what you have learned? Visit our Community Discord to get help and collaborate with others.