Skip to content

Operator Quick Reference

Use this page as a compact reminder after you already know the fuller workflows.

  • Home: confirm overall service health through Operations Snapshot
  • Endpoints: find machines, open endpoint details, and hand off into Open Sessions
  • Self-Healing: review pending self-healing work and open endpoint self-healing by endpoint id
  • IT Knowledge Base: browse native and imported documents or manage import sources
  • Guardrails: manage reusable guardrail templates
  • Local Assistant Policy: manage the default local assistant assignment
  • Endpoint Local Web: open locally from the endpoint tray or taskbar for enrollment recovery, Status, Logs, and Settings
  • Use Search, OS filters, and Apply on Endpoints before opening a machine.
  • Use Open Sessions from endpoint details when you need live investigation instead of static state review.
  • In the session workspace, start with a Guardrail template, then use Start Session.
  • Watch the session-state chips, Live endpoint intelligence, and Agent worklog together while a session is active.
  • Check the endpoint detail Sentinel panel before opening live sessions when the endpoint may already have self-healing context.
  • If an endpoint looks stale, check Last Seen, Sentinel status, Diagnostics, and whether live endpoint intelligence reports a stale or unavailable frame before escalating.
  • Self-Healing is the overview and endpoint handoff.
  • Escalation links open the Self-Healing Escalations queue for pending, approved, rejected, and expired escalation records.
  • Endpoint Self-Healing splits endpoint context into Sentinel, Sessions, Knowledge, and Escalations.
  • Proposal Reject records the rejection immediately. Escalation Reject still requires a reason.
  • Guardrails is the template inventory; opening a row takes you to the dedicated template editor.
  • Clone a template when you want a distinct starting point; delete requires an exact-name confirmation.
  • IT Knowledge Base splits into Documents and Import Sources.
  • Imported knowledge content is read-only inside Pharaoh.
  • Local Assistant Policy requires an execution guardrail template before the assistant can be enabled.
  • Endpoint Local Web is local-only, opens explicitly from the endpoint, shuts down after 30 minutes idle by default, and must redact secrets in status, logs, settings, exports, screenshots, and errors.
  • Create Playbooks for repeatable prompts that operators should reuse, but keep environment-specific facts in the IT Knowledge Base.
  • Confirm the current organization from the user menu before doing scoped work.
  • Use User Profile and Organization Settings when a workflow depends on the active tenant or membership context.
  • Use Billing when setup, payment, provider credential, subscription, or spend-limit state blocks billable work.
  • Expect admin-only surfaces to warn clearly when your current role is insufficient.