When to Create Another Organization
This document explains when it makes sense to create more than one Organization in Simplified Solutions. While many customers only need a single Organization, there are cases where separating devices into multiple Organizations provides clearer management, access control, or feature separation.
Organizations are fully isolated from one another. Devices, billing, access permissions, and subscription settings do not overlap between Organizations.
Different Security or Feature Requirements
One common reason to create multiple Organizations is when different groups of devices require different security features.
For example, you may want next-generation antivirus (NGAV) or backups enabled for servers or sensitive systems, while other devices only require basic monitoring and patching. Because subscription features are applied at the Organization level, separating these devices into different Organizations allows each group to use the appropriate service level.
This approach keeps feature usage clear and avoids applying advanced protections to devices that do not require them.
Separate Administrative Responsibility
Another reason to create additional Organizations is to separate administrative responsibility.
If different teams or individuals are responsible for different sets of devices, placing those devices in separate Organizations allows you to assign administrators only to the Organizations they manage.
This is useful when:
- Different departments manage their own systems.
- Multiple businesses are managed under the same account.
- External partners or IT staff should only see a specific subset of devices.
Clear Separation Between Environments
Organizations can also be used to separate environments that should not be mixed, such as production systems and test or staging systems.
Keeping these environments in separate Organizations helps avoid confusion and ensures that dashboards, alerts, and billing reflect the correct context.
Billing and Reporting Considerations
Because billing and invoices are generated per Organization, creating separate Organizations can simplify accounting when costs need to be tracked independently.
This can be helpful when managing multiple clients, cost centers, or business entities that require separate records.
When a Single Organization Is Enough
If all devices share the same feature requirements, administrators, and billing needs, a single Organization is usually sufficient.
Devices can still be grouped by location and type within an Organization, providing flexibility without added complexity.
Creating additional Organizations should be a deliberate choice based on management, security, or operational needs. When used appropriately, multiple Organizations provide clarity and control while keeping each environment easy to manage.