Military OS product walkthrough
Produced September 17, 2026, using synthetic local captures from September 13, 2026.

Chapter management
This walkthrough covers chapter administration and the permission boundaries around local officers, using a demonstration organisation and synthetic records.
Start in the chapter directory. Association operators can create and govern chapters here; the Enter admin link opens the tools for one selected chapter.

1. Enter a chapter workspace
The chapter workspace is scoped to one chapter. It brings the local roster, the current president, chapter stories and the chapter page links into one operating view.
A chapter admin assignment is an explicit application permission scoped to this chapter. It is separate from association-wide administration and does not create access to unrelated chapters.

2. Assign dated officer terms
Each leadership assignment records a person, a chapter and inclusive start and end dates. The chapter president is held on the chapter record; the other four officer titles are scoped assignments.
These titles describe chapter leadership and visibility. A vice president, treasurer, secretary or membership chair does not receive broad application permissions just because the title is assigned.

3. Apply the access boundary
The active, dated chapter president is the chapter's organisational owner and can manage that chapter's local operations. The same local scope flows into chapter event editing and chapter event sales where the product allows it.
Other officer titles remain leadership records unless the person also receives an explicit scoped permission such as Chapter Admin or chapter-scoped Events Admin. Global chapter creation and association-wide controls stay outside this scope.

4. Review readiness
Chapter officer readiness reviews every active chapter for current, soon-to-expire, expired or missing required positions. The readiness view gives membership operators a single place to identify the next assignment that needs attention.
Visible officer aliases can change how a position is labelled, but they do not create new permissions or change the fixed internal role keys. The result is a clear local chain of responsibility with dates and scope attached.