TEMVERIS

Resources · Documentation

Documentation that helps you move from understanding to implementation.

Find guidance on TEMVERIS concepts, review and approval workflows, record evidence, and integration pathways. Technical API specifications have their own developer references.

Find documentation
A bright, empty office desk with a laptop beside tall windows
Captured eventSource context attached
ReviewedAuthorized role
Evidence trailIllustrative, not live

Where to start

Where would you like to start?

Choose your role or the task you need to complete. Each path identifies scope, prerequisites and the authoritative owner. Choosing a role is a reading aid only; it does not grant any permission.

Path for Operations admin

Understand Plan, Govern and the record lifecycle.

  • Prerequisite: none; reading is public.
  • Owner: Product documentation
  • Choosing this role does not confer permission.
Open this path
A laptop on a desk showing an analytics dashboard

Foundations

Start with the governed record

TEMVERIS describes workforce-time events, planned context, authorized review and evidence as distinct parts of the same record.

Concept

Capture

Adds source context to workforce-time events.

A missing event is not the same as zero attendance.

Explore Capture

Record status

An approved record is not a completed transfer.

Approval, export eligibility, transmission, delivery acknowledgment and recipient processing are different conditions. Select a stage to see what it does, and does not, tell you.

Approved: The decision is approved.
What it does not mean: Approved is not transmitted.

Browse approved documentation

Find the exact guidance

Search covers publicly approved titles, summaries and controlled synonyms. Results show why they match and offer reset controls.

No published articles yet

Nothing to show here, and we won’t invent it.

Only real, published, owned articles appear in this catalogue. Until the editorial inventory is approved, browse the concept sections on this page or visit related destinations.

Related destinations
Two colleagues working at desktop computers in a bright office

Version & applicability

Use the instructions that match your situation

Every prescriptive article identifies the applicable product or deployment version and whether its verification is current. There is no “latest” badge until a real release is verified.

Select a version to see how an article’s applicability panel will read. Versions are populated from verified publications only.

LabelMeaning
Applies toVersion or deployment the steps were written for.
VerifiedReviewed by the named owner on a stated date.
Needs reviewSource changed; do not rely on it as production guidance.
DeprecatedShown with a tested successor route.
A team in a meeting room with laptops, looking at a presentation screenIllustrative workplace photo

Identity & access

Understand access responsibilities

Role-based permissions and controlled administration are part of the TEMVERIS product positioning. Specific identity protocols and setup procedures require validated technical documentation.

Review IT & Security

Developer handoff

Need API, webhook or release information?

Developer Documentation, API Reference, Webhooks and Release Notes are separate destinations. Use their verified publications for technical contracts.

Troubleshooting

Resolve a documentation issue

Begin with the symptom, affected function, safe diagnostic scope and recovery options. Escalate unknown cases rather than inventing a fix.

  • Check its applicability and review status first. If the label reads “Needs review” or no version is stated, don’t rely on it as production guidance — report it with the feedback form below.

  • Reset the filters. Only published, owned articles appear in the catalogue, so a topic may not be documented yet; use the concept sections or related destinations meanwhile.

  • A missing event is not the same as zero attendance. Confirm the approved source and its delay status with your administrator before drawing a conclusion.

  • Identity protocols and setup procedures need validated technical documentation. Ask your TEMVERIS contact or Support rather than following unverified steps.

Browse troubleshooting
A colleague presenting to a team in a brick-walled office

Safety of examples

Every example is clearly labeled.

Illustrative screens and sample values are synthetic. Executable API and webhook examples may appear only after engineering, security and documentation verification.

Synthetic illustration · not an API contract · no real records or secrets

record: EXAMPLE-0001            # synthetic identifier
captured:  true    # an event exists
reviewed:  false   # not yet reviewed by an authorized role
approved:  false
export_eligible: false
note: "Sample values only. Approved != transmitted != accepted != processed."

Editorial assurance

See which material is ready to rely on.

Technical guidance should identify owner, applicability and review status. Missing source means the instruction must not appear as production guidance.

FieldWhat readers will seeIf missing
OwnerNamed accountable teamArticle is not published
ApplicabilityProduct / deployment versionShown as “applicability not stated”
Review statusVerified, needs review or deprecatedNot shown as production guidance
Report inaccurate guidance

Feedback & corrections

Was this documentation useful?

Tell us if a step is unclear or an article appears out of date.

Please don’t enter employee data, passwords, tokens or confidential payloads.

See how TEMVERIS fits your organization.

A demo can focus on workforce-time governance, implementation roles, downstream integration needs and privacy boundaries.

Book a demoExplore the platform
A team working on laptops around a wooden table, seen from above