Skip to main content

Policy Overview

Policies are the core of device management in AndroidNexus. They define security settings, restrictions, app configurations, and device behavior for enrolled devices. Access policies by clicking Policies in the top navigation bar.

Policies Page

What is a Policy?

A policy is a configuration profile that controls how devices behave. When you apply a policy to a device (typically during enrollment via an onboarding token), AndroidNexus enforces those settings automatically.

The Policies Page

Filter Tabs

The top of the page includes filter tabs to quickly view policies by device mode:

TabDescription
All PoliciesView all policies regardless of mode
Fully managedPolicies for company-owned, fully managed devices
COPECompany-Owned, Personally-Enabled device policies
DedicatedPolicies for dedicated/kiosk devices
BYODBring Your Own Device (work profile) policies

A counter shows the total policies: "Showing all policies • X total"

Policy List

The main table displays all policies with these columns:

ColumnDescription
Policy NameName of the policy
DescriptionOptional policy description
ModeDevice management mode (badge: Fully managed device, Dedicated device, etc.)
VersionCurrent version number (e.g., v17)
AssignedNumber of devices using this policy
TagsCustom tags for organization
Last UpdatedDate of last modification
ActionsEdit button to modify the policy

Creating a New Policy

Click the Create New Policy button (orange button, top right) to create a new policy.

Create/Edit Policy Page

Create Policy Page

The policy editor is organized into header fields and configuration tabs.

Policy Header

FieldDescription
Policy NameRequired. A descriptive name for the policy
Device ModeDropdown to select: Personally Owned (BYOD), Fully Managed, Dedicated, COPE
DescriptionOptional description of the policy's purpose

Action Buttons (Edit Mode)

When editing an existing policy:

ButtonDescription
HistoryView policy version history
Assign DevicesAssign this policy to devices
Save PolicySave changes to the policy

Policy Configuration

The left sidebar contains configuration tabs:

  • Security - Security and lock screen settings
  • Applications - App deployment and restrictions
  • Network - Wi-Fi, VPN, and network settings
  • Device Info - Device information and identity settings
  • Display - Screen and display configuration
  • Work Profile - BYOD-specific settings (shown for BYOD policies)

Security Settings

The Security tab contains multiple sections organized with orange section headers. Each setting has a toggle switch and an info icon (?) for additional context.

Require Device Lock

A standalone toggle at the top to force users to set up a lock screen.

Lock Screen Security (Section)

SettingDescription
Disable Camera on Lock ScreenBlock camera access from lock screen
Disable Biometric on Lock ScreenDisable fingerprint/face unlock on lock screen

Data Protection (Section)

SettingDescription
Require EncryptionForce device storage encryption
Allow ScreenshotsToggle on/off for screenshot capability (enabled by default)
Block CameraCompletely disable the camera
Block MicrophoneDisable microphone access
Disable USB Data TransferBlock file transfers over USB

Developer & Advanced (Section)

SettingDescription
Allow USB DebuggingEnable/disable ADB debugging
Allow Developer OptionsShow/hide developer settings
Block Factory ResetPrevent users from factory resetting
Disable Safe BootBlock booting into safe mode
Credential Manager Policy (Android 14+)Dropdown with options: Unspecified (Default), and other credential handling modes

Applications Settings

The Applications tab allows you to configure app deployment and restrictions.

App Installation Settings (Section)

SettingDescription
Allow App InstallationToggle to allow/block app installation
Allow Install from Unknown SourcesToggle to allow sideloading APKs
System Update PolicyDropdown: Automatic, Windowed, Postpone

Kiosk Mode Settings (Section)

SettingDescription
Enable Kiosk ModeToggle to lock device to specific apps

Allowed Applications

A list of apps that will be installed or available on devices. The orange Add from Play Store button opens the Managed Google Play selector.

Each app in the list shows:

  • App name and package name (e.g., com.whatsapp.w4b)
  • Status badge: Required (will be force-installed) or Setup Required (needs configuration)
  • Action icons: Configure App (gear), Move to Blocked, Remove from Policy (X)

Blocked Applications

Enter package names to block (e.g., com.facebook.katana). Blocked apps will be disabled on devices, including preloaded system apps.

Device Modes Explained

Fully Managed Device

Complete control over the entire device:

  • IT manages all apps and settings
  • No personal usage intended
  • Best for company-owned devices used only for work

Dedicated Device

Locked to specific use cases:

  • Kiosk mode configurations
  • Single-app or multi-app launcher
  • Ideal for shared devices, point-of-sale, signage

COPE (Company-Owned, Personally-Enabled)

Company device with personal space:

  • Work profile for business apps
  • Personal profile for user apps
  • IT controls work side, limited control over personal

BYOD (Bring Your Own Device)

Work profile on personal devices:

  • Separate container for work apps
  • Personal apps/data untouched by IT
  • Work data is encrypted and isolated

Applying Policies

Policies are applied to devices in two ways:

During Enrollment

  1. Create an onboarding token in Onboarding
  2. Select a policy in the Policy Assignment section
  3. All devices enrolled with that token receive the policy

To Existing Devices

  1. Go to Devices
  2. Select devices using checkboxes
  3. Click Apply Policy
  4. Select the policy to apply

Policy Versioning

Each time you edit and save a policy, the version number increments (v1, v2, v3...). This helps track changes over time.

When you update a policy:

  • The new version is automatically pushed to all assigned devices
  • Devices sync the updated policy on their next check-in
  • You can see the applied version in each device's detail view

Best Practices

  1. Use descriptive names - Name policies by purpose (e.g., "Sales Team Standard", "Warehouse Kiosk")
  2. Start restrictive, then relax - Easier to loosen restrictions than add them later
  3. Test with a pilot device - Apply new policies to test devices first
  4. Document policy purposes - Use the description field to explain intent
  5. Group similar devices - Create policies for device categories, not individual devices
  6. Review regularly - Audit security settings quarterly

Next Steps