Glossary
A flat dictionary of every term we use across the dashboard, the CLI, and the API.
Core terms#
| Field | Type | Description |
|---|---|---|
| Account | An organization or team. The container for members, billing, and resources. | |
| Workspace | A set of machines that boot, live, and die together. | |
| Machine | A virtual machine (Linux VM) running inside a workspace. | |
| Recipe | The blueprint that builds one machine from scratch (one Ansible role). | |
| Stack | A service or addon installed onto a running machine (e.g. docker-run nginx). | |
| Template | A reusable workspace shape - which recipes to combine, with which sizes. | |
| TTL | Time-to-live. After it elapses, the workspace stops automatically. |
People and access#
| Field | Type | Description |
|---|---|---|
| Profile | A single user, email-verified. | |
| Account member | A profile attached to one account, with a role. | |
| Owner / Editor / Viewer | The three workspace-level roles. | |
| Service token | A long-lived API token used by the CLI and CI. | |
| Guest link | A temporary, single-purpose URL for non-EasyEnv users. |
Assessment terms#
| Field | Type | Description |
|---|---|---|
| Test | A reusable assessment definition: workspace shape + questions + scoring rubric. | |
| Interview | One instance of a test sent to one candidate. Live or offline. | |
| Live interview | Synchronous: you and the candidate share a workspace in real time. Jitsi video, shared cursor. | |
| Offline interview | Async take-home assignment. The candidate works on their schedule and you review the replay. | |
| Question | One unit inside a test. Either a free-text question or a hands-on challenge. | |
| Challenge | A hands-on question type: a recipe with something intentionally broken that the candidate must fix. | |
| Pass condition | The check that decides whether a hands-on challenge was solved. Run on submission. | |
| Replay | The combined screen + terminal recording of an interview, with a scrub timeline. |
Why the dual naming?
Internally we built the system around the words
Interview and InterviewItem. Externally, those names confused customers, so the UI relabels them to Test and Interview. The CLI and API still use the original names.