How to Configure Multiple Users, Guest Mode Restrictions, and Ephemeral Sessions on Android

Modern mobile fleet deployments and shared family environments frequently require strict data separation between multiple individuals operating on a single physical hardware handset. Whether deploying dedicated field tablets across multi-shift logistics workers or providing loaner devices in healthcare facilities, Android natively incorporates a multi-tenancy virtualization engine known as the Android Multi-User System.

Operating directly on top of Linux kernel user IDs (UIDs) and SEAndroid security contexts, Android isolates each user profile into a distinct cryptographic domain. This architecture enables enterprise administrators and personal device owners to configure Secondary Users, temporary Guest Mode sessions that automatically discard ephemeral session caches, and fine-grained telephony or SMS permissions across profiles.

Architectural Overview: Android User Virtualization and Security Boundaries

The Android runtime virtualizes applications, sandboxes, and file storage across multiple logical profiles through dedicated Linux UID offset mappings and cryptographic encryption keys:

User Profile Type	Kernel UID Range	Credential Encryption State	Persistence Lifecycle
Primary / Owner (User 0)	0 – 99,999	Decrypted at first device unlock (Credential Encrypted / CE storage).	Permanent; retains administrative device ownership and cannot be removed without a full hardware factory reset.
Secondary User	100,000 – 199,999 (User 10)	Independently encrypted with the secondary user’s lock screen PIN/passcode.	Persistent until explicitly deleted by the primary owner or enterprise MDM policy.
Guest User	Dynamic ephemeral UID allocation	CE storage derived from ephemeral key material.	Transient; prompts for session wiping and cache purges upon every session switch or logout.
Managed Profile (Work Profile)	Scoped secondary user container	Separate CE key managed via enterprise Mobile Device Management (MDM).	Tethered to the primary owner profile; subject to remote administrative wipe without impacting personal apps.

Enabling and Configuring Secondary Users on Android

Multi-user functionality must be activated within system settings on compatible Android devices (such as Google Pixel or Android Enterprise certified hardware).

Step 1: Activate Multi-User Functionality

1. Open the Settings application on your Android device.
2. Scroll to System > Multiple users.
3. Toggle the master switch labeled Allow multiple users to the On position.
4. Optionally toggle Add users from lock screen if field operators need to switch users without unlocking the primary account.

Step 2: Provision a New Dedicated Secondary User

1. Tap Add user. A system prompt will warn that the user must set up their space.
2. Tap OK and enter a friendly name (e.g. Shift Operator Alpha).
3. Select whether to toggle Turn on phone calls & SMS for this secondary user profile.
4. Tap Set up now to switch to the profile and execute the initial Google account and biometric enrolment wizard.

Managing Guest Mode and Enforcing Ephemeral Session Wiping

For short-term loans, the native Guest profile provides complete data privacy for both the device owner and the temporary user.

Step 1: Launching a Guest Session

1. Swipe down twice from the top of the display to access the Quick Settings panel.
2. Tap the User avatar icon at the bottom of the shade.
3. Tap Add guest (or Guest if previously created). The system switches instantly into the clean guest container.

Step 2: Concluding and Discarding the Ephemeral Session

When the loaner session terminates:

1. Open Quick Settings and tap the user profile icon.
2. Tap Remove guest.
3. A confirmation dialog appears: “Remove guest? All apps and data in this session will be deleted.”
4. Select Delete. The system wipes the ephemeral user directory (/data/user/10/) and zeroes out the associated cryptographic CE keys.

Enterprise Policy Enforcement via Android Enterprise MDM / ADB

For automated fleet administration, enterprise IT teams manage multi-user states using Android Debug Bridge (ADB) or an MDM server leveraging the DevicePolicyManager API.

Automating Multi-User Policies via ADB

Connect an authorised development workstation to the device and execute shell commands:

# Query active user profiles and UID assignments
adb shell pm list users

# Create an ephemeral guest user via package manager
adb shell pm create-user --guest "Temporary Field Tech"

# Create a permanent secondary user
adb shell pm create-user "Warehouse Staff 04"

# Inspect user restrictions applied to User 10
adb shell dumpsys user

Enforcing Restrictions via DevicePolicyManager (XML/Java Policy Definition)

Enterprise device owner applications enforce multi-user governance by applying user restriction flags:

// Disallow creation of unmanaged secondary users
devicePolicyManager.addUserRestriction(
    adminComponent,
    UserManager.DISALLOW_ADD_USER
);

// Prevent secondary users from modifying cellular configurations or making phone calls
devicePolicyManager.addUserRestriction(
    adminComponent,
    UserManager.DISALLOW_OUTGOING_CALLS
);

// Disallow USB file transfer access to secondary user profiles
devicePolicyManager.addUserRestriction(
    adminComponent,
    UserManager.DISALLOW_USB_FILE_TRANSFER
);

Troubleshooting Android Multi-User Configurations

Use this diagnostic reference table to resolve permission conflicts, storage exhaustion, and multi-user profile failures:

Issue	Underlying Root Cause	Corrective Action
“Multiple users” menu is missing or greyed out in Settings.	OEM disabled multi-user support in build.prop, or device storage has fallen below the minimum safety threshold (typically 1.5 GB).	Verify device build properties via adb shell getprop fw.max_users. If set to 1, the OEM has locked multi-tenancy. Clear storage on User 0 if low disk space triggered safety disablement.
Secondary user cannot place voice calls or send SMS.	Telephony permissions are restricted by the Primary Owner account.	Navigate to Settings > System > Multiple users on User 0. Tap the gear icon beside the target user and toggle Turn on phone calls & SMS to Allowed.
Application installed on User 0 fails to install or launch on User 10.	Application APK does not support multi-user APK installation flags or requires unique hardware token binding.	Install the package explicitly into the secondary user space via ADB: adb install --user 10 path/to/app.apk.
Internal storage capacity drops precipitously with multiple profiles.	Each user profile generates distinct caches and app data folders, preventing deduplication of user-specific assets.	Audit per-user storage allocation using adb shell dumpsys diskstats. Remove orphaned profiles and enforce automatic cache clearing policies on secondary users.
Guest profile retains previous user browsing history or credentials.	Guest was switched out without selecting “Remove guest”, preserving the state for a resumed session.	Always select Remove guest or toggle Start over when entering the guest profile to guarantee that cryptographic data stores are wiped.

Implementing structured multi-user profiles and ephemeral guest policies guarantees airtight separation between individual operators, safeguarding corporate compliance and personal data integrity on shared Android hardware.