Tenants, Locations & Groups
The tenant → location → group hierarchy: create, configure, organise, and export.
Tenants, Locations & Groups
NetLock RMM organises every managed device into a three-level hierarchy: tenant, location, group. This chapter describes how to create and manage that hierarchy. Policies, automations and permissions are scoped along it, so plan it early in the deployment.

4.1 The hierarchy, in brief
In short (see Core Concepts):
- A tenant is the top-level organisational container. For an in-house IT team this usually maps to the company; for an MSP it maps to a customer.
- A location is a subdivision of a tenant, typically a physical site or office.
- A group is a subdivision of a location. It typically reflects how devices should be configured (
Workstations,Servers,Laptops) rather than where they physically sit.
Every device belongs to exactly one group. Policies are assigned through automations, and an automation condition can name a tenant, a location or a group: a rule on a tenant matches every device in every location and every group of that tenant (see Chapter 5).
Tip: Keep groups focused on configuration intent. If a single policy applies to every device regardless of site, one group per location is plenty. If policies differ by device type, create device-type groups inside each location.
4.2 Managing tenants
The Tenants page at /tenants is the entry point. It lists every tenant you have permission to see, along with summary information (device counts, last activity).
Creating a tenant
- Open
Tenantsfrom the navigation. - Click the add button on the
Tenantspage. - Fill in the tenant name and any additional details required by your deployment.
- Save.
The newly created tenant starts empty, without locations, groups or devices.
Editing a tenant
Open a tenant with the row action Manage to reach its Manage tenant page. From there you can rename it, change its contact information, or adjust tenant-wide settings (covered in 4.3). Editing a tenant does not affect its devices or their assignments; only the tenant metadata changes.
Deleting a tenant
Before you delete a tenant, confirm:
- The tenant has no active devices you still care about.
- No reports or scheduled deliveries reference the tenant.
- You have archived any customer data you may need later: device inventory from the Devices page, events from Events & Audit, and any reports from Reports. (The tenant-list export at 4.5 only captures tenant metadata, not the data under the tenant.)
The delete dialog lists the automation rules that name the tenant or one of its locations, groups or devices: how many will be deleted and how many switched off, with the names of those you can see. They change when the server finally removes the tenant, after its agents are uninstalled (see §5.7).
4.3 Tenant settings
Tenant-level configuration lives on the Manage tenant page at /tenant_settings. The page requires a tenant to be selected in the header context; if none is selected, choose one first.
The page has five sections:
- General Information: editable fields for the tenant's
name,company, anddescription. This is the metadata the rest of the Console refers back to (the name shown in reports, in exports, in the navigation selector). - Contact Persons: five contact-person slots with editable details. These are used as recipients and fallback contacts for tenant-scoped notifications and reports.
- Report contacts: mail addresses, separated by commas, that receive the reports made for this tenant when a report schedule sends to the report contacts of its tenants (Chapter 11.10). Each address is checked when the settings are saved.
- Locations: a searchable table listing every location under this tenant, with a
Manageaction on each row that opens the location's detail view (see 4.4). You can add a new location directly from this table. - Custom Fields: the values this tenant holds for inheritable custom fields, with the effective value per field. Devices of the tenant without a value of their own inherit them. See Chapter 8.4 — Scope and inheritance.
The Manage tenant page has no settings for branding, notifications, integrations or agent configuration. These are configured as follows:
- Branding and themes: deployment-wide in A.6 Whitelabeling & themes.
- Notification channels and recipients: deployment-wide in A.8 Notifications deep dive.
- Agent configuration: per tenant and location on Agent Installers, not a global tenant setting.
Per-tenant isolation
Tenant metadata and contact persons are isolated per tenant: editing them in one tenant has no effect on another. For system-wide defaults that populate new tenant records, see A.12 Content defaults.
4.4 Locations and groups
With a tenant in place, add locations and groups beneath it.

