As your Device Management setup grows across regions, countries, and stores, so does the number of people who need access to the Dashboard. Until now, every Segment permission came down to three choices: Admin, Editor, or Viewer.

That often meant choosing between two bad options. You could give someone full Admin access just because they needed one extra action in one place, or find workarounds to fill the gap. Neither is ideal when you're trying to keep access tight and your organization secure.

With Custom Collaborator Roles, you decide exactly which actions each person can take in Device Management.

🚀 How it works

Create a role once for your whole organization, pick the Dashboard actions it includes, and give it a name that matches the job, like Helpdesk, Store Admin, or Auditor. Then assign it to any Segment permission, the same way you assign built-in roles today.

The role defines what someone can do, and the Segment permission defines who gets it and where. Define a role once and reuse it across as many Segments as you need.

⚙️ Key Capabilities

• Custom roles built around real jobs: select exactly the actions each role needs, and give it a clear name and description.
• Start from what you already have: duplicate a built-in role or use an existing one as a template, then adjust it. The built-in Admin, Editor, and Viewer roles are still there, unchanged.
• Workspace and Device Management actions, clearly separated: every action belongs to the Workspace (W) or Device Management (M) group. W and M badges show at a glance what each role includes before you assign it.
• Built-in guardrails: Workspace actions only apply on the Global Segment. If you assign a role that includes them on a child Segment, the Dashboard warns you before you save.
• Protected Owner actions: sensitive actions like transferring ownership or deleting the workspace stay locked and can't be granted through any role.
• Predictable inheritance: permissions add up as you go down the Segment tree, so access in a child Segment always includes what's granted above it.

📌 Use Cases

• Helpdesk teams: let support agents handle day-to-day device tasks without touching organization settings.
• Store or site admins: give local teams the extra actions they need in their own Segment, and nothing beyond it.
• Auditors and compliance teams: create a role focused on visibility, tailored to what they need to review.
• Regional delegation: build one role per job and reuse it across every region, country, or store in your Segment tree.

📚 Learn more

• Custom Collaborator Roles.
• Segments.

When someone on your team runs into a problem, the fastest fix is usually to see their screen. Too often that means long calls describing what's on the screen, or asking the user to install and set up a remote access tool themselves. And when the device belongs to someone who isn't at their desk, you often have to wait until they're back.

Applivery now integrates with TeamViewer to bring Remote Support to your Windows and macOS devices, right from the Applivery Dashboard.

🚀 How it works

Enable TeamViewer Remote once in a Policy. Applivery silently installs TeamViewer Host on every device that Policy applies to and registers each device with TeamViewer. From then on, you can start a remote session from the device's Action menu. Nobody has to install or configure TeamViewer on the device.

On macOS, Applivery also applies the profiles TeamViewer Host needs for Remote Desktop and Accessibility. The only step on the Mac is approving Screen & Audio Recording for TeamViewer Host, and the user can do that without admin rights.

⚙️ Key Capabilities

Enabled per Policy: turn it on for a whole group of devices in a single step, and it works with Policy composition like the rest of your settings.

Silent installation: Applivery deploys TeamViewer Host automatically, so users don't need to install it themselves.

You choose the session type each time you connect:

• Unattended: connect without anyone accepting on the device.
• Attended: the person at the device accepts the session first.
• View only: see the screen without sending any keyboard or mouse input.

Open sessions your way: in a new browser tab using TeamViewer's web client, or in the TeamViewer desktop app.

Status at a glance: a badge next to each device shows whether it's ready for a session before you start.

Simple licensing: each device with the feature active uses one license, no matter how many sessions you open. The license is released automatically when the feature is deactivated on that device.

📌 Use Cases

• Help remote employees in real time: see exactly what they see and guide them through the fix, wherever they're working.
• Fix unattended machines: troubleshoot a device when nobody is sitting in front of it.
• Observe without interfering: use View only to follow along while the user shows you the issue.
• One workflow for a mixed fleet: support Windows PCs and Macs from the same Dashboard, in the same way.

📚 Learn more

TeamViewer Remote Support is a premium feature. Check availability on the Applivery pricing page.

• TeamViewer Remote Support for Windows.
• TeamViewer Remote Support for macOS.

