DeepManage

Use cases

Shared devices across shifts

A handheld that passes from the night shift to the morning shift, or a ward tablet used by several nurses, needs different handling than a personal work phone.

Who it is for

  • Warehouses, depots and stations with handhelds that change hands
  • Hospitals and clinics with ward tablets used by several staff
  • Retail stores with shared store devices
  • Schools with tablet carts used by different classes

Common problems

  1. Nobody knows who had the device

    When a device is damaged, lost or misused, there is no record of which worker was using it at the time.

  2. One login for everyone

    A shared password on the device and in the apps means anyone can see the previous user's work and there is no accountability.

  3. Devices drift between shifts

    Each user changes something, installs something or leaves an app open, and the next shift starts with a device in an unknown state.

How to set it up in DeepManage

  1. Step 1

    Enroll the devices as fully managed

    Enroll each device with QR code or NFC, as a userless device if it belongs to a team rather than a person.

  2. Step 2

    Lock it to work apps

    Use kiosk mode or an app allow list so the device only offers the apps the job needs.

  3. Step 3

    Turn on the sign-in screen

    In the policy, require workers to sign in with their DeepManage account after every restart, or after a set time since the last sign-in.

  4. Step 4

    Decide how data is cleared

    Clear a specific app's data from the console when a device changes hands, or rely on the business app's own sign-out.

Screenshot: Shared devices across shifts

What a shared device is

A shared device is a company-owned phone, tablet or handheld that several people use, usually one after another. Typical cases are scanners in a warehouse, ward tablets in a hospital, store devices in retail and tablet carts in schools. The device belongs to the organization and stays at the site, while the people using it change with each shift.

Because the device is company-owned, it is enrolled as fully managed, the same as other company-owned devices. The difference is in how users are handled.

How DeepManage handles shared use

DeepManage keeps a shared device as a single managed device and adds a user layer on top:

  • Sign-in screen: a policy can require a DeepManage sign-in after every restart, or after a set time since the last sign-in. Until someone signs in, the device stays on the sign-in screen.
  • Personal accounts: each worker signs in with their own user name and password. User accounts are managed in the console and can be linked to your directory, see identity and integrations.
  • Sign-out and handover: a worker can sign out and pass the device on. If you want the device to stay with one account, the policy can hide the sign-out option.
  • Watermark: the screen can show a watermark with the signed-in user’s name.

Combined with kiosk mode, the device offers only the work apps, whoever is signed in.

What DeepManage does not do

It is worth being clear about the limits. DeepManage does not create a separate Android user profile for each worker, and it does not wipe all app data automatically when a shift ends. Data left inside a business app is cleared in one of two ways: an administrator clears that app’s data from the console, or the app clears it when the user signs out. When you plan a shared-device rollout, check how each business app handles sign-out.

If a device needs a full reset, for example when it moves to another site, you can wipe it remotely and enroll it again.

Keeping shared devices in a known state

Shared devices drift quickly. A strict policy blocks the settings users tend to change, app management keeps the same app versions everywhere, and security and compliance rules restrict a device that falls out of line.

Where shared devices are common

Shared devices appear in transport and logistics, retail, healthcare and education. Read about the wider picture in device ownership models.

Frequently asked questions

Does DeepManage create a separate Android user for each worker?

No. A shared device stays one managed Android user. Each worker signs in to DeepManage on the device with their own account, and the device is then tied to that account.

Is app data cleared automatically at the end of a shift?

Not automatically. An administrator can clear the data of a chosen app remotely, and many business apps clear their own data when the user signs out. Plan this per app.

Can workers sign out and hand the device over?

Yes, if the policy allows it. The next worker then signs in with their own account. You can also hide the sign-out option so the device stays with one account.

Can the signed-in worker's name be shown on the screen?

Yes. A policy can show a watermark on the screen that includes the signed-in user's name, which discourages screenshots and photos of sensitive screens.

See DeepManage on your own devices

Tell us about your fleet and we will prepare a demo environment for your team.