Last updated on July 3, 2026
Guide: What Can a Location Admin Do?
The regional lead. Location Admins own the setup for the Locations they're assigned to.
3-minute read
A Location Admin is a User who runs one or more Locations end-to-end without holding the keys to the whole workspace. They sit between an Approver (who owns leave decisions for a Department) and an Administrator (who owns the whole company). It's the role to reach for when a company is split across countries, offices, or regions and each side needs someone local who can move on their own.
Why the role exists
In a company with offices in different regions, holiday calendars, leave policies, and even the definition of a working week rarely match. Rolling those decisions up to a single Administrator slows things down and puts someone without local context in charge of local details. The Location Admin role solves that: the person closest to the region owns its setup, while company-wide settings like billing and plan stay with the Administrator.
Regional HR, country managers, and office leads are the typical fit.
What Location Admins can and can't do
- Edit the Location itself: holidays, working week, and Leave Policies
- Edit User profiles for Users in the Location, including working days and quotas
- Add a leave on behalf of a User in the Location
- Invite new Users into the workspace
- Create and edit Departments, and set their Approvers
- Create and manage Team Notifications
- Generate and schedule Reports
- See every User, Department, and Location in the workspace in read-only for context
- ✗Create new Locations, or edit Locations outside their scope
- ✗Edit Users who belong to a Location they don't manage
- ✗Change plan, billing, or workspace-wide settings
- ✗Manage Labels or workspace-level Add-ons that are Administrator-only (Seniority Entitlement, Entitlement by Role, Visibility Manager, Open API)
- ✗Reassign the Location Admin role or promote another User to Administrator
Anything workspace-wide (billing, plan, Labels, Admin-only Add-ons) still needs an Administrator.
How the role stacks with others
Location Admin isn't exclusive. A User can be a Location Admin and an Approver at the same time (in fact, that's the common shape: someone who runs a Location and also approves leave for a Department inside it). When roles stack, the User gets the union of the permissions, scoped where each role is scoped:
How Location Admins are assigned
The Location Admin role is granted by an Administrator on the User's profile. An Admin picks which Location(s) the User will manage; from that moment on, the User sees the Location Admin controls for those Locations. The role can be removed the same way, and a User can be assigned to more than one Location if that's the way the company is split.
What this means for the team
Common Questions
Yes. When an Administrator assigns the role, they can pick more than one Location. Everything the Location Admin can edit is scoped to that combined set of Locations.
Yes. Inviting Users into the workspace is part of the role. The new User's Location is picked at invite time and needs to be one the Location Admin manages.
They still show up in the Users list for context, but the edit controls (profile, working days, quota, add leave) don't apply. Anything cross-Location has to go through an Administrator.
It depends on the Automation. The ones open to Approvers (Blackout Period, Notice Period, Maximum Users Away, Leave Duration, Probation Period) can be configured if the User is also an Approver on the affected Department. Admin-only Automations (Seniority Entitlement, Entitlement by Role) stay with the Administrator.
Book a Call