Want to enable it for your organization? Contact your Customer Success Manager, and we'll help you get started 💬

For years, device management has been stubbornly reactive—forcing admins to manually filter lists, export CSVs, and hunt for a single nugget in a vast sea of data. But while fleet telemetry has exploded, IT capacity hasn't kept pace. Because traditional consoles passively wait to be interrogated rather than surfacing what matters, configuration drift and security risks accumulate quietly in the background.
​
The answer is already in your Workspace—getting to it just shouldn't take so long.

💡 Introducing Applivery Intelligence

Applivery Intelligence lets you get to your data by asking a question instead:

• Which Macs have not checked in for 30 days?
• Show me every Device that is missing disk encryption, grouped by Policy.
• Lock the laptop David lost yesterday.

It answers from live data through the same API the Applivery dashboard uses, so you never get a cached copy. Results come back as interactive tables, charts, maps, or Device cards. If you ask it to change something, it asks you to confirm first.
​
There's nothing to install, no API key to generate, and no second login. Click the ✨ button in the top bar of the Applivery dashboard and start asking.
​

⚙️ Key Capabilities

💬 Chat: answers you can work with
Ask in plain language. Behind the scenes, a team of Agentic Specialists (Compliance, Security, Policy, Insights, Vulnerability, and more) fetches the data and builds the answer. You can sort and filter the results, drill into a Device, download a CSV, or pin the answer to a dashboard. Type @ to point at a specific Device, Policy, Segment, or user by name.
​
📊 Insights: live dashboards with alerts
Turn any answer into a widget that refreshes on its own schedule. Add alert rules for thresholds, sudden changes, or missing data, and you'll hear about problems before someone reports them.
​
🔄 Workflows: automate what happens next
Build visual automations that start from an alert, a schedule, a webhook, or a click. Send the results to Slack, Google Chat, or email, and add a human approval step before anything touches Devices in bulk. You don't even have to draw the workflow: describe it, and the AI Workflow Builder proposes the changes for you to approve.
​
🕵️ Cowork: agents that check your fleet for you
Cowork doesn't wait for your questions. It runs checks in the background and sends the results to an inbox as findings. It looks for stale check-ins, compliance drift, dormant privileged accounts without 2FA, Policy conflicts, unusual data usage, and more. When a check offers a fix, you can approve it, and you can revert it just as easily.
​
🔌 Applivery MCP: bring your own assistant
Already working in Claude or ChatGPT? The Applivery MCP server gives those assistants access to your fleet, with the same capabilities and the same permissions.

🔐 Built to be safe

• It acts as you. Your Applivery role sets the limit: if you can't wipe a Device in the dashboard, you can't wipe it through Intelligence either. Every action shows up in the audit log under your name.
• Wipe, lock and delete always ask for confirmation, whatever your settings are.
• You decide what runs without asking. You can set each capability to Always allow, Needs approval, or Blocked.
• It won't make up answers. If it can't reach your data, it tells you so instead of guessing.

📌 Use Cases

• Monday morning check: ask your four or five usual questions and pin each answer to a dashboard that keeps itself up to date.
• Lost device: find the laptop, check where it was last seen, and lock it, all in one conversation.
• Compliance audits: list non-compliant Devices and ask what would break if you changed the Policy, before you change anything.
• Security response: look up known CVEs for an OS or app version in your fleet, with severity and exploit likelihood.
• Always-on hygiene: let Cowork flag stale devices, over-broad access, and inventory mismatches while you work on something else.
  ​

🚀 Getting started

Applivery Intelligence is licensed per person, by seat, and your organization Owner assigns the seats. Chat is available on every tier, including Free. Insights, Workflows and Cowork need a Max or Ultra seat. You'll also need Applivery Endpoint Manager in your Workspace.
​
👉 Read the full documentation here.

Rugged scanners, industrial PDAs, point-of-sale terminals, digital signage. The Android devices that ship without Google services are often the ones you deploy in the highest volumes, and until now they were the hardest ones to get onboarded at scale.

No Google account, no Managed Google Play, and no Zero-touch means every AOSP device had to be set up individually, with an admin picking the right policy by hand for each one. Multiply that by a few hundred terminals across several sites, and enrollment stops being a task and starts being a project.

