Guide
Outcome-led guides
Decision frameworks and workflow education with goal, role, depth, and source links.
Owner
Content governance
Reviewed
Per resource
Does not replace Product Documentation, and is not legal advice.
Resource Center
Find the current
ZoikoTime
guidance your
task requires
Search and browse current onboarding, help, documentation, learning, developer, proof, and release resources by task, role, product area, authority, and applicability.
Start from the task, not the taxonomy
Nine high-frequency jobs, each routing to the single source that governs it. No search required.
Get started
Role-based first actions, prerequisites, setup, and verification.
Getting Started →
Solve a problem
Troubleshooting, known states, support, and recovery.
Help Center →
Understand product behaviour
Current fields, states, workflows, permissions, and limitations.
Product Documentation →
See what changed
Verified shipped changes, applicability, and required action.
Release Notes →
Learn a concept or workflow
Guides and tutorials with applicability and source visible.
Learn family →
Build or integrate
Current development guidance, contracts, and integration options.
Development Documentation →
Review trust and governance
Security, privacy, human authority, accessibility, and status.
Trust & Governance →
Evaluate enterprise deployment
Administration, identity, support, and procurement.
Enterprise →
Compare commercial options
Current plans, trial, and terms.
Pricing — never duplicated here →
How these resources are governed
Every record exposes enough metadata to judge whether it applies to you — before you act on it.
Status
Current, changed, corrected, restricted summary, or superseded. Never a vague "latest" badge.
Authority
What this source governs — behaviour, troubleshooting, change, learning, evidence, or developer contract.
Owner
The accountable team or role. Personal names only where governance requires them.
Reviewed
The precise date dimension that matters — reviewed, verified, effective, or corrected.
Applicability
Version, plan, region, integration, or configuration — only where verified and relevant.
Limitations
The boundary of what the resource covers, or a "review applicability" signal.
Date semantics are not interchangeable
Published, Effective, Updated, Reviewed, Verified, Corrected, and Superseded mean different things and are never collapsed into a single “Updated” stamp. A document reviewed last week and a document changed last week are different facts, and a reader deciding whether to trust guidance needs to know which one they are looking at.
Choose by role
Role is explicitly selected, never inferred from your browsing. Selecting one filters the directory; it does not create a profile.
Workers
Own-record visibility, correction, and support.
Reviewers & managers
Review queues, decisions, and separation of duties.
Administrators & IT
Configuration, identity, access, and integrations.
Developers
Development guidance and current technical contracts.
Security, privacy & legal
Governance evidence and worker-rights doctrine.
Procurement & leadership
Enterprise readiness, support model, and commercial terms.
Choose by stage
Contextual next steps by declared stage — and a demo request never substitutes for content that should exist.
Evaluating
Product overview, Trust Center, Enterprise readiness, Pricing. Evidence first, conversation second.
Implementing
Getting Started, Product Documentation, Administration & Policy, Development Documentation.
Operating
Help Center, Release Notes, System Status, Enterprise Support. Support intent is never diverted to sales.
Three resource families
Learn, Use, and Build & Stay Updated. Each destination states what it governs — and what it defers to.
Learn
Video tutorial
Task demonstrations
Version-aware task walkthroughs with captions, transcript, duration, and prerequisites.
Owner
Learning
Verified
Per resource
Supplemental learning. Documentation remains the authority, and product data shown is synthetic.
Webinars & events
Governed live and on-demand sessions
Date, time, timezone, status, format, speaker, and accessibility provision.
Owner
Learning
Status
Per registry
No fictitious event, speaker, capacity, or certificate claim. Sessions appear only when current.
Customer Stories and Blog & Insights are absent from this family. Approved customer evidence and a separate editorial publishing route are not currently registry-approved, and an empty category or a coming-soon card would be content-roadmap theatre.
Use ZoikoTime
Highest authority
Product Documentation
Exact concepts, tasks, fields, states, permissions, limitations, and recovery.
Governs
Current product behaviour
Owner
Product docs
The authority for behaviour. Other resources defer to it, including this page.
Support authority
Help Center
Troubleshooting, known states, recovery, and safe escalation.
Governs
Troubleshooting
Owner
Support
Support intent is never diverted to a sales route.
Onboarding
Getting Started
Role-based first actions and how to verify you reached first value.
Governs
Onboarding sequence
Owner
Onboarding
Defers to Documentation on product behaviour.
Build & Stay Updated
Development
Development Documentation
Technical architecture, patterns, and security, testing, and production guidance.
Discloses
Version, owner, review date, prerequisites
No invented endpoints, SDKs, environments, or limits.
Release authority
Release Notes
The authoritative chronological record of verified shipped changes.
Discloses
Date, version, state, applicability, action
No roadmap, and no marketing benefit inflation.
Integration directory
Verified integrations
Provider, connection state, capability scope, and support lifecycle where verified.
Discloses
Provider identity and rights, region and plan where verified
No invented integration, provider, or logo.
Current resource directory
Registry-driven. A record appears here only when its route, content, index, accessibility, claim, rights, and QA states are all publishable — so this list is a consequence of governance, not an editorial choice.
Resource typeAudienceProduct areaAuthorityApplicabilityStatusOwnerLast reviewed
| Resource | Type & authority | Audience | Date | Status |
|---|---|---|---|---|
Product Documentation Behaviour, fields, states, permissions | Documentation · governs behaviour | All roles | Reviewed 04 Jul 2026 | Current |
Help Center Troubleshooting and escalation | Support · governs troubleshooting | Customers | Reviewed 11 Jul 2026 | Current |
Getting Started Role-based onboarding | Onboarding | New users, admins | Reviewed 28 Jun 2026 | Current |
Release Notes Verified shipped changes | Release · governs change | Customers, admins, developers | Published continuously | Current |
Development Documentation Architecture and patterns | Developer guidance | Developers, IT | Reviewed 20 Jun 2026 | Current |
Trust Center Governance evidence entry point | Evidence · governs assurance | Security, privacy, legal | Reviewed 01 Jul 2026 | Current |
Integration Directory Verified providers only | Integration discovery | IT, admins | Verified 28 Jun 2026 | Current |
Reviewer correction guide Superseded by Documentation section | Guide | Reviewers | Superseded 04 Jul 2026 | Superseded — redirected |
Legacy integration setup article Review overdue, risk assessed | Guide | IT | Reviewed 14 Nov 2025 | Removed from discovery |
Product Documentation
Behaviour, fields, states, permissions
Type & authority
Documentation · governs behaviour
Audience
All roles
Date
Reviewed 04 Jul 2026
Status
Current
Help Center
Troubleshooting and escalation
Type & authority
Support · governs troubleshooting
Audience
Customers
Date
Reviewed 11 Jul 2026
Status
Current
Getting Started
Role-based onboarding
Type & authority
Onboarding
Audience
New users, admins
Date
Reviewed 28 Jun 2026
Status
Current
Release Notes
Verified shipped changes
Type & authority
Release · governs change
Audience
Customers, admins, developers
Date
Published continuously
Status
Current
Development Documentation
Architecture and patterns
Type & authority
Developer guidance
Audience
Developers, IT
Date
Reviewed 20 Jun 2026
Status
Current
Trust Center
Governance evidence entry point
Type & authority
Evidence · governs assurance
Audience
Security, privacy, legal
Date
Reviewed 01 Jul 2026
Status
Current
Integration Directory
Verified providers only
Type & authority
Integration discovery
Audience
IT, admins
Date
Verified 28 Jun 2026
Status
Current
Reviewer correction guide
Superseded by Documentation section
Type & authority
Guide
Audience
Reviewers
Date
Superseded 04 Jul 2026
Status
Superseded — redirected
Legacy integration setup article
Review overdue, risk assessed
Type & authority
Guide
Audience
IT
Date
Reviewed 14 Nov 2025
Status
Removed from discovery
Illustrative of the registry contract. Superseded and withdrawn records are excluded from current listings, schema, sitemap, and counts.
The last row is the important one: stale guidance is removed from authoritative discovery rather than kept to avoid an empty section. A retired product label still resolves as a search synonym, but it is never presented as the current canonical name.
Curated collections
Grouped around approved goals without creating a second authority. A collection is a route, not a rewrite.
First 30 days as an administrator
Onboarding, configuration, identity, and verification — mixed authorities, each labelled.
Preparing for a works-council conversation
Worker rights, human authority, anti-surveillance doctrine, and accessibility evidence.
Reviewer essentials
Queue behaviour, decisions, separation of duties, and correction handling.
Evaluating for procurement
Trust evidence, enterprise readiness, support model, and commercial terms.
Recently changed and corrected
Nine freshness states, each with a distinct public treatment.
Recently verified — reviewed on a date, with no implied product change
Recently changed — what type of content changed, linked to the release record
Correction — the note, date, affected section, replacement, and owner
Superseded — redirected to the current resource where safe
Stale / review overdue — marked or removed according to risk
Withdrawn — removed from content and public indexing
Changed product label — old term resolves in search, is not shown as canonical
Index lag — the directory stays authoritative; search may lag
A “reviewed” date and an “updated” date answer different questions. Both are shown when both matter.
One question, one authority
The Resource Center summarizes what a destination governs and then gets out of the way. It does not restate security posture, quote pricing, or explain product behaviour in its own words.
Product behaviour
Product Documentation.
Troubleshooting
Help Center.
Shipped changes
Release Notes.
Security & privacy
Trust & Governance.
Live operational state
System Status.
Procurement & contracts
Enterprise & Procurement.
Commercial terms
Pricing — never duplicated here.
Accessibility
Tested scope and known limitations.
No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection under any tier or configuration.
Every resource indexed here preserves worker visibility, correction rights, human decision authority, and the deterministic-classification boundary.
If you cannot find it
CurrentThe rule: sales is never the default recovery.
No results
“No current resources matched those terms,” with an explanation that gated content is not exposed — plus clear filters, approved synonyms, and browse-by-task.
Search unavailable
“Search is temporarily unavailable. Browse current resources below.” The directory and quick paths stay usable.
Restricted-only match
No title or snippet leak. A generic controlled-access summary only where policy allows.
Outdated match
The current replacement is preferred, with the old term mapped to the current label.
Offline
Non-sensitive filter state preserved, connectivity shown, and never a false claim that a submission succeeded.
Limitations: a route failure gives resources-aware recovery rather than a generic 404, and a withdrawn resource is never served from cache.
Report stale, missing, or inaccessible content
CurrentObjective: let a reader fix the library rather than work around it.
What to report
Content that is stale, missing, contradictory, or inaccessible.
Where from
Result metadata, a resource detail, or this section.
What you get
A reference and a status. No response time is promised, because none is approved for this route.
Do not include
Personal, worker, credential, account, security, legal-case, health, or payment information.
Not a vulnerability channel. Security issues go to the responsible disclosure route. Generic content feedback is not a substitute for it, and routing a vulnerability through a marketing form would be unsafe.
Discovery first
Still need a person?
Support, documentation, and trust evidence come first and are never gated. A commercial conversation is available when you want one — not as a replacement for content that should exist.
Visit Help Center
Resource Center questions
The public discovery layer for current ZoikoTime onboarding, help, documentation, learning, developer, proof, and release resources — each shown with authority and currentness metadata. It routes you to the source that governs your question rather than answering in its own voice.
Use Product Documentation for current product behaviour, concepts, fields, states, permissions, limitations, and recovery guidance. The Resource Center routes you to that source rather than duplicating its content.
Use Release Notes for the authoritative chronological record of verified shipped changes. Each change can include its date, version, state, applicability, and required action.
Resources are governed by status, owner, review or verification dates, applicability, authority, and limitations. Stale, superseded, corrected, or withdrawn resources receive distinct treatments rather than being presented as current.
Yes. Resources can be discovered by task, role, product area, authority, applicability, and resource type. Role selection is explicit and filters the directory; it does not create a profile or infer information about you.
Yes. Security, privacy, governance, accessibility, and related assurance evidence are available through the Trust & Governance destination. The Resource Center identifies that authority rather than restating security claims itself.
Yes. Development Documentation provides current technical guidance, architecture, patterns, security, testing, production guidance, and verified integration information where available.
Use the approved task paths, filters, synonyms, and current directory first. If no current resource matches, the Resource Center should explain that clearly and provide an appropriate recovery path. Sales is never the default recovery for missing support or documentation.
No. Resource discovery does not require worker monitoring or collection of sensitive worker activity. The Resource Center does not use screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection.
Security vulnerabilities should be reported through the responsible disclosure route. General Resource Center feedback is not a substitute for the vulnerability reporting channel.
Enterprise buyers can use the Enterprise and Procurement resources for readiness, identity, administration, support, procurement, and commercial information. Support intent is not redirected to sales when authoritative support or documentation already exists.