Administration
Team management
Team collaboration workflows.
Overview
Team management covers collaboration workflows, ownership of applications and tests, assignment routing, and handoffs between QA and engineering. Teams map to Console visibility scopes and API resource filters.
Administrators structure teams to mirror organizational boundaries while avoiding excessive permission fragmentation.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Create teams
Admin Center → Teams → Create with name and description.
Assign team lead for assignment routing.
Link applications
Map applications to owning team for scoped Runs and Reports views.
Invite members
Admin Center → Users → Invite with role and team membership.
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
- Validate changes in staging before applying release gates to production.
- Include run IDs and timestamps when escalating issues to support or auditors.
- Align internal runbook terminology with Zof Console UI labels for clarity.
Was this page helpful?
