Tenant Management

This guide explains how to effectively manage tenants (clients/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.

graph TD A[MSP Tenants] –>|Manages| B[Tenant A] A –>|Manages| C[Tenant B – Corp B] C –>|parent of| D[Tenant C – Subsidiary Business 1] C –>|parent of| E[Tenant D – Subsidiary Business 2]

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 depending on their assigned permissions.

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 a parent tenant, typically representing separate business entities that share some infrastructure with the parent. Child tenants do not have direct access to the parent tenant’s Azure resources.

To enable Azure resource sharing, a separate domain can be associated with the child tenant. This allows integration with the parent tenant’s Azure environment, but it requires users in the child tenant to operate under that specific domain, rather than the domain used by the rest of the parent organization’s Azure users.

Creating Tenants

Creating Tenants Manually

  1. Navigate to Tenants in the left sidebar
  2. Click New on the Tenants list page
  3. Enter the tenant information:
    • Name
    • Description (optional)
    • Parent tenant (if applicable)
  4. Click Save

Importing Tenants from Integrations

If you have configured integrations, you can import tenants:

  1. Navigate to Show More > Integrations in the left sidebar
  2. Find and Edit your integration (RMM, PSA, or Azure)
  3. Navigate to the Clients tab
  4. Click Sync agents for selected clients
  5. Review the imported tenants
  6. Configure any additional settings
  7. Click Save

Tenant Hierarchy

ImmyBot allows you to create a hierarchical structure of tenants:

Creating Parent-Child Relationships

  1. Navigate to Tenants
  2. Select the tenant you would like to make a child tenant
  3. Go to the Edit tab
  4. Select the parent tenant from the dropdown
  5. Click Update

Inheritance in Tenant Hierarchy

Child tenants inherit certain settings from their parents:

  • Deployments (if configured for inheritance)
  • Maintenance Schedules (if configured for inheritance)

Child tenants do not inherit from their parents:

  • Tenant preferences
  • Integration Links

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

  1. Navigate to Tenants
  2. Select the tenant
  3. Click the Schedules tab
  4. 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

  1. Navigate to Tenants
  2. Select the tenant
  3. Click the Preferences tab
  4. Configure available preferences:
    • Default maintenance options
    • Remote Control settings
    • Computer settings
    • User settings
    • Onboarding Pages settings
  5. Click Update to save changes
Note

Tenant preferences can also be managed from Show More > Preferences under the Tenant tab, by selecting the tenant from the drop-down. See Preferences for the full list of tenant-level preferences.

Tenant-Specific Deployments

You can create deployments that apply only to specific tenants:

  1. Create a new deployment
  2. Under Targets, select Tenant
  3. Choose the specific tenant
  4. Configure the deployment as needed
  5. Save the deployment

For detailed instructions please see Deployments

Managing Tenant Users

Each tenant can have its own set of users:

Manually Adding Users to Tenants

  1. Navigate to Show More > People in the left sidebar
  2. Click New button
  3. Enter user information:
    • Tenant assignment
    • Name
    • Email
    • Azure Object Id – This is needed if you want to be able to enable this person to login to ImmyBot
  4. Click Create to add the user

Syncing Users from Azure AD

If you have configured Azure AD integration:

  1. Navigate to Show More > Azure in the left sidebar
  2. Select an Azure Client
  3. Click Sync users from X selected customer(s) at the top of the table

Tenant Migration

Sometimes you may need to move computers between tenants:

Moving Computers Between Tenants

  1. Navigate to Computers
  2. Select the computer(s) to move
  3. Click Batch Actions
  4. Under Change Tenant Select the target tenant
  5. Click Change
  6. Confirm the action was successful

Merging Tenants

ImmyBot has a built-in bulk merge action so you don’t have to move computers and delete the source tenant by hand:

  1. Navigate to Tenants
  2. Select the checkboxes next to the tenants you want to merge (you can select more than two at once)
  3. Click Batch Actions and choose Merge Tenants
  4. Select the target tenant that the others should be merged into
  5. Confirm the merge
Warning

Merging tenants is permanent. All of the selected source tenants and their associated data are merged into the target tenant and cannot be split back apart.

Deleting a tenant

To delete an tenant:

  1. Click on Tenants
  2. Select the checkbox next to the tenant you need to delete
  3. Click batch actions
  4. Click delete.

If you need to delete several instances, select several checkboxes in step 2.

The selected tenants will show a "Marked for deletion" message until deleted and a notification will show once the tenant has been deleted.

Best Practices

Follow these best practices for effective tenant management:

  1. Consistent Naming: Use a consistent naming convention for tenants
  2. Regular Audits: Periodically review tenant structure and settings
  3. Documentation: Maintain documentation of tenant configurations

Next Steps

Now that you understand how to manage tenants in ImmyBot, you might want to explore:

Was this article helpful?