Workflows

Run the approval workflow

Let Cadet staff propose official changes while instructors retain a clear review point.

Instructors and staff Cadets14 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.The default flow
2.Review the change, not just the requester
3.Direct-apply rights
4.When work is stuck

On this page

1. The default flow
2. Review the change, not just the requester
3. Direct-apply rights
4. When work is stuck

The default flow

1A Cadet holding an authorized position proposes a change.
2The request stores the current value beside the proposed value.
3An instructor reviews the exact difference.
4Approve applies the change; deny leaves the official record untouched.
5The Cadet is notified and the action remains attributable.

Review the change, not just the requester

The side-by-side values are the heart of the queue. Confirm the target record, the current value, and the proposed value before deciding.

A familiar requester can still select the wrong Cadet or formation. The queue protects the record only when the reviewer reads the actual difference.

Direct-apply rights

A trusted position can be allowed to skip approval for the access it has been granted. This is a property of the position, not a permanent personal privilege.

Start new holders in the queue. Add direct-apply only when the operational benefit outweighs the reduced review point, and reconsider it at turnover.

When work is stuck

Confirm the request was submitted rather than left incomplete.
Confirm an instructor is reviewing the correct unit and queue.
Check whether the target record changed after the request was created.
Use history to confirm that an apparently missing approval was not already applied.

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

Confirm the requester is acting on the intended Cadet record and from the correct unit.
Read the current and proposed values side by side; do not decide from the request title alone.
Check whether another recent request changes the same field.

Success looks like

Approval applies exactly the reviewed value; denial leaves the official record unchanged.
The requester receives a clear outcome and the decision remains attributable.
Conflicting or stale requests are resolved before later work is approved.

What you see	Likely cause	What to do next
A request is not in the queue	It was not submitted, belongs to another unit, or direct-apply authority bypassed the queue.	Check the requester’s position rights and history before submitting a duplicate.
The current value differs from the request	Another approved or direct change occurred after submission.	Re-evaluate the proposal against the current record and reject or recreate stale work as appropriate.
Approved work seems missing	The viewer is on a filtered view or the action targeted a different record.	Open the request and history to confirm target, status, and applied value.

When to contact support. Provide the request identifier or target record, status, approximate submission time, expected outcome, and the related history event if one exists.

Key terms in this guide

Position: A named unit duty that can carry permissions, scope, an assigned Cadet, and continuing work.
Direct apply: Authority for a position holder to make a permitted change without waiting for instructor approval.
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

Configure positions and permissions

Build a chain of command where responsibility and access survive annual turnover.