Admin UI
The Onumia admin page is the WordPress-side control center for sandbox work. Administrators use it to watch activity, decide what each role can do, tune sandbox defaults, and, with Pro, review work before it ships. Users with Onumia capabilities or a sandbox share can also open the app to reach the work they are allowed to see, but Settings stays reserved for administrators with WordPress’s standard manage_options capability.
Navigation
The admin app is organized into a small number of top-level sections. Overview gives you the current state of the sandboxes you can see, Settings is where administrator configuration lives, and Workspace appears only when Onumia Pro is installed. The Onumia header stays visible as you move between ordinary pages; inside Workspace, dedicated display controls can hide that header or switch to full-screen for distraction-free review.
By default Onumia adds itself as a top-level item in the WordPress admin menu. If that placement does not suit your site, you can relocate it beneath Tools or Settings with the onumia/admin/menu_location filter.
Overview
Overview summarizes what Onumia is doing right now. At the top, a set of headline metrics counts total sandboxes, active sandboxes, command runs, logged events, and promoted sandboxes, giving you a quick read on volume and activity. Two charts sit alongside them: one tracks command activity over time, and the other breaks down sandboxes by status. Below that, a sandbox list shows each sandbox with its status, command count, and last activity, so you can spot stale or busy work without leaving the screen.
Settings
Settings is divided into sections, currently Access and Sandbox defaults. Each section saves independently with explicit Reset and Save actions. Reset opens a confirmation dialog before it restores that section’s defaults, so you cannot wipe your configuration with a single misclick.
Access
The Access section is where you assign Onumia capabilities to WordPress roles. Each role appears as its own card, and every Onumia capability is a switch you can turn on or off for that role. Toggling a switch changes what users in that role, and any Application Passwords they create, can do through Onumia tools. It is important to understand what this does not do: granting an Onumia capability never grants ordinary WordPress admin access. The two permission systems are separate, which is exactly what lets you give a role sandbox access without handing it the keys to the rest of WordPress.
Sandbox Defaults
The Sandbox defaults section controls how new sandboxes behave. Each one can be overridden at runtime by a WordPress filter when a host needs different behavior.
| Setting | Default | What it controls |
|---|---|---|
| Default sandbox TTL | 3600 seconds | How long a new sandbox lives before it is eligible for cleanup. |
| Maximum active sandboxes per user | 50 | How many sandboxes one user may keep active at once. |
| Maximum local clone database size | 250 MB | The largest copied database payload allowed when cloning into a sandbox. |
| Inactive sandbox retention | 30 days | How long inactive sandboxes are kept before retention removes them. |
Workspace
Workspace is the review surface that ships with Onumia Pro. It pairs a left rail of workspace sessions with a sandbox list and sandbox-level modes for Browser, Merge, Share, and Tasks. You can open a sandbox preview, inspect database changes, manage sandbox sharing, and keep several review contexts side by side.
Workspace focuses on browser review, database merge staging, sandbox sharing, and promoted-sandbox inspection. The merge surface lets reviewers scan changed tables, stage rows by change group, preflight, and promote. Promoted sandboxes then expose the rows written to live, including selected rollback and explicit force handling for drifted rows.