Zoiko Sema + ZoikoTime

Connect approved communication context to reviewable workforce operations

Map approved Zoiko Sema workspaces to ZoikoTime teams or organizational units, apply roles, permissions, privacy modes, policy scope, and jurisdiction controls — then review connection health and approved operational context.

Start Free Request Enterprise Demo

Optional

Workspace-scoped

Role-controlled

Audit-ready

Zoiko Sema and ZoikoTime licensing, availability, setup, context scope, direction, and implementation vary by plan, contract, configuration, region, and product status.

An administrator mapping approved communication workspaces to governed workforce scopes while colleagues review the connection

Nothing is active yet

Two workspaces are excluded by policy and will never map. No exchange occurs until eligibility, mapping, governance, authorization, testing, and acceptance are all complete. Illustrative interface — all values synthetic.

How do Zoiko Sema and ZoikoTime work together?

Zoiko Sema and ZoikoTime are independent products that organizations may connect through an optional, customer-configured integration. Authorized administrators map approved Sema workspaces to ZoikoTime organizational scopes, define permitted context categories, roles, privacy modes, policy and jurisdiction treatment, test the connection, and approve activation. Communication context remains governed and reviewable — it does not automatically become time worked, payroll truth, performance evidence, discipline, legal status, or compliance.

Independent product

Zoiko Sema

Governed communication.

Meetings and messaging
Channels and spaces
Decisions and actions
Workspace administration
Approved AI-generated outputs

Optional bridge

Governed bridge

Explicitly configured.

Workspace mapping
Role permissions & context scope
Privacy modes, policy, jurisdiction
Review before sync
Health, exceptions, audit

Independent product

ZoikoTime

Workforce Truth Infrastructure.

Reviewable workforce records
Deterministic policy application
Human review
Evidence Ledger history
Controlled downstream workflows

Independence rule

Zoiko Sema remains a complete communication platform without ZoikoTime. ZoikoTime remains complete Workforce Truth Infrastructure without Zoiko Sema. Neither is a feature hidden inside the other, and the connection between them is optional and separately qualified.

Explore ZoikoTime Visit Trust Center

The Locked Connection Model

Map → Govern → Review

Three steps, in this order, always. There is no configuration in which context reaches a workforce record without passing through all three.

Map approved workspaces

An authorized administrator selects which Sema workspaces connect, and to which ZoikoTime organizational scope. Nothing is mapped by default.

Explicit selection

Workspace, owner, destination unit, effective dates, ownership record.

Unmapped means outside

An unmapped workspace is not connected in any sense — not partially, not for metadata.

Duplicates resolved

Overlapping or ambiguous mappings must be resolved before activation.

Workspace mapping

Direction and method are not claimed here. One-way or two-way sync, real-time delivery, APIs, webhooks, batch transfer, specific fields, latency, and providers are stated only where validated for your configuration. This page describes governance, not a transport guarantee.

Availability, Licensing & Eligibility

Not Included by Default — Anywhere

The integration is a separately qualified capability. Having both products does not mean the bridge is available to you.

Dependency	Must be confirmed
Product subscriptions	Both products, separately licensed
Plan & contract	Integration eligibility under your current agreement
Enterprise setup	Implementation scope and support model
Region & product status	Current availability for your region and version
Administrator authority	Named eligible roles on both sides
Governance readiness	Policy, privacy, legal, and accessibility review complete

Check current Pricing or request enterprise evaluation. Nothing on this page should be read as confirming availability for your organization.

Role-Based Entry Points

Six audiences, six routes

Sema administrators

Workspace eligibility, ownership, and what leaves a workspace.

ZoikoTime administrators

Destination scopes, policy version, review owners, retention.

Reviewers & managers

What arrives for review, and what it does not establish.

IT & security

Service identity, least privilege, credential custody, revocation.

Workers & participants

Notices, source visibility, correction and support routes.

Buyers & evaluators

Licensing, implementation, evidence, and enterprise evaluation.

Workspace & Organizational Mapping

Every Mapping Is a Governed Object

