Dashboard
/dashboardPreview timer, workload, and key operating indicators.
Taktis
Coming soonTaktis is the professional-services workspace for projects, time entries, timesheets, approvals, customers, invoices, expenses, staffing, and operational reporting. Its current release candidate is also known internally as Chronos.
Release-readiness guide
Taktis pre-release readiness manual
Prepare roles, reference data, controls, and acceptance evidence for the Taktis professional-services workspace before production release.
Audience, scope, and prerequisites
This is a release-readiness guide, not production operating authority. It covers preparation and controlled acceptance of project-to-cash, time, approval, invoice, expense, absence, scheduling, reporting, and administration workflows.
Who this is for
- Professional-services operations
- Project managers and approvers
- Finance administrators
- Release testers and support
Before you sign in
- A formal release or preview invitation
- A non-production tenant and synthetic acceptance data
- Named business, finance, security, privacy, and technical owners
- Written project, rate, approval, invoicing, and retention rules
Roles and responsibilities
| Role | Access | Responsibilities |
|---|---|---|
| Consultant | Preview assigned projects, time entries, and timesheets. |
|
| Manager or approver | Preview projects, staffing, approvals, and reports within assigned scope. |
|
| Finance or administrator | Preview customers, rates, invoices, reports, and tenant settings when explicitly assigned. |
|
Prepare the release candidate
Do not treat route availability as production approval. Establish the release, ownership, data, access, and accounting baseline first.
Confirm authorized preview access
Establish that the environment and user are explicitly approved for acceptance testing.
- 1Obtain the release notice
Record environment, build, known issues, support channel, test window, and prohibited uses.
- 2Confirm identity and tenant
Verify the expected tenant claim and one minimum role; test that an unassigned identity fails closed.
- 3Name accountable owners
Assign business, project, finance, privacy, security, and technical acceptance owners.
- 4Set evidence handling
Define where sanitized screenshots, identifiers, reconciliations, and defects are retained.
Expected result
The test has explicit authorization, owners, version, scope, evidence location, and stop conditions.
Prepare controlled reference data
Model the rules that drive time, approvals, billing, staffing, and reports without importing production records.
- 1Define synthetic customers and projects
Include active, inactive, billable, non-billable, budgeted, and cross-team cases.
- 2Define rates and periods
Set expected currencies, rate rules, tax assumptions, invoice periods, and independent expected totals.
- 3Define approval paths
Map consultant, manager, finance, and administrator decisions including rejection and recall.
- 4Prepare edge cases
Include time-zone boundaries, overlapping work, absences, expenses, closed periods, and insufficient permissions.
Expected result
A synthetic dataset and expected-results ledger cover normal, denied, correction, and boundary cases.
Run controlled acceptance
Test one traceable project-to-cash scenario and reconcile every transition before recommending release.
Accept the project-to-cash workflow
Validate time capture through approval, invoice generation, reporting, and audit evidence.
- 1Create or select the test project
Verify customer, assignment, budget, rate, dates, and tester permissions.
- 2Record and correct time
Test timer and manual entry, validation, edit, delete, filters, and draft boundaries.
- 3Submit and decide the timesheet
Exercise submit, reject with reason, correct, resubmit, approve, and allowed recall behavior.
- 4Generate a draft invoice
Use the accepted period and reconcile line items, currency, totals, customer, and included time.
- 5Inspect output and reports
Verify PDF and report/export values without sending the invoice or marking real payment.
- 6Preserve acceptance evidence
Record stable identifiers, expected versus actual totals, roles, timestamps, and defects.
Expected result
The synthetic project-to-cash trail is authorized, arithmetically reconciled, role-correct, and reproducible.
Record the release decision
Convert test evidence into an explicit accept, conditional-accept, or reject decision.
- 1Reconcile results
Compare permissions, status transitions, amounts, PDFs, exports, and reports with the approved ledger.
- 2Review non-functional controls
Assess accessibility, localization, performance, recovery, auditability, privacy, and tenant isolation.
- 3Classify every gap
Assign severity, owner, workaround, target release, and retest requirement.
- 4Approve explicitly
Collect sign-off from business, finance, security/privacy, support, and release ownership.
Expected result
A dated decision identifies the tested version, accepted scope, open risks, owners, and production authorization status.
Security and data handling
- Use synthetic customer, worker, time, expense, and invoice data before production approval.
- Apply least privilege and time-bound elevation to approval, finance, report, and settings roles.
- Reconcile amounts independently; interface output is not proof of accounting correctness.
- Do not send invoices, mark payments, or create official records during preview testing.
- Treat exports and PDFs as confidential test artifacts and dispose of them under the acceptance plan.
Known limitations
Read before relying on an unsupported workflow
These limits describe the source-pinned Taktis / Chronos 2.0 release candidate scope and must be rechecked when the product changes.
- Taktis is listed as coming soon and this manual does not authorize production use.
- Implemented routes and a version number do not establish operational readiness, SLA, or accounting acceptance.
- Features, role names, calculations, and navigation may change before release.
- The frontend depends on the existing private Chronos API and correct Keycloak tenant and role claims.
- Official payroll, billing, leave, tax, and accounting use requires separate organizational approval.
Troubleshooting
You cannot sign in to Taktis
Likely cause: The session expired, the identity is not assigned to the application, or the tenant claim is missing.
- Open the application from the approved portal and complete sign-in again.
- Confirm that the correct organizational identity and tenant are selected.
- If access is still denied, record the time and request an entitlement check from support.
A documented action or navigation item is not visible
Likely cause: The current role, release, tenant configuration, or feature flag does not expose that operation.
- Confirm the role and prerequisites listed for the procedure.
- Reload the page after signing in again; do not attempt to bypass the interface through direct URLs.
- Ask the product owner whether the feature is enabled for the tenant before reporting a defect.
A saved change or background operation is not visible
Likely cause: Validation failed, processing is still running, or the current view is stale or filtered.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search for the item by its stable name or identifier.
- Do not repeat irreversible or externally visible actions until the original operation status is known.
A calculated amount or report does not reconcile
Likely cause: Rate, period, billability, currency, tax, status, or backend contract differs from the expected ledger.
- Stop the scenario before sending or marking payment.
- Preserve sanitized inputs, IDs, statuses, expected calculation, and actual output.
- Raise a release-blocking defect with finance and product ownership.
Contact support
Contact support when
- A repeatable Taktis error blocks an approved workflow
- Expected data, permissions, or tenant boundaries appear incorrect
- A security, privacy, compliance, or data-loss concern is suspected
- An acceptance result differs from the independent financial calculation
- A role can approve, report, invoice, or administer outside its scope
- A preview action creates an unintended external effect
Include
- The page, action, and expected result
- The exact error text and time of occurrence, including time zone
- Your tenant, role, browser, and a sanitized record or item identifier
- Whether the problem can be reproduced and which troubleshooting steps were tried
Never include
- Passwords, access tokens, API keys, recovery codes, or session cookies
- Unredacted personal, health, financial, or other regulated data
- Private encryption keys or complete confidential documents unless an approved channel is provided