A court clerk IT group keeps offensive and defensive runbooks in the same wiki with role-based edit rights. What documentation control is that?

Collaborative documentation with least-privilege role-based edit rights for civic purple-team offensive and defensive runbooks is the documentation control a court clerk IT group applies when both runbook types live in one wiki. Sharing a documentation space improves purple alignment, while role-based edit rights protect offensive procedures from casual alteration and keep defensive runbooks editable by those who execute them. Least privilege on edits is the difference between useful collaboration and uncontrolled wiki chaos.

Collaborative documentation with role-based audited version history tracking for civic purple-team offensive and defensive runbooks fails by concept: the scenario defines the control as shared wiki space plus least-privilege editing, not audited version history tracking by itself. Collaborative documentation with time-boxed role-based edit rights for civic purple-team offensive and defensive runbooks fails by concept: the court clerk IT group applies persistent least-privilege editing by role, not temporary time-limited edit windows. Collaborative documentation with role-based lead-review approval publishing for civic purple-team offensive and defensive runbooks fails by concept: the described control uses role-based edit rights, not a lead-review approval publishing gate.

Exam caveat: read access and edit access should be separated—broad read for responders may be appropriate while edit remains limited to owners.

Operational check: verify offensive runbook edit is limited to designated purple leads, blue responders can read defensive runbooks, and the control is one shared wiki with role-based edits rather than time-boxed role-based edit rights, audited version history tracking alone, or lead-review approval publishing.