Tenant Management
This guide explains how to effectively manage tenants (customers) in ImmyBot, including creation, organization, and configuration.
Understanding Tenants
In ImmyBot, tenants represent the organizations you manage. Each tenant:
- Has its own set of computers and users
- Can have tenant-specific deployments
- May have different settings and configurations
Tenants can be organized hierarchically, with parent-child relationships that allow for inheritance of certain settings and deployments.
Tenant Types
ImmyBot supports several tenant types:
MSP Tenant
By default that first tenant in the ImmyBot instance is your MSP tenant. You can create additional MSP tenants, however, and Users (not People) can view and manage all Tenants within your instance.
Client Tenants
Client tenants represent your customers. They can be created:
- Manually in ImmyBot
- Automatically through RMM integration
- Automatically through PSA integration
- Imported from Azure AD
Child-Tenants
Child-tenants are sub tenants of tenants. They can represent:
- Branch offices
- Departments
- Divisions
- Geographic locations
Creating Tenants
Creating Tenants Manually
- Navigate to Tenants in the left sidebar
- Click New on the Tenants list page
- Enter the tenant information:
- Name
- Description (optional)
- Parent tenant (if applicable)
- Click Save
Importing Tenants from Integrations
If you have configured integrations, you can import tenants:
- Navigate to Show More > Integrations in the left sidebar
- Find and Edit your integration (RMM, PSA, or Azure)
- Navigate to the Clients tab
- Click Sync agents for selected clients
- Review the imported tenants
- Configure any additional settings
- Click Save
Tenant Hierarchy
ImmyBot allows you to create a hierarchical structure of tenants:
Creating Parent-Child Relationships
- Navigate to Tenants
- Select the tenant you would like to make a child tenant
- Go to the Edit tab
- Select the parent tenant from the dropdown
- Click Update
Inheritance in Tenant Hierarchy
Child tenants inherit certain settings from their parents:
- Deployments (if configured for inheritance)
- Maintenance windows
- Integration mappings
You can override inherited settings at the child tenant level when needed.
Tenant Configuration
Each tenant can have its own configuration options:
Configuring Tenant Schedules
- Navigate to Tenants
- Select the tenant
- Click the Schedules tab
- Configure the Schedule:
- Click New to create a new schedule
- Set schedule name, frequency, and time window
- Select targets (computers or groups)
- Click Create to save the schedule
Configuring Tenant Preferences
- Navigate to Tenants
- Select the tenant
- Click the Preferences tab
- Configure available preferences:
- Default maintenance options
- Agent settings
- Deployment defaults
- Click Update to save changes
Tenant-Specific Deployments
You can create deployments that apply only to specific tenants:
- Create a new deployment
- Under Targets, select Tenant
- Choose the specific tenant
- Configure the deployment as needed
- Save the deployment
For detailed instructions please see Deployments
Managing Tenant Users
Each tenant can have its own set of users:
Adding Users to Tenants
- Navigate to Show More > People in the left sidebar
- Click New button
- Enter user information:
- Name
- Role
- Tenant assignment
- Click Create to add the user
Importing Users from Azure AD
If you have configured Azure AD integration:
- Navigate to Show More > Azure in the left sidebar
- Select an Azure Client
- Navigate to the Users tab
- Click Sync users From the parent tenant
- Review the imported users
- Click Save to apply changes
Tenant Migration
Sometimes you may need to move computers between tenants:
Moving Computers Between Tenants
- Navigate to Computers
- Select the computer(s) to move
- Click Batch Actions
- Under Change Tenant Select the target tenant
- Click Change
- Confirm the action was successful
Merging Tenants
To merge two tenants:
- Identify the source and destination tenants
- Move all computers from the source to the destination
- Update any tenant-specific deployments
- Once empty, you can delete the source tenant
Best Practices
Follow these best practices for effective tenant management:
- Consistent Naming: Use a consistent naming convention for tenants
- Hierarchical Organization: Create a logical hierarchy that reflects your business relationships
- Regular Audits: Periodically review tenant structure and settings
- Documentation: Maintain documentation of tenant configurations
- Limit Direct Access: Restrict direct access to the MSP tenants
Next Steps
Now that you understand how to manage tenants in ImmyBot, you might want to explore:
- User Roles and Security - Learn about user permissions and security
- Integration Overview - Connect ImmyBot to your existing tools
- Maintenance and Updates - Configure maintenance for your tenants