Features

Team Permissions and Two-Person Approval

Define who may see or change a site, host, group or machine—and require a second person for sensitive work.

In practice

What VMBook implements

Scoped grants, exceptions, expiry, freeze controls and signed multi-site synchronization are implemented in the current source. This capability is kept inspectable: VMBook shows the machine or image state involved and leaves the underlying QEMU operation visible.

Real-world environment related to Team Permissions and Two-Person Approval

Rights follow infrastructure boundaries

Grants can be limited to a site, host, machine group or individual machine. Explicit exceptions and expiry make temporary duties possible without turning every operator into a fleet administrator.

Dual control is not two-factor authentication

TOTP helps prove one person’s identity. Two-person approval requires a different authorized person to agree to a sensitive action. VMBook keeps those controls separate and records the resulting decision.

Current sign-in status

Password and password-plus-TOTP paths are active. Passkey/WebAuthn and USB FIDO2 key paths are represented in the design but are not ready in the current build; they must not be treated as available authentication methods.

VMBook product screen related to Team Permissions and Two-Person Approval

Evaluate it

Next step for Team Permissions and Two-Person Approval

Review the tested systems for evidence related to Team Permissions and Two-Person Approval, then use the free build in an isolated environment with copies of the images involved in your test.

Download VMBook free Read the technical documentation