Platform reference

Cadet position permission reference

A precise reference for every current permission, its scope, its parent dependencies, and whether the corresponding product surface is live.

Instructors20 minute readManage Unit → Positions → PermissionsVerified against the live product · August 2026

Guide at a glance

How to use this guide

Start with

Use this as a precise reference. Check the named surface, role, domain, and availability state against your situation.

By the end

You can distinguish current behavior from planned capability and know which product surface owns the action.

1.Roster and requests
2.Structure hierarchy
3.Live operational permissions
4.Permissions reserved for planned features
5.Parent permissions revoke their children
6.Permission review at turnover

On this page

1. Roster and requests
2. Structure hierarchy
3. Live operational permissions
4. Permissions reserved for planned features
5. Parent permissions revoke their children
6. Permission review at turnover

Roster and requests

Permission	Effect
Can add Cadets	Allows creation of a new roster record. Existing-record edits use relative authority and need no view permission.
Can skip requests	Applies unit structure, position, and award edits directly. Never bypasses relative authority on Cadet records.
Can review requests	Participates in the unit-level structure, position, and award review ladder.

Structure hierarchy

Permission	Scope
Can manage assigned unit structure	Opens the structure-management family for the Cadet’s assignment.
Can view assigned battalion	Reads the assigned top-level formation.
Can manage assigned battalion	Edits its identity such as logo and motto.
Can view assigned company	Reads the assigned company-level formation.
Can manage assigned company	Edits that company.
Can manage all companies	Lifts company editing across the unit.

Live operational permissions

Permission	Current feature
Can manage the calendar	Create, edit, delete, design, and publish calendar output.
Can manage reports	Build, edit, print, and export roster-backed reports.
Can manage fundraisers	Create and operate fundraisers.
Can manage blood drives	Start drives; named organizers manage their specific drive.
Can manage forms	Create forms and read responses; authors retain their own forms.

Permissions reserved for planned features

Permission	Navigation status
Can manage operation orders	OPs Orders is shown as Soon.
Can manage award orders	Award Orders is shown as Soon.
Can manage attendance	Attendance is shown as Soon.
Can manage inventory	Inventory is shown as Soon.
Can manage certificates	Certificates is shown as Soon.

Parent permissions revoke their children

The editor represents related structure grants as a tree. Turning off a parent also clears the descendants it gated so hidden residual authority cannot remain stored.

Review the complete tree after changing a senior structure permission or copying a position template.

Permission review at turnover

Access follows the position to its new holder. That is useful only when the position definition is still appropriate.

Review sensitive grants—request bypass, reports, public publishing, forms, and campaigns—before or at each change of command.

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.
Scope: The records or formations within which a permission, report, tool, or action applies.

Continue reading

Configure positions and permissions

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