Adding a location
- Open the tenant on its
Manage tenantpage. - Click
Add locationabove theLocationstable. - Enter a location name that reflects the site, for example
Berlin HQ,Remote Workers,Datacenter A. - Save.
Locations are freeform; use as many as the geography of your deployment warrants. An MSP managing a customer with three offices typically creates three locations.
Editing and deleting a location
Locations are edited and deleted with the usual edit and delete actions. Deleting a location removes its groups; any devices in those groups lose their group assignment and must be reassigned before configuration flows to them again.
Adding a group
- Open the parent location with the row action
Managein theLocationstable. TheManage locationpage opens. - Click
Addabove theGroupstable. - Enter a group name aligned to the devices it will contain.
- Save.
Groups accept devices immediately. You can now:
- Approve new devices into this group (see First-Run Walkthrough step 6).
- Move existing devices into the group from the
Devicespage. - Route policies to the group by creating an Automation with a
Groupcondition that picks this group.
Moving devices between groups
Change the group of the device on the Devices page (see Chapter 3). The agent picks up the new assignment on its next poll and any policies attached to the new group take effect.
Note: Moving a device between groups does not trigger a device reboot or re-authorisation. The agent starts receiving a different policy set.
4.5 Exporting the tenant list
The Export Data dialog, opened from the Tenants page, exports the list of tenants you are permitted to see. It is not a full tenant archive.
What is exported. One row per tenant, with these fields: id, tenant_name, guid, date (creation date), author (who created the record), description, and company. Devices, policies, events, audit entries, custom-field values and deployment histories are not part of this export; they are described in their own chapters and exported from there if needed.
Scope. Every tenant that matches your tenants permission list. If you are scoped to specific tenants, the export contains only those. The dialog always exports the full visible list; it has no option for a single tenant.
Formats. The dialog asks you to pick one output format:
JSONXLSX(spreadsheet)XMLHTML
Permissions. Any user with access to the Tenants page can run the export. The export needs no separate permission flag.
Steps:
- Open
Tenants. - Click the export action to open the Export Data dialog.
- Pick the output format and confirm. The file downloads to your browser immediately.
If you need to archive more than the tenant list, for example a customer's full device inventory or audit trail before offboarding, run the relevant exports from Reports or Events & Audit, or use the export functions of the pages that hold that data.
Common tasks
Set up a new MSP customer from scratch
- Create a tenant for the customer on the
Tenantspage. - Add one location per physical site the customer operates.
- Add groups inside each location that reflect the device roles you will manage (
Workstations,Servers, etc.). - Open the
Manage tenantpage and fill in contact information and any per-tenant defaults. - Generate an agent installer for the customer's tenant and location (see First-Run Walkthrough).
- Deploy the agent on the first device and approve it in
Unauthorized Devices. - Build and apply a baseline policy to the group (see Guide H.4).
Reorganise an existing tenant
- Plan the new structure on paper first: list the new locations and groups and the automations that will route policies to each group.
- Create the new locations and groups on the
Manage tenantandManage locationpages. - Create or update Automations to match the new group names before moving devices, so devices do not sit unassigned after the move.
- Move devices in small batches, verifying policy assignment in the device detail view and policy deployment in
Eventsafter each batch. - Delete the old locations and groups once empty.
Archive and remove a departing customer
- Export device inventory, event history, and any scheduled reports from their respective pages; the tenant-list export only covers tenant metadata.
- Optionally export the tenant list via the Export Data dialog on the
Tenantspage so you keep a record of the tenant row itself. - Uninstall agents on the customer's devices (outside the scope of this chapter).
- Delete the tenant on the
Tenantspage.
Permissions
Tenant, location, and group operations are gated by a tenant-management permission group. In addition, tenant-scoped user accounts (see Chapter 14 — Users & Roles) only see the tenants they are explicitly permitted to access, which also restricts every other feature area to those tenants.
Related chapters
- Core Concepts — the tenant → location → group model in context.
- Chapter 3 — Devices — how devices are created, moved, and labelled.
- Chapter 6 — Policies — attaching policies to tenants, locations, and groups.
- Chapter 14 — Users & Roles — scoping user access to specific tenants.
- A.12 Content defaults — system-wide defaults that apply to new tenants.