How to Set Up a New Company Android Phone in 10 Minutes

Setting up a managed company Android phone takes about ten minutes, and most of that is the phone doing things by itself. You factory reset the handset, tap the welcome screen six times, scan a QR code, and wait. The device joins your organisation, applies your security policy, and installs the apps your team needs without anyone typing a Google password into it.

Here is the whole sequence, including the part nobody warns you about.

Before you start

Three things need to be true.

The phone runs Android 8 or newer. Check in Settings, About phone. Older handsets cannot be enrolled as company-owned devices, and finding that out with the box already open is annoying.

The phone is factory reset, or brand new and not yet set up. This is the step that catches everyone. Management has to be established during initial setup, before any user account exists, which is exactly what makes it unremovable afterwards. A phone already in daily use cannot be converted without wiping it.

You have connected your organisation to Google once. This is a two-minute job on Google’s own screen and you only do it for the first device, not every one.

If you are wiping a phone that has been in use, sign the previous Google account out of it before you reset, or factory reset protection will ask for that account’s password on the next boot and you will be stuck.

Step one: create an enrollment profile

Before touching the handset, decide what this phone is going to be.

An enrollment profile bundles the decisions so you do not repeat them per device: which group the phone joins, which security policy applies, which apps install, and a naming convention so the device arrives in your dashboard called something useful rather than a serial number.

For a batch of phones going to the same team, one profile covers all of them. You can reuse the same QR code across the batch.

If you are not sure which policy to pick, start with the standard business template and tighten later. A published policy can be changed after enrollment; you do not have to get it perfect now.

Step two: the six taps

Power on the factory-reset phone. You land on the Android welcome screen, the one that says hello and asks about language.

Tap the same blank area of that screen six times.

The phone responds by offering to scan a QR code. Depending on the handset it may first ask you to connect to wifi, which you should do, and on some devices it will download a small setup component before the scanner appears. That is normal.

Six taps is the whole trick. It is deliberately obscure so that a stolen phone is not trivially enrolled into someone else’s organisation.

Step three: scan

Point the phone at the QR code in your console.

From here it runs itself. The device registers with your organisation, Google’s Android Device Policy is configured as the device owner, your security policy applies, and required apps download from Managed Google Play. You will see the screen work through several stages.

On a decent connection this is usually three to six minutes, and most of it is app downloads. A phone with several large apps takes longer. You can put it down and do something else.

In your dashboard the device moves through its states as it goes, so you can watch progress rather than guess. Enroll a batch and you can see which handset is stuck.

Step four: hand it over

When setup finishes, the phone is ready. The employee does not configure anything.

What they will notice is that the Play Store shows a smaller, approved catalogue rather than everything, that a screen lock is required, and that some settings are unavailable. If the device is a kiosk it will open straight into the one app it exists for.

What they will not notice is any management app, because there isn’t one to see.

Assign the device to a person in your console at this point. Future-you, trying to work out who has the handset that stopped checking in, will be grateful.

Where ten minutes becomes thirty

Three things slow a first enrollment down, and all three are avoidable on the second.

The reset. Wiping a used phone and waiting for it to reboot is five to ten minutes before you even start. Batch this: reset the phones the evening before.

Factory reset protection. If the old Google account was not removed first, the phone demands that account’s credentials after the wipe. There is no way around it except signing in with the original account. Always sign out before resetting.

Slow wifi. App installation dominates the timeline. A congested guest network turns six minutes into twenty. Use a decent connection for the rollout.

What to do this week

1. Enroll one phone, not ten. Do a single device end to end. You will learn where your particular handsets are awkward, and it costs you fifteen minutes.
2. Write your enrollment profile down once. Group, policy, apps, naming. Getting this right means the tenth phone takes no thought at all.
3. Set a reset routine for old devices. Sign out of Google, then wipe, the night before you plan to enroll. It removes the two most common delays.

FAQ

Do I need to install an app on the phone?

No. Google’s Android Device Policy is set up automatically during enrollment as part of Android itself. There is no separate app to download and nothing for an employee to uninstall.

Can I reuse one QR code for several phones?

Yes. An enrollment profile produces a code you can scan on a whole batch. Each device registers separately and applies the same policy.

What if the six taps do nothing?

Make sure you are on the very first welcome screen of a genuinely factory-reset device, and tap the same spot rather than moving around. If the phone has already been through setup, it needs wiping first.

Does the employee need a Google account?

Not for the device to be managed. Enrollment does not involve typing a personal Google password into the handset. Apps come from Managed Google Play under your organisation.

Can I undo enrollment?

Removing management requires a factory reset of the device, which wipes it. That is the point: it is what stops someone opting out of the rules.

The first phone teaches you the process. After that, enrolling a handset is genuinely a coffee-length job.

Start a free trial and enroll one device, or read how Android Enterprise works underneath.