Console
Navigation
Left navigation, command palette, and persona-aware surfaces.
Overview
Console navigation is engineered for operational speed at enterprise scale. The left navigation groups destinations by function; the top bar anchors tenant context, notifications, and account settings; the command palette provides search-driven jumps to projects, Console areas, and common actions.
Persona lenses adjust emphasis without hiding authorized destinations, QA leads see coverage and test health shortcuts; SREs see execution status and topology links; executives see reliability posture summaries; administrators see directory and policy entry points.
Power users rely on the command palette and deep links for runbooks. Less frequent users benefit from the structured left nav and Console Home quick actions.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- Console access with permissions for the areas you need to reach
- Keyboard shortcuts enabled in your browser (command palette requires no additional extension)
When to use this workflow
- Training new team members on how to reach Runs, Test Health, or Agent Console quickly
- Building on-call runbooks that specify palette queries instead of multi-click paths
- Auditing whether role assignments expose the correct Console sections
Three navigation modes
Three navigation modes
Most operators combine left navigation, command palette, and Home quick actions depending on urgency.
Step-by-step procedure
Use left navigation for sectional browsing
Expand a section group, Operate, Quality, Automation, Governance, or Platform, to reveal destinations.
Active route highlighting shows your current location; collapsed groups remember state per session.
From Console Home, select Operate → Runs to open the run list without using the project wizard.
Jump with the command palette
Press ⌘K (macOS) or Ctrl+K (Windows) anywhere in the Console to open the palette.
Type "Test Health" to jump directly to failure and flakiness analysis.
Type a project name fragment to open project detail or start a contextual action when your role permits.
Confirm tenant and notifications in the top bar
Verify organization name before destructive actions such as archiving projects or canceling shared runs.
Review notification badges for run completion, approval requests, and agent connectivity alerts.
Open profile menu for sign-out, organization switcher, or link to personal Settings.
Apply persona lens for role-appropriate emphasis
Open Settings → Preferences (or persona control on Home) and select the lens matching your primary function.
Observe how Home cards and suggested actions reorder, executive lenses de-emphasize case editing, for example.
Switch lenses when wearing multiple hats; permissions still enforce access regardless of lens.
Deep link for runbooks and integrations
Copy Console URLs from the address bar after navigating to canonical list views (Runs, Reports, Test library).
Embed links in incident tickets, Slack runbooks, or Confluence pages so responders land on the correct view.
Prefer stable list URLs over transient wizard steps when documenting procedures.
Reach Agent Console and Studio from Automation
Open Automation in the left nav, then Agent Console for cloud and endpoint execution fleet operations.
Open Zof Studio when authoring governed assets; Studio is related to but distinct from day-to-day Operate workflows.
Do not refer to Agent Console as "the Console" in customer-facing runbooks, use Zof Console for the product.
Escalate to Admin Center when navigation is blocked
If a section is missing entirely, your role likely lacks permission, request access via Admin Center → Directory → Roles.
Administrators configure role profiles; operators should not expect hidden sections to appear via persona alone.
Document required permissions in access-request templates to speed approvals.
Key concepts
- Organization scope
- All Zof Console and API operations are isolated to your authenticated tenant.
- Governed execution
- Agent output and remediation follow policy packs with human approval when configured.
Best practices
- Standardize on command palette queries in team runbooks ("⌘K → Test Health") for faster incident response
- Teach executives and PMs persona lenses early so Home remains useful without training on entire left nav
- Avoid instructing users to bookmark wizard intermediate steps, link to stable entity lists instead
- When demoing the product, narrate section names (Operate, Quality) to build shared vocabulary
Common issues
- Command palette returns no results
- Your role may lack access to the destination, or the query does not match indexed entities. Try the left nav path and confirm permissions with an administrator.
- Expected section missing from left navigation
- Permissions exclude the area. Persona lenses do not grant access, they only change emphasis. Request a role update in Admin Center.
- Wrong organization after sign-in
- Use the organization switcher in the top bar. Verify invitation acceptance if a new tenant does not appear.
Was this page helpful?