Selecting a mapping opens its full record: source, destination, purpose, scope, policy, privacy, owner, test evidence, and change history.

MAP-0114 · version 2 · effective 01 Sep 2026

Field Ops North → Field Services · North

Mapped · awaiting test

Source

Workspace: Field Ops North
Workspace owner: Named, on Sema side
Eligibility: Confirmed

Destination

ZoikoTime scope: Field Services · North
Scope type: Organizational unit
Duplicates: None unresolved

Purpose & scope

Business purpose: Documented
Context categories: Meeting context only
Prohibited uses: Recorded explicitly

Governance

Privacy mode: Restricted
Policy version: Field North v3
Jurisdiction: DE · qualified
Retention: Per approved schedule

Authority

Review owner: R. Adeyemi
Integration admin: Named
Final approver: Named

Test evidence

Sample validation: Not yet run
Denied cases: Not yet run
Acceptance: Not signed off

Notices

Participant notice: Drafted, pending activation
Worker notice: Required before first exchange

What this mapping does not do

It does not export a communication stream, and it does not make meeting context into hours worked. It permits a defined category to be reviewed by a named person.

Mapping states: Draft · Mapping incomplete · Mapped · Test pending · Test failed · Accepted · Active · Paused · Excluded · Superseded · Retired.

Context Scope Registry

Approved categories, and nothing else

Each category carries a purpose, direction, sensitivity, retention, and visibility. A category absent from the registry is excluded by definition.

Context category	Registry state
Meeting context — occurrence, scope, owner	Approved
Decisions recorded in an approved space	Approved
Actions and owners from an approved space	Approved
Approved AI-generated summary, as reviewable draft	Conditional — human review required
Message content and full communication streams	Excluded
File content and attachments	Excluded
User activity monitoring of any kind	Prohibited

No universal export

Not every message, meeting, file, user activity record, or AI output is shared with ZoikoTime. Unmapped workspaces and unapproved or excluded categories remain outside the connection entirely — there is no partial or metadata-only leakage from an unmapped workspace.

Exact fields are not published

Precise categories, fields, direction, timing, retention, and visibility must come from your current configuration and documentation rather than from this page. Publishing a field list we cannot guarantee for your deployment would be a claim, not information.

Governance, Privacy Modes & Jurisdiction

The Bridge Cannot Widen Itself

Only authorized administrators select workspaces, mappings, context categories, roles, privacy modes, policy scope, jurisdiction treatment, and retention. No prompt, request, or integration behavior expands that.

No screenshots, keystroke content, URL history, application-name monitoring, or clipboard collection under any tier or configuration.

Minimized

Least context necessary for the stated purpose.

Restricted

Narrow role visibility with review required.

Aggregated

Unit-level context only, no individual attribution.

Review-gated

Nothing reaches a workflow before human approval.

Excluded

The workspace or category never connects.

Administrator-configured

Which workspaces map, and to which scopes
Which context categories are permitted
Privacy mode per mapping
Policy version, jurisdiction treatment, retention
Notices, review requirements, and audit settings

Excluded by policy, typically

Confidential and legal spaces
Executive and HR spaces
Security and regulated spaces
Externally attended spaces

Jurisdiction and data-location treatment is qualified, never asserted. See Data Location & Residency.

Controlled Setup & Authorization

Ten Stages Before First Exchange

Deliberately slow. An integration that can be switched on in an afternoon is an integration nobody reviewed.

Stage 01

Confirm eligibility

Products, contracts, versions, environments, ownership, roles, support path, readiness.

Stage 02

Establish authority

Sema owner, ZoikoTime owner, integration admin, security/privacy/legal reviewers, business owner, final approver.

Stage 03

Define purpose & scope

Business purpose, mapped organizations, categories, permitted and prohibited uses, acceptance criteria.

Stage 04

Design mapping

Workspaces to scopes, duplicates resolved, effective dates, ownership recorded.

Stage 05

Configure governance

Roles, privacy modes, policy versions, jurisdiction, retention, notices, exclusions, audit.

Stage 06

Authorize connection

Approved method, service identity, least privilege, credential custody, expiry, revocation.

