If you are a managed service provider (MSP), each of your clients has its own tenant in mi.team. A tenant keeps one client’s users, devices, teams and settings separate from every other client. The MSP Configuration page is where you create those tenants and get the correct agent installer for each one.
This article covers what the page shows, how to add a new client, how to download the agent for a specific client, and what you cannot yet do from the page.
Where to find MSP Configuration
Log in to mi.team at go.mi.team, open Settings in the left-hand menu and select MSP Configuration. The page is only shown to MSP accounts.

What the Tenants table shows
The table lists every tenant you manage. Your own organisation appears in the list too, so you can monitor your own staff in the same way as your clients.
Each row has three parts:
- Name: the client’s company name, as entered when the tenant was created.
- Enrolment Code: a unique code for that client. When the agent is installed, this code tells mi.team which client the device belongs to.
- Download Agent: opens the agent download page for that client, with the enrolment code already built into every installer and script.
The two buttons at the top right of the table refresh the list and add a new tenant.
Keep enrolment codes private
The enrolment code is what links a device to a client’s tenant. Treat it in the same way as any other deployment credential: share it only with the people who install the agent, and do not paste it into tickets, emails or documents that the wider client team can see. If you share screenshots of the page, blur the codes first.
How to add a new client tenant
- On the MSP Configuration page, click the green + button at the top right of the Tenants table.
- In the Add Tenant window, enter the client’s Company Name.
- Enter the Number of users you expect to monitor for that client.
- Click Add Tenant.
The new client appears in the list with its own enrolment code. If it does not appear straight away, click the refresh button.

Check the company name before you click Add Tenant. Tenants cannot currently be renamed or deleted from the MSP Configuration page, so a typing error will stay in your list. If you need a tenant changed or removed, contact mi.team support.
The company name is also used as the suggested prefix for the client’s installer file. Names containing characters such as an ampersand (&) work in mi.team, but the ampersand can cause problems in command lines and scripts if the file name is not wrapped in quotation marks. If you rename the installer, use a simple prefix made of letters and numbers only, such as SmithAndCo_.
How to download the agent for a specific client
Click Download Agent on the client’s row. This takes you to the Agent Download page for that client, and the tenant switcher at the bottom of the left-hand menu changes to show the client’s name.
Choose a Deployment method from the drop-down list. There are seven options for Windows:
- Direct: Direct Installer (.exe) and PowerShell Script.
- Enterprise: Active Directory (GPO) and Microsoft Intune.
- RMM platforms: SuperOps, NinjaRMM and General RMM (for any RMM tool that can run PowerShell remotely).

Each method shows step-by-step instructions and a script or command that already contains the client’s enrolment code, so you can copy it and use it as it is. The agent requires Windows 8.1 or later.
For a full walkthrough of each method, see How to Install mi.team Silently.

Installer naming rules
The direct installer file name contains the enrolment code between two # characters, for example:
mi.team.installer#xxx-xxx-xxxxx#.exe
- Do not change anything between the
#characters. That text is the enrolment code, and the installer uses it to join the correct tenant. - You may add a prefix or suffix outside the
#characters. The recommended format is the client’s name followed by an underscore, for exampleClientName_mi.team.installer#xxx-xxx-xxxxx#.exe.
Adding the client’s name is good practice when you manage several clients, as it makes it much harder to deploy one client’s installer to another client’s machines.
Before you deploy to a client
Installing the agent is only one step in a rollout. Your client remains responsible for choosing a lawful basis, telling staff about the monitoring and completing a DPIA before devices are enrolled. Our guide How to Deploy mi.team: The Complete Rollout Process sets out the steps in the right order, and it is worth sharing with each new client before you deploy.
With the client selected in the tenant switcher, you can also set up their teams and Startup Agreement wording from the other Settings pages. See How to Create Teams, Add Members and Add Managers.
What you cannot do yet
To be clear about the current limits of the page:
- Tenants can be created, but not renamed or deleted, from MSP Configuration.
- The agent is available for Windows only.
If either of these affects how you would like to work, please let us know. Feedback from MSPs has a direct influence on what we build next.
Frequently asked questions
Does each client need a separate installer?
Yes. Each client has its own enrolment code, and the installer or script must contain the code for the client whose devices you are deploying to. Always start from that client’s Download Agent button.
Can I use the same script for several clients?
No. The scripts are identical apart from the enrolment code, but that code decides which tenant the device joins. Use the script from each client’s own Agent Download page.
What happens if I deploy the wrong client’s installer?
The device will enrol into the wrong client’s tenant. This is why we recommend naming each installer with the client’s name and keeping enrolment codes private.
Why does my own company appear in the tenant list?
Your own organisation is a tenant too, so you can use mi.team for your own team in the same way as your clients do.