Device enrollment is the first step in bringing your organization’s devices under centralized management in Trio. Whether you manage laptops, desktops, tablets, or phones, enrollment ensures that every device is identified, authenticated, and configured according to your company’s security and compliance standards.
Once a device is enrolled, administrators can apply policies, push software, enforce security rules, and monitor compliance — all from a single dashboard.
Why Enrollment Matters
Enrollment connects a device to Trio’s management framework, allowing your IT team to:
Automate setup — Instantly deploy apps, Wi-Fi settings, certificates, and restrictions.
Secure company data — Enforce passcodes, encryption, and compliance policies.
Support hybrid ownership — Manage both corporate and personal (BYOD) devices without mixing personal data.
Simplify oversight — View device health, status, and activity from the Fleet dashboard.
Whether the device belongs to the company or an employee, enrollment ensures the right balance between control and privacy.
Enrollment Overview
From the Fleet → Enrollment section, administrators can:
Choose a platform (Android, iOS, macOS, Windows, iPadOS, Linux).
View all supported enrollment methods for that platform.
Track the number of enrolled devices per OS in the Enrollment Summary.
Use Quick Enrollment to register devices instantly with a pairing or enrollment code.
Manage all generated tokens under Saved Enrollment Tokens, including their expiry dates and assigned device groups.
Trio supports both manual and automated enrollment methods, letting you scale from a single device to thousands.
Enrollment Methods
Trio provides multiple enrollment options tailored to your organization’s setup, control level, and device type:
Enrollment Type | Description | Typical Use Case |
Silent Enrollment (COD) | Automates bulk deployment without user interaction using a PowerShell or shell script. | Ideal for IT teams provisioning company laptops in bulk. |
Pairing Code (COD) | Uses a one-time secure code for quick corporate enrollment. | Suitable for small or medium deployments with admin guidance. |
SSO Enrollment (COD) | Leverages your company’s SSO provider for secure authentication. | Best for organizations using Google Workspace, Microsoft Entra, or similar IdPs. |
Credentials Enrollment (BYOD) | Lets employees enroll personal devices using a username and password. | Enables light management for user-owned devices. |
Each method determines the level of control, privacy, and automation available during setup.
Quick Enrollment and Token Management
The Quick Enrollment panel simplifies adding new devices:
Copy or share an auto-generated Enrollment Code.
Choose the default method (e.g., macOS Pairing Code).
Decide where enrolled devices should go — under the organization or a specific Device Group.
Manage Token Expiration to ensure codes remain secure and valid only for a limited period.
Admins can also renew or deactivate tokens anytime to maintain security hygiene.
Assigning Enrollment Defaults
From Enrollment Settings, you can define:
Default Device Group: Automatically group new devices by platform, department, or location.
Token Lifetime: Set how long each enrollment token remains valid (e.g., 30 days).
These controls ensure that all new devices automatically align with your organization’s structure and policies.
After Enrollment
Once devices appear in the Recent Enrollments list, they immediately begin syncing with your organization’s Trio configuration.
Admins can then:
Assign policies under Policy Management
Deploy apps through Software Management
Configure restrictions and security features
Monitor device activity and compliance under Fleet and Security sections
Summary
Trio’s enrollment system is designed for flexibility — allowing IT teams to manage a growing fleet of devices with minimal friction. From automated scripts for large-scale rollouts to secure SSO logins for corporate users, every method ensures your organization’s devices are protected, compliant, and ready for work from day one.