Stage 07

Test safely

Non-production or synthetic data, sample mappings, denied and excluded cases, error and retry.

Stage 08

Review & accept

Product, business, security, privacy, legal, accessibility, support, and operational sign-off.

Stage 09

Activate & communicate

Scheduled activation, notices confirmed, first exchanges monitored, rollback preserved.

Stage 10

Stabilize & govern

Health, exceptions, questions, audit evidence, mappings, policy, versions, expansion readiness.

Setup outputs

Implementation plan and approved mapping
Governance profile
Test evidence and acceptance record
Activation record and rollback plan
Support runbook and review schedule

Testing must include the failures

Acceptance requires validating denied cases, excluded categories, permission errors, and retry behavior — not only the happy path. A test that only proves success has not tested the governance.

Test data is approved non-production, synthetic, or controlled. Live worker records are never used to validate a new mapping.

Review Before Sync & Human Authority

Context Is an Input, Not a Conclusion

The integration never determines

Time worked · attendance · breaks · payroll outcomes · performance · misconduct · discipline · employment status · legal status · compliance. It may route context for review. Authorized humans decide, under ZoikoTime policy, with correction and escalation available.

What a reviewer sees

Source reference and workspace
Context category and purpose
Privacy mode and policy version
Stated limitations of the context
What accepting it will and will not affect

Any ZoikoTime classification downstream remains deterministic, policy-bound, jurisdiction-aware, reviewable — and is never branded as AI.

Connection Health & Change History

Status, freshness, versions, owners

A connection health dashboard showing source status, freshness indicators, a failed exchange, and downstream destinations

Exceptions, Retry, Quarantine & Reconciliation

Fifteen Exception Types, None of Them Silent

Uncertain context is contained rather than passed along. Quarantine exists so that a failure cannot become a workforce record by default.

Authorization expiredPermission deniedDestination missingMapping conflictExcluded categoryPolicy mismatchRetention conflictSource unavailableDestination unavailableDuplicateOut of orderUnsupported versionReview overdueAcceptance expiredNotice outdated

Exception	Affected mapping	Attempts	Owner	Participant impact	State
Authorization expired	Service Desk	3	IT & security	None — nothing exchanged	Open
Mapping conflict	Project Atlas	—	Integration admin	None — not active	Awaiting correction
Retention conflict	Field Ops North	1	Privacy	Notice update required	Quarantined

Exception queue, synthetic. Diagnostics are sensitive-data-safe; no message content, credential, or worker record appears in an error detail.

Quarantine

Prevents uncertain context from reaching downstream workflows while preserving source, reason, owner, review, and expiry. Nothing is discarded, and nothing proceeds.

Reconciliation

Compares source, bridge record, destination status, version, review outcome, downstream effect, and corrective action. Conflicts are never silently overwritten.

Closure

Requires resolved cause, retry or reconciliation result, affected items reviewed, participant communication where required, complete evidence, linked support reference, prevention logged, and owner sign-off.

Meeting-to-Work Context

A Meeting Is Not a Timesheet

Approved meeting context — occurrence, scope, owner, recorded decisions, actions, and follow-ups — may support review. Its limitations travel with it.

Meeting presence is not time worked

Meeting presence or duration is context, not automatic time, attendance, payroll, performance, or compliance truth. ZoikoTime rules, review, correction, and human approval remain authoritative — a calendar entry has never been evidence of work performed.

Channels, spaces, decisions & actions

Structured communication outcomes — a recorded decision, an assigned action, a named owner, a follow-up — carry their workspace scope with them. Unstructured discussion does not transfer.

Governed AI-Generated Outputs

Always a draft until a person owns it

AI-generated

Meeting summary · draft, pending review

Status: Draft — not approved, no downstream effect
Source references: Linked to the approved meeting record
Generated: 05 Aug 2026, 11:02 CEST
Reviewer: Unassigned
Edited: No
Retention: Per approved schedule
Limitations: May omit or misattribute content. Not a record of work performed.

Product, version, and model information appear only when approved. A reviewer must verify source, accuracy, completeness, attribution, context, sensitivity, permitted purpose, and destination effect before approval.

