The terms used across the HyperView knowledge base, grouped by subject. For the same terms in alphabetical order, see the Glossary.

System: a machine registered with your console. It appears when the HyperView Server is installed, or when someone runs DesktopAgent from a support link.

Hostname: the name the machine reports for itself. It isn't unique: two machines can report the same one, and a cloned VM usually does.

Alias: a name you give the system in the console. See Organize your systems.

Fingerprint: how a system proves it's the same machine after a restart. When it stops matching (after cloning or re-imaging, for example), the system registers again, which is where duplicate entries come from.

Heartbeat: the regular check-in from the HyperView Server. The status dot is green while it's current.

System status: ACTIVE, INACTIVE, BLOCKED, UNREGISTERED or CONFLICTED.

System type: SERVER for an installed HyperView Server, DESKTOP_AGENT for a temporary remote support system.

Folder: the main way to group systems. A system is in at most one folder. Folders drive filtering, access and usage reporting.

Tag: a label on a system, either name:value or just name. A system can have many.

Owner: the user responsible for a system. Drives the My systems view.

Installation key: the key used to install the HyperView Server. It decides the folder and owner a new system gets, which version installs, and the server settings it runs with. See Installation keys.

Installation key settings: server behaviour the key applies to every system installed with it, such as audio mode and the automation action log.

Default share: access created automatically when a system registers, so someone can connect straight away.

Session: a person or an automated caller connected to a system. What you're billed for.

Connection mode: how a session behaves: Connect, View only, Admin (shared), Admin (stealth) or Group share.

Share link: a URL that gives someone a session in a set mode without a console login. See Act on a system.

DesktopAgent: the small, temporary HyperView Server used for remote support. The person you're helping downloads it; it deletes itself when the session ends.

Session state: what the desktop is doing: logged_in, locked, logged_out, screensaver, switching_user or unknown. Automation usually needs logged_in.

Venue: a relay that joins the console and a system. A private venue is one your account runs itself.

API key: the credential a script or agent signs in with. Its access rules decide which systems it can reach.

Access rule: a pairing on an API key of a set of systems and the capability policy that applies to them. Rules are checked top to bottom and the first match wins. A key with no rules reaches nothing.

Permission: what an API key may do in the console, such as use automation. See API keys and their permissions.

Capability: one thing a session may do on a system: take a screenshot, run a command, write a file. There are 18; 6 are marked risky. See Automation capabilities.

Capability policy: a named set of choices, one per capability: Allowed, Guardian, Human approval or Denied. Three come built in: Read only, Approval required and Full access.

Approval: a person's decision to let a key use a gated capability on a system. It applies to that key on that system, not just to one session.

Guardian: an AI reviewer for capabilities set to Guardian. It reads the request and approves it, denies it, or passes it to a person.

Mission: the instructions Guardian judges requests against. Each version is recorded on every decision.

Skill: a file that tells an AI agent the hv CLI exists and how to use it.

Automation Enabled: the account-wide off switch. When it's off, no automation session can start.