Getting Started
Create an account
Register and authenticate to the Zof Console.
Overview
Access to the Zof Console begins with account registration and authentication. Organizations typically enforce corporate email domains, SSO via Google or GitHub OAuth, or email one-time passcode (OTP) verification depending on admin configuration.
After authentication, you are associated with an organization through team membership, either by creating a new organization during onboarding or accepting an administrator invitation.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- Valid corporate email address (recommended for enterprise tenant association)
- Organization invitation link (if joining an existing tenant)
- Modern browser (Chrome, Firefox, Safari, or Edge current version)
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
Navigate to registration
Open the Zof signup page from your invitation email or your organization signup URL.
If your company uses SSO exclusively, use Sign in with Google or GitHub as directed by IT.
Complete identity verification
For email OTP: enter your address, retrieve the code from your inbox, and enter it within the validity window.
For OAuth: authorize Zof with the identity provider; ensure you use your corporate account if required.
Verify email if required
Some organizations require email verification before Console access.
Check spam filters if the verification message does not arrive within a few minutes.
Land on Console Home or onboarding
New organizations may enter the onboarding wizard (organization, applications, integrations).
Invited users typically land on Console Home with team-scoped visibility.
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.
Common issues
- OTP not received
- Retry after 60 seconds; verify email spelling; contact admin if corporate mail filtering blocks transactional email.
- Wrong organization after login
- Confirm you used the correct email; admin may need to add you to the intended team.
- SSO redirect errors
- Verify OAuth app is allowlisted by IT; try email OTP if SSO is misconfigured.
Was this page helpful?
