Core Concepts
Human authorization
Overview
Explicit approver action required before remediation apply steps execute.
In the Zof Console: Remediation → Approvals queue. This concept appears across API responses, Console navigation, and reliability workflows. Understanding it is essential for consistent communication between QA, platform, and SRE teams.
Who should read this
- New users, technical writers, and integration engineers aligning internal documentation with Zof terminology.
Prerequisites
- Basic familiarity with Zof Console navigation
- Organization member access
When to use this workflow
- Onboarding engineers unfamiliar with Zof terminology
- Writing internal runbooks that align with Console UI labels
- Mapping customer CMDB or ITSM fields to Zof entities
Step-by-step procedure
Locate in Console
Navigate to Remediation → Approvals queue.
Use the command palette (⌘K or Ctrl+K) to search for related screens by name.
Use in workflows
Reference this entity when configuring runs, policies, integrations, or reports.
Follow related documentation links below for step-by-step operational procedures.
Verify understanding
Confirm your team uses the same term in Jira/Linear tickets and internal docs.
Escalate terminology questions to your Zof administrator or account team.
Key concepts
- Human authorization
- Explicit approver action required before remediation apply steps execute.
- Where to find it
- Remediation → Approvals queue
Best practices
- Match Console UI labels in internal documentation for reduced onboarding friction
- Link requirement and test IDs when traceability is required for audits
- Do not conflate similar terms (e.g., test run vs test result vs test case)
Was this page helpful?