Smart Enrollments now work on AOSP devices — and they work exactly the same way they already do on the rest of your Android fleet. Same fields, same conditions, same rules, same deployment steps. Nothing new to learn, nothing extra to enable.

⚙️ Key Capabilities

• Conditional policy assignment. Define rule sets so every device receives the right policy automatically.
• Enrollment guardrails. Limit who and what can enroll: by user authentication through your SSO integration (email patterns or user groups), or by device information such as IMEI or serial number.
• Auxiliary fields. Add dropdowns that the user fills in during enrollment. Their answers become device tags, and those tags decide which policy applies.
• Target segment and tags. Enrolled devices are assigned to the segment you choose.
• Display name pattern. Device names are built automatically by combining device properties, so your inventory stays readable from day one.
• Identical configuration flow. Everything you have already built for your Android Enterprise fleet applies here.

📌 Use Cases

• Warehouse and logistics. Roll out hundreds of rugged scanners with the right policy per site, without touching them one by one.
• Retail. Enroll point-of-sale terminals across multiple stores, using auxiliary fields so each store's devices get their own configuration.
• Digital signage. Provision display units consistently, with naming and segmentation applied automatically.
• Field operations. Hand industrial PDAs to technicians and let SSO authentication decide which policy each device receives.

📚 Learn more about AOSP Smart enrollments with our complete step-by-step guide.

Managing dedicated AOSP devices has always come with a trade-off. Because AOSP hardware doesn't ship with Google Mobile Services or Managed Google Play, teams running rugged scanners, industrial terminals, or custom-OS devices were limited to the most basic kiosk setups — one app, locked down, and not much room to shape the experience. If you wanted a branded, multi-app launcher with granular control, you had to reach for standard Android Enterprise hardware.

Not anymore.

Applivery's Advanced Launcher is now fully supported on AOSP devices — and it behaves exactly like it does on Fully Managed (AMAPI) devices. No stripped-down version, no missing options. The same managed launcher experience you already use on standard Android now extends to the AOSP fleet you thought you'd have to compromise on.

⚙️ Key Capabilities

• Both operating modes available: run the device as a managed Launcher (a corporate launcher with policy-driven controls, without full lockdown) or as a full Kiosk that locks the device to a defined set of apps.
• Full personalization: corporate wallpaper, icon size, app layout, folders, and a configurable startup app — all with support for dynamic variables like device serial or assigned user.
• Granular settings access control: restrict the Settings app entirely, define a specific landing view, or password-protect it so only technicians and store managers can make changes.
• Advanced display and power controls: screen brightness, timeout, maximum time to lock, stay-on-plugged modes, and customizable header/footer.
• Network Escape Hatch: keep devices recoverable if they can't reach the network at boot — critical for unattended, field-deployed hardware.

Everything is configured from the same Kiosk section of your Policy — no separate workflow for AOSP.

📌 Use Cases

• Rugged and industrial fleets: scanners, handhelds, and warehouse terminals that run on AOSP hardware but need a branded, controlled multi-app experience.
• Retail on custom hardware: point-of-sale and clienteling devices with a corporate look and technician-only Settings access.
• Field and logistics devices: unattended terminals that stay recoverable thanks to the Network Escape Hatch.
• Digital signage and always-on kiosks: screen-always-on displays with locked navigation and a clean, defined app set.

What about the other modes?

Single App kiosk remains fully supported on AOSP, as before. The Basic Launcher is still not available on AOSP, since it relies on Android's native Device Policy Controller infrastructure that AOSP devices don't include — but with the Advanced Launcher now on board, you get a far more capable multi-app experience anyway.

📖 Read the full guide here.

Managing a fleet means living in the details — knowing exactly what's on each device, reaching the right endpoints at the right time, and trusting that your reports say the same thing everywhere. This release brings a batch of improvements across Device Management and App Distribution that do exactly that: more control over Android and eSIM, better visibility into certificates, and cleaner, more consistent reporting.

Here's everything that's new. 👇

📱 Device Management

🔔 Send push notifications to Android devices

