Devices
The Devices page shows all devices across your organization that have the Containment.AI extension or another supported client registered. Each device represents a browser instance or tool connected to your organization.
Viewing and managing devices requires Administrator permission.
Devices Page
Navigate to Devices in the sidebar. Each device row shows:
| Column | Description |
|---|---|
| Device | Device name, with the operating system as a sub-line |
| User | The user associated with this device |
| Type | Browser Extension, Coding Tool, API Client, or Gateway |
| Browser | Browser name (hidden on narrow screens) |
| Version | Client or extension version (hidden on narrow screens) |
| Last seen | Most recent check-in |
| Status | Active or Inactive |
| Actions | Per-device action menu |
Use the search box (Search by device, user, browser...) to narrow the list; it also matches the device type label. The list is paginated at 25 devices per page. There is no type or status filter dropdown today.
Device Status
| Status | Description | Indicator |
|---|---|---|
| Active | The device registration is enabled | Green |
| Inactive | The device registration has been deactivated | Gray |
Device status reflects whether the registration is enabled, not live connectivity — there is no Connected/Disconnected/Idle model and no heartbeat-staleness threshold. Last seen is shown so you can judge recency yourself.
Multi-Device Support
Users can have multiple devices — for example a work laptop running Chrome and another running Edge. Each device:
- Has its own device identifier
- Is tracked separately
- Shares the user's policies
- Reports independently
Device Actions
From the row action menu:
- View details - Open the device detail drawer
- View alerts - Jump to the Alerts page
The detail drawer shows Associated user, Device details (device name, OS, browser, version), Identifier, Activity (last seen, registered, created), and an Actions section with:
- Deactivate / Reactivate - Disable or re-enable the device registration (Administrator only)
- View Alerts and View user
There is no Force Refresh and no Remove Device action. Deactivating a device disables its registration rather than deleting it; reactivating restores it.
Device Security (roadmap)
Device compliance verification is a roadmap capability, not a shipped feature. The Devices surface does not perform OS-version or browser-minimum checks, and it does not read MDM enrollment or compliance state — a device record carries only its own reported name, OS, browser, version, and check-in times. "Advanced MDM posture checks" is a plan-tier capability delivered as a custom engagement; see Advanced MDM. Standard MDM force-install works today — see MDM Integration.
Device Reports and Alerts (roadmap)
Packaged device reports (coverage, version, activity) and automatic device notifications (disconnected device, outdated extension version) are not shipped. Use the Devices list and its search to review coverage and versions today; contact your account manager if device reporting is a requirement for your deployment.
Best Practices
Monitoring
- Review the device list periodically, sorting by Last seen to spot devices that have stopped checking in
- Follow up with users whose devices report older versions
Updates
- Keep the extension updated (browsers auto-update store-installed extensions)
- Use MDM to force-install and pin the extension across managed devices
Hygiene
- Deactivate device registrations that no longer belong to an active user
- Review unfamiliar device names with the associated user
Troubleshooting
Device shows Inactive
- Confirm whether the registration was deactivated deliberately
- Verify the extension is still installed and the user is signed in
- Ask the user to open the extension popup and check its status
- Reactivate the registration from the detail drawer if appropriate
Device has not been seen recently
- Check whether the user is active
- Verify the extension is installed and signed in
- Check network and firewall access to
containment.ai
Unfamiliar devices
- Review with the associated user
- Deactivate registrations the user does not recognize
- Check for shared accounts
Extension version looks old
- Confirm the browser's extension auto-update is not blocked
- Ask the user to update from the browser's extensions page
- Verify your MDM update policy is not pinning an older version
Related Topics
- Device Types - Types of devices
- Users Overview - User management
- Chrome Extension - Extension setup
- MDM Integration - Enterprise deployment