Overview
In IT Agent, Tenants, Organizations, and Groups are three different layers used to define ownership, access, and targeting. Understanding how they relate to each other helps you structure your environment correctly and apply actions and policies with confidence.
At a high level, the hierarchy looks like this:
Tenant
→ contains one or more Organizations
→ each Organization contains Groups
Tenant
A Tenant is the top-level container for your IT Agent account.
What a Tenant represents
Your IT Agent account
Your sign-in domain / URL
Your region
Subscription and provisioning state
Tenant-level access and administration
If you sign in using a tenant-specific domain (for example, yourcompany.us1.itagent.app), that domain belongs to a Tenant.
When you’ll interact with Tenants
Managing billing and subscription details
Configuring tenant-wide settings
Switching between different tenants (if you have access to more than one)
Most users don’t interact with Tenants daily — they exist primarily to define account boundaries and ownership.
Organization
An Organization is where your operational data and daily work live. An Organization lives inside a Tenant and contains your operational objects.
What an Organization contains
Computers / hosts
Jobs, remediations, rules, and impacts
Reboot and maintenance operations
Organization-specific settings and configurations
How Organizations are typically used
Managed Service Providers (MSPs): One Organization per customer
Internal IT teams: One Organization per environment, department, or business unit
Organizations allow you to clearly separate systems, users, and actions while still managing everything under a single Tenant.
Group
A Group is a way to organize and target subsets of users or computers within a single Organization.
What Groups are used for
Structuring devices and users into logical collections
Targeting actions such as policies, jobs, or remediations
Simplifying management at scale
Common Group examples
Servers
Workstations
Engineering
Executives
Patch Ring A / Patch Ring B
Important details about Groups
A Group always belongs to one Organization
Groups can contain:
Computers
Users
Associated policies
Group membership may be:
Manual (explicitly assigned)
Rule-based (automatically maintained)
Putting it all together
Visual Hierarchy
Tenant
├ Organization A
│ ├ Group: Servers
│ ├ Group: Workstations
└ Organization B
├ Group: Engineering
└ Group: Patch Ring A
Example: MSP setup
Tenant: Acme MSP (account, billing, login)
Organizations: Client A, Client B, Client C
Groups (inside Client A):
Servers
Accounting
Patch Ring 0
Example: Internal IT setup
Tenant: Acme Corp
Organizations: HQ, Warehouse, Retail
Groups (inside HQ):
Executives
Engineering Laptops
Conference Room PCs
Frequently Asked Questions
Can I have multiple Organizations in one Tenant?
Yes. This is a common setup, especially for MSPs or environments with multiple business units.
Can a Group span multiple Organizations?
No. Groups are scoped to a single Organization. If you need similar grouping across multiple Organizations, you’ll create a Group in each one.
Where are policies applied?
Policies are applied within an Organization, most often by targeting Groups.
Practical Tips
Use Organizations to model customers or environments.
Use Groups to segment devices for targeting and rules.
Think of Tenant as your overall account boundary — it’s not used for daily operations, but it matters for login and billing.
Summary
Tenant = account, billing, login domain, and global ownership
Organization = where your devices, jobs, and operational work live
Group = how you organize and target subsets of users and devices
Understanding these layers helps ensure your IT Agent environment stays organized, scalable, and easy to manage.