Prohibited use of any AI output

No AI-generated output may automatically determine hours, attendance, breaks, payroll, performance, misconduct, discipline, employment status, legal status, or compliance. If source content, AI output, policy, or a reviewer decision changes, downstream context is re-evaluated and versioned.

Worker & Participant Transparency

The People in the Context Can See It

Notice

Approved notices where the integration affects a worker-facing record or workflow, issued before first exchange.

Source visibility

Which workspace, which category, which purpose, and which policy version applied.

Correction

A defined route with human review, and escalation where a correction is declined.

Support

A named route for questions about the integration itself, not only about a record.

Manager, Reviewer & Leadership Experience

Bounded review, not a monitoring console

Reviewers see assigned context within their scope, with limitations attached.
Managers see queue state, not behavioral profiles of their team.
Leadership sees organization-level context, aggregated where individual detail is unnecessary.
Nobody gets a ranking, a productivity score, or an activity feed. Those do not exist in this product.

Audit Evidence & Governed Exports

What is preserved

Configuration versions and who approved them
Mapping changes with reason and effective date
Transfer and exchange records within retention
Review outcomes and reviewer identity
Exception, quarantine, and reconciliation history
Notice issuance and correction records

Exports are governed, scoped, and audited. Audit evidence supports review — it is not an audit opinion, and it does not establish legal admissibility.

Evidence Ledger

Security, Privacy, AI Governance & Trust

Where the Evidence Lives

Trust Center

Entry point for assurance evidence.

Security

Identity, access, encryption, logging, incidents.

Privacy

Categories, purposes, retention, rights.

AI Governance

Approved scope, prohibited uses, authority classes.

Human-in-Command

Where decision authority sits and stays.

Data Location

Storage, processing, access, transfers — separately.

Accessibility

Tested scope, methods, known limitations.

System Status

Authoritative current operational state.

Jurisdiction, Residency, Retention & Lifecycle

Qualified, never asserted

Data location, transfer, retention, deletion, and retirement for the integration are qualified against your contract and configuration. This page makes no residency guarantee for any region.

Retirement covers disabling a mapping, pausing exchange, deleting or retaining prior context per schedule, and preserving audit history. Decommissioning the bridge does not delete records already created in ZoikoTime under policy.

No invented claims

No certification, compliance, data-residency, security, retention, customer, productivity, ROI, accuracy, or performance claim appears on this page. Where a claim would require evidence we do not currently hold, the claim is absent rather than hedged.

Implementation, Pilot, Launch & Expansion

Controlled Rollout

Phase 01
Discovery & readiness
Output
Eligibility confirmed, authority named, purpose and acceptance criteria documented.
Phase 02
Pilot
Output
One or two mappings, full governance, tested denied cases, participant notices live.
Phase 03
Launch
Output
Scheduled activation, monitored first exchanges, rollback preserved, support runbook active.
Phase 04
Stabilize & expand
Output
Health and exception review, audit evidence, expansion only after stabilization.

There is no universal implementation duration. Timing depends on scope, workspaces, governance review, jurisdictions, pilot outcomes, and support model.

Commercial & Enterprise Evaluation

Separate subscriptions, separate setup

What is separately qualified

Zoiko Sema subscription
ZoikoTime subscription
Integration eligibility under your plan and contract
Enterprise setup and implementation scope
Support model and region availability

Pricing Procurement & Legal

Customer & implementation evidence

No customer names, logos, counts, quotes, metrics, or case studies appear here, because none has been verified and approved for this integration. This is an intentional empty state rather than an omission — when verified evidence exists, it will appear with its scope and date.

Already a customer?

Open Integration Settings Documentation Service Status Product Updates Contact Support Enterprise Support

Pause, disable, and decommission are supported operations with their own evidence and notice requirements — not hidden settings.

Optional by Design

Connect communication context without surrendering workforce authority

See how an optional, customer-configured bridge can route approved Zoiko Sema context into reviewable ZoikoTime operations — with explicit mapping, governance, human review, and audit history at every step.