Before you begin
- An Enterprise plan or above. The Integrations hub is locked below Enterprise
- The Administrator role in Atlas to connect, configure or disconnect a connector. Integrations appears under Administration only for administrators
- A tenant selected in the tenant picker. Credentials are stored encrypted per tenant, so each tenant you manage connects its own account
- A Level API key
What you can do
- See every Level device with its group, operating system, online status and last seen, and jump from a device to the matching session host in Atlas.
- Track online and offline devices at a glance.
- List your Level groups with their descriptions and device counts.
- Sync Level devices into Atlas Vault as assets, every hour.
- Read Level devices and groups from your own automation with an Atlas API key.
Step 1: Create an API key in Level
In Level, go to Settings → API Keys, create a key for Atlas and copy it. Level is cloud-hosted, so there is no server address to note.
Step 2: Connect in Atlas
Once connected, the card shows Manage, which opens the Level page, and Disconnect. The key is stored encrypted.
- Select the tenant in the tenant picker.
- Go to Administration → Integrations and click Connect on the Level card.
- Paste the API Key and click Connect. Atlas reads your Level groups with the key before saving anything; if Level rejects it, nothing is stored.
What you see
- Overview: Total Devices, Online, Offline and Groups, and the device online ratio.
- Devices: name, group, OS, status and last seen. Search by name, OS or group, sort any column, and click the AVD link to open the matching session host. A device links when its name matches a VM name exactly, or when its short name matches exactly one VM.
- Groups: each group's name, description and number of devices.
Atlas reads Level live each time you open a tab or click Refresh; the page does not copy your Level data into Atlas. Asset sync into Atlas Vault is separate and runs only if you set it up.
Sync devices into Atlas Vault
With Level connected, open Atlas Vault → Assets → RMM & PSA sync and click Add sync: pick Level as the source, a device group, and the asset template each device becomes, then map fields. Atlas then creates and updates a Vault asset for each device every hour, or when you click Run now. Fields you can map include the device's host name, status, OS, group and notes. Values someone edits by hand in Vault are never overwritten. Setting up a sync needs a Vault admin and at least one asset template.
Use it from your own tools
An Atlas API key with the integration.level.read scope can list devices at GET /api/integration/level/devices and groups at GET /api/integration/level/groups. There is no write scope for Level. See API Access for how keys are issued.
What the integration does not do
- It is read-only. It does not change anything in Level.
- It does not show Level alerts or monitors, and there is nothing to acknowledge or resolve.
- It does not run automations or scripts, open a remote session, or patch. Use Level for those, or Atlas Reach.
- It does not create tickets.
- It connects one Level account per Atlas tenant.
- Credentials cannot be edited in place: disconnect and connect again with the new key.
- Atlas Advisor can tell you whether Level is connected, but does not answer questions about devices.
GCC High tenants
On a tenant or deployment in Azure Government (GCC High), calls to Level are blocked by default, because they can carry VM, host-pool and tenant names to a service outside the Government boundary. Connect fails with an Azure Government (GCC High) egress boundary message and nothing is stored, and pages that read from Level stay empty. The operator who runs your Atlas deployment can approve Level as a destination that is allowed to receive that data; once approved, the connector works normally. Running in Azure Government does not by itself make a third-party integration GCC High or CMMC compliant.
Disconnecting
Click Disconnect on the card and confirm. Atlas deletes its stored copy of the API key and pauses any Atlas Vault asset sync from Level. Assets already in Vault stay; turn the sync back on after you reconnect. Nothing changes in Level. Delete the key in Level too if you no longer need it.
Troubleshooting
- Level rejected the supplied credentials: the key is wrong or has been deleted. Create a new one and connect again.
- Level is temporarily rate limiting requests — try again shortly: wait a minute and try again.
- Could not connect to Level: Level could not be reached. Try again shortly.
- Something went wrong on the Devices or Groups tab: click Retry. If it keeps failing, check the key still exists in Level.
- Asset sync reports the integration is not configured: Level was disconnected. Connect it again, then turn the sync back on.