Set up your location hierarchy early — nearly every record in FacilityLane references a location, and a clean structure makes work orders, assets, and inventory easy to organize.

​
Plan the hierarchy first

Sketch your structure before creating records. Start from sites (top level) and work down: site → building → floor → area or room. Go only as deep as your team will actually use — a hierarchy nobody fills in accurately is worse than a shallow one everyone uses.

​
Create a location

1

Open the location create form

Go to Locations and select Add Location.
2

Name it and place it in the hierarchy

Enter the location name and choose its parent location. Leave the parent empty for a top-level site.
Location create form with name field and parent location picker

Creating a location and choosing its parent in the hierarchy

3

Assign the site and area code

Confirm the site assignment and give the location an area code — a short identifier used on labels and in lists.
4

Save

Select Save. The location immediately appears in location pickers across work orders, assets, and inventory.

​
Edit or move a location

Open the location, select Edit, and update its name, area code, or parent. Changing the parent moves the location — and everything beneath it — to the new branch of the hierarchy.
Moving a location moves its child locations with it. Check the subtree before reparenting a building or floor.
Location edit form showing the parent location being changed

Editing a location's parent to move it within the hierarchy

​
Location scopes for users

Location scopes control which sites and locations a user can see and work with. Scope technicians to their home site so their work order lists, asset searches, and notifications stay relevant.
1

Open the user's settings

Go to Teams & Users and open the user.
2

Set the location scope

Assign the locations or sites the user should have access to.
User settings page showing location scope assignment with selected sites

Assigning a location scope to a user

3

Save and verify

Save, then confirm the user sees only work orders and assets within their scoped locations.
Scoping affects visibility, not the data itself. Records at other locations remain intact and visible to users with broader scopes.
Use consistent area codes (for example A-01-MECH for Building A, Floor 1, Mechanical Room) so codes sort predictably in lists and reports.