As an introduction to Applivery’s Device Management, we highly recommend you explore and understand the following basic concepts that will be explained in detail in the following chapters of the documentation since they represent the very basic concepts of our platform.
Workspaces #
A Workspace is the organizational environment where devices, policies, resources, automation rules, and administrators are managed.
Each workspace operates independently and contains its own configuration, segmentation model, and access control structure.
Device #
A Device is any enrolled Apple, Android, or Windows endpoint managed through Applivery.
Once enrolled, a device can receive policies, applications, scripts, configurations, and security settings defined by administrators.
Enrollment #
Enrollment is the process of registering a device into Applivery’s management system.
During enrollment, the device establishes trust with the platform and becomes eligible to receive configurations, policies, and automated actions.
Enrollment methods vary depending on the operating system and organizational setup.
Smart Enrollment #
Smart Enrollment automates the enrollment process by applying predefined rules and conditions.
Devices that meet specific criteria can automatically receive policies and configurations during enrollment, ensuring standardized setup without manual intervention.
Policy #
A Policy is a structured collection of configurations that define how a managed device behaves.
Depending on the operating system, policies may include:
- Security restrictions.
- Passcode and encryption requirements.
- Application management rules.
- Network configurations (Wi-Fi, VPN, email).
- Kiosk mode settings.
- System restrictions.
Policies enforce compliance and operational standards across devices.
Device Audience #
A Device Audience is a dynamic group of devices automatically generated based on predefined conditions (such as OS version, compliance status, model, or custom attributes).
Device Audiences update automatically as devices meet or no longer meet the defined criteria, enabling scalable targeting for automation and policy assignments.
Automation Rule #
An Automation Rule is a rule-based mechanism that automatically triggers actions when a device matches the conditions of a Device Audience.
Actions may include:
- Assigning policies.
- Deploying apps or scripts.
- Updating configurations.
Automation Rules enable dynamic lifecycle management without manual execution.
Segment #
A Segment is a structural division within a workspace that enables granular administrative control.
Segments restrict visibility and management permissions, ensuring that administrators can only access the devices, policies, and resources assigned to their scope.
This is especially important in multi-department or multi-entity environments.
Resource #
A Resource is any deployable asset that can be assigned to devices, either manually or through policies and automation.
Resources may include:
- Applications.
- Scripts.
- Books.
- Images.
- Certificates.
- Certificate Providers.
Resources extend device functionality and enable secure configuration management.
Compliance Status #
Compliance Status indicates whether a device meets the security and configuration standards defined by assigned policies.
Devices may be marked as compliant or non-compliant depending on factors such as encryption status, passcode requirements, OS version, or security posture.
Compliance monitoring helps enforce corporate security standards.
Directory #
The Directory centralizes the management of:
- Collaborators (workspace administrators).
- Device Employees (end users).
- Access control and segmentation.
It defines who can manage devices and how devices are associated with users within the organization.