Workbench is a specialist area for authorized project users preparing derived outputs and inspection records. It is available only when the active client has Workbench enabled and the signed-in user has the required viewer/workspace access. The sidebar Workbench link opens Orthomosaic Workbench. The bare /workbench/ route redirects to MACP when MACP is also enabled for the active client; otherwise it opens Pano Packages. If the feature is not enabled, the route is deliberately not exposed.
Every Workbench list respects the active workspace client. When the workspace is not locked, use the Client and Project filters and select Apply. Select Reset to remove those filters. The lists are operational queues: their status badges and missing-data messages tell you whether to set up, create, inspect, download, or correct a row.
Choose the right surface
- Orthomosaic Workbench is for model-based orthomosaic setup, generation status, and opening the generated result.
- Pano Packages is for desktop Pano2VR package preparation, package creation, opening a ready Pano output, and downloading desktop or rendered packages.
- MACP Workbench is for inspection records, evidence, and MACP database export. It requires both Workbench and MACP to be enabled for the selected client.
Use the row’s project, facility, and file ID to confirm scope before starting an action. A row can be visible because it has video, model, or pipeline state, while still be missing the derived artifact required for the task. Correct missing setup rather than assuming a processing status will create it automatically.
Access and common problems
Switch to the client that owns the project before opening a direct Workbench URL. If a tab is disabled or a route returns no page, first confirm the active workspace and the client’s feature entitlement. MACP is intentionally disabled in Orthomosaic and Pano views for a client without MACP access. Workbench can show only projects the user is allowed to reach, so an absent project may be an access or workspace-selection issue rather than a missing file.
Use the feature-specific guides for the actual operation. Do not use a Pano package in place of an orthomosaic deliverable, or a MACP export in place of a viewer download; each output has a separate record, readiness state, and delivery path.
Access to a Workbench list does not grant every action. Saving orthomosaic setup and starting orthomosaic generation require an authorized TREKK staff or developer account. Pano and MACP actions also depend on the selected file, enabled features, and your project permissions.