Unit Command
Policy and Guidance
Unit Command
Permissions What this team can do, and which posts carry each.
-
Permissions
- All
-
Sensitive
- 5
-
Posts carrying them
- 4
What this team can do
Everything
A permission lets someone do something on the site beyond taking part. It comes with a post: whoever holds the post can do it, and stops when they leave.
Chairman can do everything
Every permission there is, including any added later.
-
Promote ORBAT rules Sensitive
Make an ORBAT rule required, or advisory again, and change a required rule, on the team that owns the role's combat area or everywhere. A required rule stops an ORBAT being published. When more than one must agree, ask and agree here.
Chairman, Commanding Officer, Executive Officer, Senior Enlisted Leader
-
Set ORBAT rules Sensitive
Write the advisory rules the ORBAT builder checks for a role (where it may sit, how many per unit, who it needs or keeps apart) on the team that owns its combat area, and, held everywhere, for unit types too. Every new rule starts advisory.
Chairman, Commanding Officer, Executive Officer, Senior Enlisted Leader
-
Edit role cards Sensitive
Choose the Force Manual documents and passages on the role cards of the team's combat areas, which roles each card reads, and each card's status on each platform.
Chairman, Commanding Officer, Executive Officer, Senior Enlisted Leader
-
Manage roles, combat areas and domains Sensitive
Add, edit and retire ORBAT roles, combat areas and training domains in the Roles centre.
Chairman, Commanding Officer, Executive Officer, Senior Enlisted Leader
-
Set the limits every training team works within on a platform, the platform's own ladder, and open access for a trial period.
Chairman, Commanding Officer, Executive Officer, Senior Enlisted Leader