Skip to content

Common tools

Some pages and tools do not belong to a single hub but serve the whole platform: ticket inspection, logs, bug reporting, certificate verification, training, records, account security and error handling.

What it is for. It is the in-depth ticket inspection tool: a detailed view with all the data, the timeline, the links and the internal notes.

When to use it. For diagnosis and second-level support, when you need the complete picture of a ticket.

How to open it. From the dock or from the inspection links.

What it shows and how to use it. The ticket in depth (fields, history, relationships, internal notes), in advanced read-only mode; from here you move to the Editor to make changes.

What happens next. It supports analysis; no direct changes.

Notes. Complements the Editor (Ticket editor) and the Preview (Ticket preview).

What it is for. It is the platform’s activity log.

When to use it. For audits and to reconstruct «who did what and when».

How to open it. From the settings / audit area.

What it shows and how to use it. The entries with actor, action and date, with filters and export.

What happens next. It supports audit and compliance.

Notes. Complements the Routing Log (Routing Log) and the tickets’ Audit tab.

What it is for. It is the tool users use to report platform problems. The floating red button on every page is not an error message: it is Bug Reporting.

When to use it. When you find a platform malfunction to report.

How to open it. From the floating red button on every page; the list of reports is on the Bug Reporting page.

What it shows and how to use it. The report form (description, page, screenshot) and, on the page, the list of collected bug reports.

What happens next. The report is recorded so that someone can pick it up.

Notes. It is a feedback tool, not an error.

What it is for. It verifies the authenticity of certificates/attestations issued by the platform (e.g. training certifications).

When to use it. To validate a certificate someone presents.

How to open it. From the «Verify certification» link or from the certificate URL.

What it shows and how to use it. The verification result for the certificate (valid/not valid) with its data.

What happens next. It confirms or refutes authenticity.

Notes. Linked to the Learning Platform (Learning Platform).

It is the training and micro-learning platform (courses, paths, quizzes, certifications), shared between HR and operational enablement. Described in Learning Platform.

It manages generic records (entities built with the Builder) and document retention. Described in Records Management.

What it is for. It is the sign-in page of exoCortex Core.

When to use it. When you enter the platform or after sign-out/session expiry.

How to open it. At the tenant address (automatic redirect if you are not authenticated).

What it shows and how to use it. The email/password fields, sign-in with company domain if available (SSO/Azure, if enabled for your user), self-service password recovery (TOTP) and, if configured, the MFA code. See Accessing the platform.

What happens next. Once authenticated you enter the Home (or you are asked for MFA/QR on first sign-in).

Notes. After too many failed attempts the account is temporarily locked (anti brute-force).

From the user menu on every page you reach Change password (Change password) and MFA Setup (MFA Setup). Only you set your password; MFA uses a QR code + 6-digit code.

The bell on every page opens your notifications (assignments, status changes, approvals, SLAs, mentions), governed by the notification matrix. See Notifications.