Workflows

Relative authority on Cadet records

The three-axis rule that decides whether a Cadet edit applies immediately or becomes a request—and why no permission bypasses seniority.

Instructors and Cadet staff18 minute readCadet editor and RequestsVerified 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.Visibility and editing authority are separate
2.The editor must match or beat all three axes
3.The proposed outcome also sets the bar
4.What position permissions do—and do not do
5.Authority is recalculated live
6.Worked examples

On this page

1. Visibility and editing authority are separate
2. The editor must match or beat all three axes
3. The proposed outcome also sets the bar
4. What position permissions do—and do not do
5. Authority is recalculated live
6. Worked examples

Visibility and editing authority are separate

Every Cadet can reach the roster and inspect Cadet records. The system does not hide senior Cadets merely because a junior cannot change them directly.

What differs is the outcome of Save: direct application or a change request.

The editor must match or beat all three axes

Axis	How it is measured
Position	The resolved authority rank of the held position; zero when no position is held.
Course level	LET for JROTC or the configured ROTC course-level equivalent.
Cadet rank	The position of the rank in the active branch’s rank ladder.

The proposed outcome also sets the bar

Authority is checked against both the target’s current standing and the standing the surviving changes would create. A promotion therefore requires authority over the destination rank, not merely the rank being left.

The requirement is the per-axis maximum. Matching two axes and falling short on one still produces a request.

What position permissions do—and do not do

Can add Cadets gates a new record because there is no existing target to compare. Can skip requests applies to unit structure, positions, and awards.

Can skip requests cannot grant authority over a senior Cadet record. No position flag buys a way around the three-axis rule.

Authority is recalculated live

The application recalculates which actions to show as the request changes. The server repeats the calculation inside the final transaction before applying anything.

Denying a promotion field can lower the remaining requirement; adding a more senior outcome can raise it. Contributor seniority alone does neither.

Worked examples

A Cadet equal on position and rank but lower in course level submits a request.
A peer may apply an address correction only if they match or beat all three current axes.
A promotion to a rank above the reviewer raises the rank requirement immediately.
An instructor always clears the unit authority model, but their action is still logged.

Key terms in this guide

Cadet record: The unit’s authoritative operational record for one Cadet; it is separate from the account used to sign in.
Position: A named unit duty that can carry permissions, scope, an assigned Cadet, and continuing work.
Change request: A proposed official change that keeps the current and proposed values available for review.

Continue reading

Collaborative change requests, review, and conflict resolution

The full request lifecycle: contributions, field-level decisions, authority requirements, chain review, conflicts, merge, and closure.