When to Create Multiple Organizations
Most customers only need a single Organization, but there are situations where creating multiple Organizations makes management clearer and more flexible. This guide explains when it makes sense to separate devices into more than one Organization.
Different Feature Requirements
Organizations apply subscription features to all devices within them.
If some devices need advanced security features, such as NGAV or backups, while others only need basic monitoring and patching, separating those devices into different Organizations allows each group to use the appropriate features.
This avoids enabling features where they are not needed and keeps billing aligned with actual requirements.
Separate Administrative Responsibility
Multiple Organizations are useful when different people or teams are responsible for different sets of devices.
By creating separate Organizations, you can control which administrators and users have access to each group of devices.
This is common when managing:
- Different departments within a company
- Multiple businesses or clients
- Internal systems and external or partner-managed systems
Environment Separation
Some customers prefer to keep production systems separate from test or staging systems.
Using separate Organizations for each environment reduces confusion and keeps dashboards, alerts, and reports clearly scoped.
When One Organization Is Enough
If all devices share the same feature needs, administrators, and billing, a single Organization is usually the simplest choice.
You can still organize devices by location and type within one Organization without creating additional complexity.
Keep It Intentional
Creating multiple Organizations should be a deliberate decision based on management or security needs.
When used appropriately, multiple Organizations provide clearer access control and cleaner separation while keeping setup and daily use straightforward.