III — How-To Guides
Create your first tenant, location, and group
Build the three-level organisational hierarchy every device lives in.
Create your first tenant, location, and group
NetLock RMM organises every device into a three-level hierarchy: tenant → location → group. A device cannot be approved into the console without one of each. This guide walks through creating the hierarchy from scratch on the Tenants page. Once finished you will have an empty tree ready to receive an agent.

Before you start
- You are signed in to the Console as a user with permission to manage tenants.
- Required permissions:
tenants_enabled,tenants_add,tenants_manage,tenants_locations_add,tenants_locations_manageandtenants_groups_add.
Steps
Create the tenant
- In the navigation, open
Tenants. - Click
Addabove the tenant table. While no tenant exists, the page showsCreate Tenantinstead. - Enter the tenant name and, if you like, a description, the company and contact persons. For an in-house IT team the tenant usually maps to the company; for an MSP it maps to one customer.
- Click
Confirm. The new tenant appears in the list. It does not contain any locations, groups or devices yet.
Create the location
- Open the new tenant with the row action
Manage(or double-click the row). TheManage tenantpage opens. - Click
Add locationabove theLocationstable. - Enter a location name. Locations usually reflect a physical site, for example
Berlin HQ,Remote WorkersorDatacenter A. - Click
Confirm.
Create the group
- In the
Locationstable, open the new location with the row actionManage. TheManage locationpage opens. - Click
Addabove theGroupstable. - Enter a group name aligned to how the devices inside it will be configured, for example
Workstations,Laptops,ServersorPOS Terminals. As a rule of thumb, create one group per intended policy. - Click
Confirm.
Tip: If a single policy applies to every device at a location regardless of role, one group per location is plenty. Only split groups when different policies will apply. It is easier to add groups later than to consolidate them.
Verify it worked
Tenantslists the new tenant.Manage tenantfor that tenant lists the new location underLocations.Manage locationfor the new location lists the new group underGroups.
Troubleshooting
- An
Addbutton or theManageaction is missing. Your user account is missing the matching permission from the list above. Ask an administrator to grant it. - A name is rejected with
Name already taken.Tenant names are unique across the installation, location names within their tenant, and group names within their location. Pick a different name or a different parent.
Related
- Chapter 4 — Tenants, Locations & Groups — full reference, including tenant settings, per-tenant exports, and hierarchy reorganisation.
- Guide H.1 — Deploy your first agent — installs an agent into the new hierarchy.
- Guide H.4 — Build and apply a policy — routes a policy to the new group.