Skip to main content
Two Platform pages under Agents govern Omni Desktop: Devices and Desktop policy. They appear once Omni Desktop is available for your organization. Who may view them, change the policy and revoke a computer follows your access policies.

Devices

Devices lists every computer signed in to Omni Desktop, with its system (macOS or Linux), member, app version and whether it is Online now. Revoke disconnects a computer at once. Its owner is signed out, agents lose access to its folders, and the app shows Mac removed. Nothing on the computer is deleted. Signing in again adds it as a new computer. A member who leaves the organization has all their computers revoked. One member can have up to 20 computers connected at a time.
Devices page listing three computers, each with its system and version, member, app version, last seen and Online or Offline status

Platform > Agents > Devices. Shown with sample data.

Desktop policy

Desktop policy sets the most Omni Desktop may do. The Every member row is the organization default and opens a panel with every setting below. A new organization starts with every permission open and Limit agents in browsers, terminals and banking apps off. Turn off what you want to keep closed, and turn the limit on if you need it. Members can turn any of these off for their own computer, never on beyond what you set. See Your switches.
Every member panel with switches for Omni Desktop, Shell, Shell can reach the network, App automation, Move to cloud, Bring work back, Browser control, Computer control, Limit agents in browsers, terminals and banking apps, and Keep screenshots, Local files set to Read and write, and When the computer is offline set to Ask

Every member: the organization default for a new organization. Shown with sample data.

A saved change reaches every connected computer at once, with no restart. If xpander cannot read a member’s policy, for example during an outage, it treats every switch as off until it can.

Group overrides

Group overrides give a group’s members more than the default. Choose Add group override, pick the group, set its values and Save. Anything the default already turns on shows as on and locked. A member in several groups gets the most any of their groups allows. When their groups pick different offline behaviors, the app asks. Remove override returns the group to the default.
Desktop policy page with Add group override, an Every member row and an Engineering group override row, each with a summary of its settings and its status

Platform > Agents > Desktop policy: the organization default and a group override. Shown with sample data.

What is recorded

The audit log records:
  • Every sign-in to the app.
  • Every file or shell action an agent takes: the action, path, outcome and duration, never file content.
  • Every screen action: where it landed, never what was typed or seen. The audit log keeps no screenshots. The conversation keeps them while Keep screenshots is on.
  • Every site the Omni browser opened (the site only).
  • Every move to the cloud or back, and every schedule linked to or unlinked from a computer.
Agent actions on a computer (files, shell, screen and browser) are kept 90 days. Sign-ins, computers added or revoked, moves, schedule links and policy changes are kept 400 days. To keep them longer, export them as CSV or JSON from the audit log, or stream them to your own store with Log destinations.

Hybrid and Air-Gapped

Omni Desktop connects to whichever xpander its address points at (first run). Members’ computers must reach your install over HTTPS, for example on your network or VPN. An Air-Gapped install needs xpander v2026.11.03 (xpander-airgap chart 0.17.26) or later for Omni Desktop: older installs do not give the app the address of their AI Gateway. Upgrade an older install first.

Deploy to every Mac with MDM

Two parts, both from your MDM (Jamf, Intune, Kandji or another):

The installer package

Download xpander-latest-arm64.pkg (Apple silicon) and xpander-latest-x64.pkg (Intel) from https://<your xpander>/desktop/. Both are signed “Developer ID Installer: Xpander Inc. (76H3VNMG43)”, notarized and stapled, and install /Applications/xpander.ai.app, which macOS shows as Omni. Each package is built for one architecture, so scope each one to its Macs, for example with a smart group on the architecture. The installed app updates itself from the same address.

The address profile

Deploy a configuration profile as a device (system) profile. With it installed, the app opens on that address, shows Set by your organization, and members cannot change it. A profile that a person opens themselves is not managed, and the app ignores it.
The download page has a sample profile, xpander.mobileconfig, with this payload and a managed login item, so Omni stays allowed under System Settings > General > Login Items. Replace https://xpander.example.com in it with your address. To check a Mac, run defaults read "/Library/Managed Preferences/ai.xpander.desktop" ServerUrl.
Welcome to Omni screen with the xpander URL field locked to xpander.acme.internal and the note Set by your organization

The first run on a Mac whose address is set by MDM. Shown with sample data.