The admin UI at a glance
Vox builds its admin UI from your model. Every entity type gets lists, forms, relations, history and, where you opt in, drafts and releases, without a bespoke UI. This page is an overview for editors, product owners and anyone who evaluates Vox. Developers can extend the admin UI with plugins.

Home
The home screen shows what needs attention: drafts with unpublished changes, scheduled publications, open content releases, entities whose assessments fail or warn, and subscriptions that are failing or paused.
Lists
- Views: a table, cards, a gallery for images, or a tree for hierarchies such as categories. Plugins can add views of their own.
- Search and filters, including filters on relations, eg the products of a category and its subcategories.
- Status of each entity: published, draft changes, scheduled, or in conflict.
- Bulk changes: select entities, or everything that matches the filters, and export them to Excel. Edit the workbook and import it again, with a preview before anything is saved. See Edit in bulk with Excel.

An entity

- Forms from the model. Fields are grouped and labelled from the editor metadata, with rich text, choices, units and validation as you type. Imported and calculated fields are shown but can't be edited, so editors see where every value comes from.
- Values per language, market and channel. Edit the value of a context, see whether it's set there, falls back or uses the invariant value, and ask the admin to explain why a value is what it is. See Languages, markets and channels and Variations.
- Relations in their own tab, eg the products of a category or the accessories of a product.
- Assessments show what fails or needs attention, next to the field it concerns, eg a missing image for Norway.
- Assets such as images, with a focal point for cropping.
- History: every version, what changed and who changed it, and restoring an earlier version. See History and audit.



Drafts, releases and preview
For entity types that use authoring:
- Drafts are saved automatically and don't change what's published. Publish now or schedule it, also with an end date. See Drafts and publishing.
- Content releases collect changes to many entities, eg a campaign with its products and pages, and publish them together. See Content releases.
- Conflicts between a draft and what has been published since are resolved field by field.
- Visual preview opens your own site inside the admin, in the draft or release you're working on. Click content on the page to edit it in a panel beside it. See Visual preview.

Contexts and experiments
Markets, channels, languages and experiments are entities too. Their selection criteria, eg the path of a language or the visitors of an experiment variant, can be edited as conditions or as JSON and tested in the admin. A winning variant is promoted into the published content with one click. See Run an A/B test.
Administration
- Subscriptions: set up and follow the deliveries of changes to other systems. See Events and subscriptions.
- Users, roles and API clients are managed like other entities, with permissions down to fields, languages and channels. See Users, roles and permissions.