Console
Settings
Profile, notifications, appearance, and security settings.
Overview
Console Settings govern personal preferences within your organization tenant: profile details, persona lens, notification channels, display defaults, and session-related options. Settings do not replace Admin Center policies that administrators apply org-wide.
Separating personal Settings from organization administration reduces accidental policy changes during daily operations. Operators adjust how the Console feels and alerts them; administrators manage roles, integrations, and security in Admin Center.
Review Settings when onboarding to a new organization, when changing primary role (for example QA to SRE), or when notification volume becomes distracting during high-churn release weeks.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- Signed-in Console session
- Understanding of difference between personal Settings and Admin Center
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
Open Settings from the profile menu
Select your avatar or initials in the top bar and choose Settings.
Alternatively, use the command palette (⌘K) and search "Settings" when keyboard-first navigation is preferred.
Confirm organization context in the top bar before changing preferences in multi-tenant accounts.
Update profile and display preferences
Set display name and time zone so scheduled reports and run timestamps align with your locale.
Choose theme or density options when available to match accessibility needs for long review sessions.
Save changes and verify timestamps on a recent run detail page.
Configure persona lens
Select the persona that matches your primary workflow, QA, SRE, executive, compliance, or admin emphasis.
Return to Console Home to confirm cards and quick actions reordered appropriately.
Remember persona adjusts emphasis only; missing Console areas still indicate permission gaps.
Tune notification preferences
Enable or disable categories such as run completion, failure thresholds, approval requests, and agent offline alerts.
Route email notifications to your corporate address; avoid personal inboxes for audit-sensitive approvals.
Reduce noise during migration windows by temporarily lowering non-critical categories.
Review connected sessions and security options
Sign out inactive sessions when rotating roles or offboarding from a contractor engagement.
Follow your organization SSO policy, some tenants disable password changes in favor of identity provider controls.
Contact administrators for MFA or SSO issues rather than attempting workarounds in Settings.
Know when to use Admin Center instead
Navigate to Admin Center for API keys, webhooks, roles, teams, audit export, and platform configuration.
Request role changes through your internal access process; Settings cannot elevate permissions.
Document Admin Center paths in platform runbooks separate from personal preference guides.
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
- Set time zone before interpreting scheduled run or report timestamps
- Revisit persona lens when your responsibilities change teams or functions
- Keep notification categories aligned to on-call rotation, avoid alert fatigue on Home and email
- Never store API keys in personal profile fields, use Admin Center → Developer
Common issues
- Cannot find API key or role management in Settings
- Those controls live in Admin Center. Settings is personal scope only.
- Persona change did not unlock a Console section
- Request appropriate role permissions. Persona does not grant access.
Was this page helpful?