Workflows

Read the change history

Trace what changed, who acted, and what the record contained before the change.

Instructors11 minute readVerified against the live product · August 2026

Guide at a glance

How to use this guide

Start with

Identify the target record, current value, proposed outcome, actor, and reviewer before deciding what should happen next.

By the end

The decision is complete, attributable, and reconcilable with the official record and its history.

  1. 1.What is recorded
  2. 2.Use history to answer a question
  3. 3.Why accounts must not be shared
  4. 4.When to contact support

What is recorded

FieldMeaning
TargetThe record or field affected.
Previous valueThe value immediately before the action.
New valueThe value applied by the action.
ActorThe account responsible for the action.
TimeWhen the action occurred.

Use history to answer a question

  1. 1Start with the Cadet or record being questioned.
  2. 2Narrow to the approximate date.
  3. 3Read the previous and new values before interpreting the action.
  4. 4Identify the actor and confirm whether their account was individual.
  5. 5Compare related changes made around the same time.

Why accounts must not be shared

History can only name the account that acted. If several instructors use one login, the actor field cannot tell you which person made the decision.

Give every instructor their own included account. This improves recovery as well as attribution.

When to contact support

Contact support when the history shows a platform-administrator action nobody recognizes, a value that changed without a corresponding event, or a sequence that cannot be reconciled with the visible record.

Include the school, unit, affected record, approximate time, and what you expected. Do not include passwords.

Practical playbook

Checks, outcomes, and troubleshooting

Use this section when you are carrying out the task now, or when the ordinary path did not produce the expected result.

Before you act

  • Identify the affected record and narrow the time window as closely as possible.
  • Confirm each instructor uses an individual account before relying on actor names.
  • Read surrounding changes; one operational action may produce several related entries.

Success looks like

  • You can state what changed, from which value to which value, who acted, and when.
  • The entry is reconciled with an approval, direct change, or necessary platform action.
  • Any correction is made through the normal workflow so the explanation remains complete.
What you seeLikely causeWhat to do next
The actor name is not the person expectedA shared account was used or a platform administrator assisted with the record.Confirm account ownership and compare the event with any open support case.
A value seems to change without an entryThe wrong record, field, date range, or filtered history view is being inspected.Clear filters and verify the exact record identifier before escalating.
Several entries show one operationA single workflow updated multiple connected fields.Read the entries as a sequence and compare their timestamps and target fields.

When to contact support. Send the school, unit, target record, approximate time, unexpected value, and what the visible history does or does not show.

Key terms in this guide

Change request
A proposed official change that keeps the current and proposed values available for review.
Change history
The attributable sequence of previous values, new values, actors, and times behind official changes.

Continue reading