You can now send a push notification straight to Android devices that will be handled by the Applivery Android Self-Service App — either as a single action on one device, or in bulk across many at once. It's a direct line to your managed devices when you need to reach them without waiting.

⚙️ Managed configurations for AOSP apps

AOSP apps now support managed configurations, so you can pre-define and push app settings remotely instead of configuring them by hand on each device. Same centralized control you already have for Managed Google Play apps, now extended to AOSP.

📶 More eSIM management options

Two new capabilities for devices with eSIM:

• A command to retrieve the EID (the unique identifier of the device's embedded SIM).
  ​
• A wipe data flag to control eSIM data handling during a wipe.

🔐 Certificate Report History (Android EMM)

You can now consult the history of certificate reports for Android enterprise devices, not just the latest state. This unlocks timeline/history views and lets you inspect past certificate report snapshots in detail — with sensitive identity data automatically redacted so reports stay safe to share.

🌳 Segment tree keeps your "Show children" selection

The segment tree now remembers your "show children elements" setting, so the view you set stays applied as you work instead of resetting on every new session. A small change that saves a lot of repeated clicks.

📊 Unified report configurations across native agents

We've standardized the report descriptions and configurations across the native agents, so the same report means the same thing no matter which platform you are configuring — less ambiguity, easier cross-platform reporting.

📦 App Distribution

🖥️ See device and platform in Downloads

The Downloads view now shows the device and platform for each download, giving you clearer visibility into exactly where and on what your apps are landing.

Most MDM solutions are built around Android Enterprise and Google Mobile Services. That works great for standard devices — but what about your rugged terminals, industrial PDAs, point-of-sale hardware, and digital signage that ship without GMS?For organizations deploying these devices at scale, management has historically meant fragmented tools, vendor-specific workarounds, or simply giving up on centralized control.Not anymore.Applivery now supports full MDM for AOSP devices — Android devices that run without any Google dependency. No Google account. No Android Enterprise setup. No Managed Google Play. Just the same Applivery Dashboard you already use.

⚙️ Key Capabilities

• Kiosk Mode — lock a device to a single app or a curated suite, with full control over the navigation bar, status bar, and power button
• Silent App Distribution — install, update, and uninstall APKs directly from the Dashboard, no Play Store required
• Policy Enforcement — password complexity, keyguard restrictions, factory-reset protection, remote wipe, and 80+ configurable settings
• Wi-Fi & Certificate Management — silently provision corporate networks (Open, WPA, WPA-Enterprise with EAP-TLS, PEAP, and TTLS)
• Always-On VPN — force all device traffic through a corporate VPN with optional lockdown mode
• Remote Commands — lock, reboot, reset password, clear app data, and disenroll devices in real time
• OEM Configurations — extended support for Zebra, Bluebird, Samsung Knox, and other AOSP hardware
• Factory Provisioning — pre-install the Applivery DPC in an OEM image and provision devices automatically at first boot

📌 Use Cases

• Retail and logistics fleets running ruggedized Android terminals
• Point-of-sale and self-service kiosks
• Industrial and warehouse PDAs without GMS certification
• Digital signage and fixed-purpose devices
• Any OEM Android build requiring dedicated device lockdown

🔜 Coming in June 2026

• Remote Support & Control — view and control AOSP devices directly from the Dashboard
• Advanced Kiosk Launcher — Basic and Advanced Launcher modes for AOSP
• Work Profile on AOSP — separation between corporate and personal data on non-GMS devices
  ​

📖 Ready to get started? AOSP management is available on all Applivery plans. Learn more here and contact your Customer Success Manager to get it enabled in your Workspace.

We're making an update to how tag-based filters work in App Distribution to improve overall platform performance.

🔎 What's Changing

Tag filters in builds will now require an exact match, including capitalization. Until now, tag searches were case-insensitive, meaning Release, release, and RELEASE would all return the same results. In the coming days, only an exact match will return results.
This change affects build tag filters specifically. Partial device searches will continue to work as before, with case-insensitive matching still supported.

📌 What You Need to Do

Review your current tag naming conventions and make sure the tags you use in filters match exactly — including uppercase and lowercase letters — the tags assigned to your builds.
For example, if your builds are tagged Production, searching for production or PRODUCTION will no longer return results. You must search for Production exactly.

⚙️ Why We're Making This Change

This update is necessary to address a performance issue. Exact matching allows us to maintain a faster and more reliable experience across the platform.

We’ve introduced Smart Attributes, a new capability that allows you to define and manage custom attributes associated with devices.

This feature enables more precise targeting and dynamic segmentation across your device fleet.

⚙️ Key Capabilities

🏷️ Custom Attributes

Define attributes tailored to your organization (e.g., location, department, usage type).

🔄 Dynamic Assignment

Assign and update attribute values per device as needed.

🎯 Integration with Device Audiences

Use Smart Attributes as filtering criteria in Device Audiences to enable dynamic grouping.

🧠 Flexible Targeting Logic

Combine Smart Attributes with existing filters (e.g., OS, model, tags) for advanced segmentation.

🔍 Why It Matters

Smart Attributes allow you to move beyond static configurations and adopt a more flexible, scalable, and data-driven approach to device management.

Whether you’re organizing devices by business unit, region, or use case, Smart Attributes make it easier to apply the right actions to the right devices — at the right time.

📌 Use Cases

• Device classification by business unit, location, or ownership.
• Conditional policy or configuration targeting.
• Gradual rollouts based on custom-defined segments.

Smart Attributes extend the device data model, allowing administrators to implement custom segmentation logic without relying on static structures. This improves scalability and flexibility in large or complex environments.

💡 Enable It Today!

Smart Attributes are only available on Enterprise plans. If you’re not sure which plan you’re on, check the pricing page or reach out to your Customer Success Manager.

👉🏻 You can learn more about Smart Attributes here.

We've completely reimagined the Applivery Android and iOS MDM Agents. Version 2.0 goes far beyond background telemetry — it now puts a full corporate app store directly in the hands of your end users, without compromising IT control.

No more tickets. No more manual installs. Just the right apps, available on demand.

⚙️ Key Capabilities

📦 Application Catalog

End users can browse, install, update, and uninstall corporate apps directly from their devices. Apps are synced automatically from your Applivery Policy — no web console required on the user side. Corporate APKs are silently sideloaded from Applivery servers; Play Store apps open natively in Google Play with real-time status sync back to the agent.

🔄 Over-the-Air Updates

A dedicated Updates tab surfaces all apps with a pending version bump. Users see exactly what needs updating and can act immediately. Admins retain full control over which versions are available.

🔖 Bookmarks

Share internal URLs, web tools, and documentation with your fleet — organized by category and always up to date via managed configuration. No more pinning links in Slack.

📊 Status Dashboard

Users get a real-time view of every management agent running on their device: Location tracking, App Usage, Data Usage, Network Signal, and Resource downloads (see OS-specific reports for more details) — with green/gray/orange health indicators and last-sync timestamps. Less noise for IT, more transparency for users.

🛡️ Full IT Control

Every section of the portal (Applications, Bookmarks, Status, Files, Notifications) can be independently toggled per device or device group via managed configuration. Set a default view, restrict what users see, and push changes silently — all from the Applivery Dashboard.

📌 Use Cases

Frontline & field teams

Give warehouse, retail, or field workers instant access to the tools they need, without waiting for IT to push installs remotely.

BYOD / COPE

Let employees self-serve corporate apps within a controlled, policy-enforced environment.

App rollouts at scale

Reduce helpdesk load during large app deployments by empowering users to install on their own schedule.

Distributed IT teams

Surface device health status to users directly, cutting down on "my tracking isn't working" support tickets.

Internal resource sharing

Replace ad hoc link sharing with a curated, always-current bookmarks section tied to your managed config.

The Self-Service Portal is fully controlled through your existing Android and iOS managed configuration policy in the Applivery Dashboard. Feature sections are toggled individually, default views are configurable, and the entire experience is invisible to users unless you enable it — so you can roll it out gradually.

⚠️ Minimum requirements

• Android 7.0+ · Fully managed or work profile devices · Applivery Android MDM Agent v2.0.0
• iOS 16.0+ · Applivery iOS MDM Agent v2.0.0

📚 Full documentation is now available for both Android and iOS MDM Agents.