Manage event types, leadership roles and scheduling

Maintain the event types and their flags, the leadership roles, the review rules, the order sections, the registration reasons and the scheduling settings.

Positions that currently hold this permission, and where. It can be granted: Everywhere. To change who holds it you need Grant permissions, and to hold this permission yourself, everywhere or for the same platform, event type or team.

• Unit Command Chairman Everywhere, as a post that holds every permission

Holding this permission lets you change these. All settings

• An element this big is worth a warning

  The builder warns when one element has more of its own slots than this. It never stops anyone building it.

  Key

  operations.orbat.element_size_warning

• Warn when a callsign is used twice

  Two elements with the same callsign and suffix on one ORBAT make radio traffic ambiguous.

  Key

  operations.orbat.warn_duplicate_callsigns

• Announce slots added after release

  When a leader adds slots to an ORBAT members can already see, one line goes to the event type's announce channel saying where.

  Key

  operations.orbat.announce_added_places

• At most one announcement every

  Slots added close together go out as one line, so a leader building quickly does not fill the channel.

  Key

  operations.orbat.announce_throttle_minutes

• Planned events show on the schedule

  On means drafts and events under review appear on the schedule and calendar as Planned, so nobody books the same evening twice. Each event type can still keep its drafts off.

  Key

  operations.scheduling.planned_events_visible

• Planned events show their name

  Off means a planned event is listed as "Planned operation" with its date, platform and organiser, and the name stays with the mission team until release.

  Key

  operations.scheduling.planned_event_names_visible

• A reviewer may approve their own event

  Off means someone who organises an event or holds a leadership role on it cannot be the one to approve it. On lets a small team review its own.

  Key

  operations.scheduling.reviewer_may_approve_own

• Announce channel

  Where releases and locks are announced when the event type names no channel of its own. Set per platform, with this as the fallback. Empty means nothing is posted.

  Key

  operations.scheduling.announce_channel_id

• Slot imported deployments here

  Off while the current site is still where members slot for the deployments it scheduled. Turn it on when Operations moves across; deployments planned here are slotted here either way.

  Key

  operations.slotting.slot_imported_events

• Ask reserves to confirm before lock by

  From this long before the ORBAT locks, every reserve is asked on the ORBAT whether they can still make it. Leadership sees who said yes first.

  Key

  operations.slotting.reserve_confirm_hours

• Take reserves after lock

  Members may still put their name down as a reserve after the ORBAT locks, until the deployment ends.

  Key

  operations.slotting.reserves_after_lock

• A clash stops a claim

  A member already deployed on another event at the same time cannot take a slot until they cancel their deployment there. Off, they are only warned.

  Key

  operations.slotting.clash_blocks

• An assignment waits for the member to accept

  When the field leader assigns a member who has not said they are coming, the slot is theirs once they accept it. A reserve assigned by the field leader is in at once.

  Key

  operations.slotting.assignment_needs_acceptance

• Leadership can read reasons for not attending

  Off, a member's reason and note are theirs alone: the deployment's leadership sees who is not coming, never why. A reason can be about the leadership itself.

  Key

  operations.slotting.show_absence_reasons