A Location Admin (formerly Building Admin) manages operations within designated boundaries. To prevent accidental "over-permissioning" or data leaks in multi-facility organizations, a Location Admin is restricted to performing tasks only within the physical Locations assigned to their profile.
Step-by-Step Instructions
Navigate to the Users page from the left navigation sidebar.
Select the target user from the table to open their details card, then click Edit in the bottom bar (or click the + button in the top-right corner of the table to create a new profile).
Select Location Admin from the Role dropdown menu.
Locate the Locations multi-select dropdown field on the form.
Click the Locations field to open the list of active facilities.
Select the physical Locations this user is authorized to manage. (You can select multiple Locations).
Critical Validation: Location Admins must be assigned to at least one physical Location. Leaving this field blank will trigger an on-screen validation error on save.
Click the SAVE button in the bottom edit bar.
A green success banner confirms the user configuration was saved, and you will be returned to the active user list.
Operational Scope of a Location Admin
Once saved, the system automatically applies the following boundary rules to the Location Admin's dashboard:
Filtered Lists: When viewing the assets directory or work orders table, the Location Admin will only see records that belong to their assigned Locations. Equipment or tickets in unassigned buildings are completely hidden.
Filtered Drop-downs: When creating new assets or work orders, the Location/Building dropdown options will only display their assigned Locations.
Technician Scoping: When assigning personnel to a work order, the user selection lists will only display technicians who share overlapping Location clearances, ensuring that local work is assigned to local teams.
Access Controls Grid: In the settings dashboard, the permission columns for the Location Admin are visible but non-editable. This prevents accidental lockouts and guarantees they retain standard administrative functions within their scoped boundaries.
Troubleshooting & Common Alerts
Error: "At least one location is required"
Cause: You selected the Location Admin role but did not select any facilities in the Locations dropdown.
Resolution: Click the Locations dropdown on the form, select at least one physical Location, and click SAVE again.
See Also
Understanding Aetos User Roles
How to Create a New User
How to Assign Users to a Work Order