How to Manage Company Phones Across Several Locations
How to manage company phones across multiple locations from one office: a group per site, enrollment profiles, site Wi-Fi, filters and the right roles.
To manage company phones across multiple locations, give each site its own group, its own enrollment profile and, where the rules differ, its own security policy, then run everything from one console. A new phone at any site comes up already named, grouped and locked down. When something goes wrong, you filter the devices list by site instead of phoning around. You do not need anyone technical at the other locations, only someone who can scan a QR code.
Here is the usual starting point. A cleaning company has its main office and two satellite depots forty minutes apart. The office manager set up the first eight phones by hand. The depot leads set up their own, each a little differently. Six months later, one depot’s phones have no screen lock, the other’s are all named “Galaxy A15”, and nobody knows which phone the driver who quit last week had.
None of that is anyone’s fault. It is what happens when each site does its own setup. The fix is to decide the setup once, centrally, and make every site use it.
Why does each location drift?
Sites drift because the setup lives in people’s heads. The office does it one way, a depot lead learns a shortcut, and the next hire copies whichever phone is nearest. Three things usually go first:
- Names. Phones end up named after the model, so you cannot tell which site they belong to.
- Settings. Screen lock and blocked apps vary by who set the phone up.
- Ownership. Nobody at head office knows who holds which phone.
A device management tool fixes this by making the setup a thing you choose, not a thing someone remembers.
Step 1: One group per location
In NounDesk, a group is a set of devices that share a security policy. Make one per site: “Main office”, “North depot”, “South depot”. Add a “Spares” group for phones on a shelf.
Organizing company phones by team, site and employee covers groups in full. The point here is that every later step hangs off the site group: who gets which documents, which Wi-Fi gets pushed, how you find a phone.
If two sites run the same rules, they can share a policy and still be separate groups. You keep the reporting split without doubling your policy work.
Step 2: One enrollment profile per location
An enrollment profile saves the group, the policy and a device name prefix. Make one per site, with prefixes like “North” and “South”.
When a depot lead sets up a new phone, they factory-reset it and scan that site’s QR code. It comes up as “North 7”, in the North depot group, on the right policy. Nobody at the depot has to choose anything.
Two choices worth making on each profile:
- Code expiry. Seven days suits a code you email to a site lead. One hour suits a code you show on screen while you are on the phone with them.
- Single use or reusable. Single use is safer if the code might be shared. Reusable saves time when a site is setting up a box of phones in one sitting.
The enrollment profiles guide has the details, and our guide to rolling out 50 company Android phones in a day shows how to run a big batch. If your phones come through an authorized zero-touch reseller, they can enroll automatically the first time they are switched on, with no QR code at the site at all.
Step 3: Push each site’s Wi-Fi
Site Wi-Fi passwords are a constant small leak. They get texted around, written on whiteboards and given to visitors.
A security policy can hold up to 20 Wi-Fi networks, and every phone on that policy joins them without anyone typing a password. If all your sites share one policy, put every site’s network in it, and phones moving between sites connect wherever they land. Our post on pushing Wi-Fi to company Android phones explains the options.
Step 4: Share site documents with the site group
Each location usually has its own paperwork: an opening checklist, a key-holder list, a local price sheet. With company documents, you share a file with one group, and only that site’s staff see it. When the price sheet changes, you replace it once and every phone at that site has the new version.
Step 5: Find any phone in two clicks
On the devices list, Filters narrows by group, employee, policy, manufacturer or Android version. Pick a site and you see only its phones, with online status, compliance and Device Trust in columns.
Reports break compliance down by group too, so you can see that the South depot has three phones overdue for a security update without opening each one. The device dashboard shows the whole fleet’s health at a glance.
Step 6: Give site leads the right role
You will want someone at each site who can hand out phones and act quickly on a lost one. That is the Operator role: they can enroll devices, assign them to staff, lock, reboot and put a phone in lost mode. They cannot erase a phone or change security policies.
Keep Owner for yourself and one trusted backup, and Admin for whoever looks after policies. Our post on who should have admin access to company phones goes through the choice.
The honest limits
Roles cover the whole organization, not one site. An Operator at the North depot can see and act on phones at every location. If that matters, keep site leads as Operators rather than Admins, because Operators cannot erase phones or change policies, and every action they take is in the audit log.
One policy per group. A device in a group takes that group’s policy. If one phone at a site needs different rules, such as a front-desk kiosk, put it in its own group.
It does not track where phones are. “North depot” means the group you put a phone in, not where it physically is. Location is reported only while a phone is in lost mode.
More than 50 devices across your sites? The free trial covers up to 50. Email support@noundesk.com before going past that.
What to do this week
- List your locations and how many phones each has. Include spares in drawers.
- Create a group and an enrollment profile for each site, with a clear name prefix.
- Put every site’s Wi-Fi in the policy so nobody types a password again.
- Move existing phones into their site groups with one bulk action from the devices list, and rename the ones called “Galaxy A15”.
- Invite one Operator per site. Send them that site’s QR code and a one-line instruction: factory reset, scan, hand over.
FAQ
How do I manage company phones across multiple locations?
Make one group and one enrollment profile per location in your device management console. Every new phone at a site enrolls with that site’s name, group and policy, and you filter the devices list by group to see one location at a time.
Can each location have different security settings?
Yes. Each group can have its own security policy. If several sites share the same rules, they can share one policy and still stay in separate groups for reporting.
Does someone at each site need to be technical?
No. Someone at the site needs to factory-reset a phone and scan a QR code. The group, policy and name come from the enrollment profile.
Can a site manager only see their own location’s phones?
Not today. NounDesk roles apply to the whole organization. Give site leads the Operator role, which can hand out and lock phones but cannot erase them or change policies.
If you run phones at more than one location, try NounDesk free for 14 days and set up your first site group today.