Tasks Steps

Logging

Logging keeps a timeline of each test session, and the step's log level (Basic, Standard or Detailed) decides how much detail it records. The level is fixed when a session starts, so a change only affects sessions that start afterwards.

Updated 2026/11/04

Logging keeps a timeline of what happens while a candidate takes a step: signing in, pre-start checks, starting and resuming the session, moving between pages and finishing, along with any warnings and errors. When a question comes up after the exam, such as “did the candidate start on time?” or “what went wrong with the camera?”, the log shows what happened and when.

Where to set it

Open the step in the step editor and go to the Logging section, then choose a Log level. The level applies to every candidate who takes the step, and each step in a task can use its own level.

Log levels

OptionWhat is recorded
DefaultYour organization's standard level. The label shows which level that is, for example Default (Standard).
BasicThe main events of a session: signing in, pre-start checks such as the camera and microphone, starting, resuming, moving between pages and finishing, plus every warning and error.
StandardEverything in Basic, plus smaller actions inside the session, for example switching cameras or a blocked right-click.
DetailedEverything in Standard, plus the finest interface actions, for example opening a menu.

Each level includes everything recorded by the levels above it in the table. Levels that aren't available to your organization are shown but can't be selected.

When the level takes effect

A session's log level is fixed when the session starts. If the candidate leaves and resumes later, the session keeps the same level. When you change a step's log level, only sessions that start after you save the step use the new level.

Before a session starts

Candidates also spend time in the task's workspace before they start a step and between steps. There, logging uses the most detailed level among the steps the candidate can take. If no step is available to the candidate, your organization's standard level is used.

Where to read the logs

  • Session details: the Logs section shows the timeline of that session.
  • Candidate details: the Logs section shows everything recorded for the candidate, including the time spent in the workspace.

Both views can be filtered by level, so you can hide routine events and focus on warnings and errors.

The log level only changes how much is recorded. It doesn't change what candidates see, it doesn't affect scoring, and it doesn't use credits.
Good to know

No. Each session keeps the log level it started with, even when the candidate leaves and resumes it later. When you change a step's log level, the new level applies only to sessions that start after you save the step. Sessions already started or completed keep the level they had.

Default uses your organization's standard log level, which is also the most detailed level available to it. The option's label shows which level that is, for example Default (Standard). Steps left on Default follow your organization's level automatically, so you don't need to update them one by one if that level changes.

Levels that are shown but disabled aren't available to your organization. You can always choose Default or any enabled level. If a step was set to a level that later becomes unavailable, its sessions use your organization's standard level instead. Contact TestInvite support if you need more detail than the enabled levels provide.

Before a session starts, the candidate is in the task's workspace: signing in, completing the access form, accepting consents and choosing a step. Logging there uses the most detailed level among the steps the candidate can take, so nothing a later step would record is missed. If no step is available to the candidate, for example when the task is closed, your organization's standard level is used.

Yes. Every log level, including Basic, records warnings and errors, such as a camera or screen sharing problem. Standard and Detailed only add more routine events, which helps when you need to reconstruct exactly what a candidate did step by step.

No. Logs record what happened during a session, such as starting, moving between pages and finishing. Answers and scores are stored with the session itself and shown in its results. Choosing a more detailed log level records more events, not more of the candidate's answers.

No. The log level doesn't use credits, and candidates see no difference during the exam: the same screens, the same steps and the same timing. A more detailed level only records more events in the background.

No. The log level is set on the step and applies to every candidate who takes it. Customized step settings on a candidate's ticket, such as extra attempts or relaxed security, don't include the log level.