The sign-in page asks for the user name first, then the second factor (a security key or an authenticator code), then the password. A security key completes the sign-in on its own, and a user without a second factor can be guided to set one up before getting a session.

Fleet overview with drill-down tiles: node status, agent versions, operating systems, desktop environments, node groups and policy counts link straight to pre-filtered lists. The sidebar is grouped into Fleet, Policy and System.

The whole console is theme-aware: dark mode and high contrast come from PatternFly design tokens and are switched from the masthead.

Browse and manage policies with search and filters by type, status and bindings. Sixteen policy types, each with its mark; policies are released, archived, exported or imported from the list.

A four-step wizard: pick the type from tiles grouped into Browsers, Desktop and System, name it, configure it in the same editor used later, and review. The success screen offers to release the policy or assign it to a node group right away.

Policies and their bindings travel as YAML bundles, for backups, migration between servers and version control. An import always runs as a dry run first and shows what would be created, updated, skipped or rejected before anything is written.

The complete Firefox policy catalogue in a tree editor organised by category: updates, privacy and telemetry, network, security and more. Released policies show a read-only view with the lifecycle actions in the header.

Mozilla Thunderbird with its full policy catalogue. The agent writes the managed policies.json for package and Flatpak installations alike.

Homepage and startup, browser UI, extensions, Safe Browsing, network and proxy, and privacy settings for Google Chrome and Chromium, in the same tree editor.

Microsoft Edge for Business on Linux. The agent writes bor_managed.json into each Edge managed-policy directory and removes it when the last bound policy goes away.

Any KDE setting from a built-in catalogue: Kiosk action restrictions, System Settings lockdown, screen lock, power, appearance, applications and more, each entry enforced or left as a default. Policies can scope to Unix groups and deploy a wallpaper and panel layout.

dconf key-value entries the agent writes to the managed GNOME desktop. Each entry can be locked so users cannot override it.

Polkit rules from a structured form: exact action IDs, action prefixes, subject filters and variable conditions. Bor generates and deploys the JavaScript rule.

firewalld zones on enrolled nodes: services, ports, forward ports, rich rules, masquerade and the zone target. The agent validates with firewall-cmd --check-config before reloading, and the zone files are tamper-protected.

systemd units per node: enablement, activity, timer schedules and service overrides through drop-ins, plus scheduled tasks deployed as bor- units. Unit names come from what the nodes report.

Enforcement mode, booleans, permissive exceptions, modules, file contexts and login mappings for Fedora, RHEL and SLES 16 nodes. Nodes without SELinux can be treated as non-compliant or prepared for the next reboot.

AppArmor on Ubuntu, Debian and SLES 15: the service state, the user namespace restriction, profile modes, custom profiles, local overrides and home directory roots.

What a node installs on its own, on which schedule, which packages are held back, and the reboot rule, driving the distribution's own update engine. Limits turn stale security updates and pending reboots into compliance items.

When selected users and groups may use a desktop session: weekly schedules per rule, lock or log off when a window ends, and optional PAM enforcement of fresh logins.

APT, DNF and Zypper repositories with GPG keys, one-click import of Ubuntu PPAs, openSUSE 1-Click files and Fedora COPR, and packages with a desired state and an optional version pin.

Enter a ppa:owner/name address and pick an Ubuntu codename; the server fetches the repository URI and signing key from Launchpad.

Upload a .ymp file and the server fills in repositories and packages in one step, skipping entries that are already present.

Flatpak remotes and applications, with the server-side catalogue: Flathub is indexed out of the box, and the editor searches it to add applications as Present, Latest or Absent.

LUKS2 full-disk encryption for the fleet: the volumes in scope, TPM 2.0 unlocking with a PCR profile, Tang network unlocking with pinned keys, and the escrowed recovery key with its rotation interval.

Enrolled desktops with status, node group, operating system, last-seen time, agent version and notes. Lists are filtered and sorted server-side and export as CSV; the MAC and Updates columns show what each node runs.

The details panel of a node: identity, operating system and desktop, agent version, groups and last seen time, followed by its units, mandatory access control, software updates and disk encryption sections.

Every server serves its own signed agent packages. Pick the platform and architecture and get one copy-paste script that trusts the server CA, sets up the repository, installs the agent and enrolls it into a node group with a one-time token.

Nodes are organised into groups, and policies are bound to groups. One-time enrollment tokens are issued per group and expire after five minutes.

Which policy applies to which group, with an enabled switch, a priority that decides between policies of the same type, and the number of affected nodes.

Per node and per policy, what the agent reported after the last enforcement: compliant, non-compliant, inapplicable or error, with the message and every setting's item. Items that correspond to a CIS benchmark control carry its number.

The fleet's LUKS volumes with their protectors, escrow state and pending rotations, searchable by host name, LUKS UUID or key id, the way a help-desk call provides them.

Revealing a key needs its own permission, a reason or ticket number, the operator's password and an authenticator code, and is audited every time.

Every administrative action with timestamp, actor, action, resource and source address. Searchable, filterable, exportable as CSV or JSON, and forwardable to a SIEM in CEF or OCSF.

Local and LDAP accounts with their source and state, enabled, disabled or deleted with a type-to-confirm dialog.

Built-in roles from Auditor to Super Admin and custom roles with per-action permissions. Assigning a role is guarded against privilege escalation.

Groups of console users that carry roles; members receive the group's permissions, and membership changes are guarded like direct role assignments.

Require a second factor for every sign-in, let users set one up while signing in, and choose the TOTP algorithm.

Desktop notifications the agent shows when a policy changes, with a cooldown and editable messages.

The application catalogue behind Flatpak policies: Flathub indexed from its AppStream feed, more repositories from a .flatpakrepo URL, and uploads for air-gapped servers.

Registered Tang servers with their verified signing keys, per-key bound-volume counts and a flag when a server advertises a new key after a rotation.

Users secure their account with an authenticator app or a security key over WebAuthn (YubiKey, Bitwarden, 1Password and similar).

TOTP enrollment with a QR code for any authenticator app, the manual-entry secret as a fallback, and backup codes to acknowledge on completion.

The agent tells the user on the desktop when a policy was updated and which applications to restart for the change to take effect.
