A library consortium documents every SOAR action that can modify production mailboxes. What integration governance practice is that?

A library consortium that documents every SOAR action that can modify production mailboxes is maintaining a change inventory of write integrations. Mailbox deletes, forwards, and purges affect evidence, patron communications, and staff continuity; an inventory makes those capabilities visible to governance, legal, and IR leads. Maintaining a change inventory of SOAR read integrations that monitor civic mailbox activity tracks read-only visibility, not write capability; it does not capture every SOAR write action that can modify production mailboxes in the civic automation estate.

Why the other options fail by concept: Maintaining a change inventory of SOAR read integrations that monitor civic mailbox activity is a read-visibility register, not a write-action inventory; it does not maintain a register of every SOAR write action that can modify production mailboxes. Maintaining a change inventory of SOAR approval decisions for proposed mailbox automation is a governance-decision log, not an inventory of write integrations; it does not document which automation actions can modify production mailboxes. Maintaining a change inventory of SOAR sandbox tests for mailbox playbooks before deployment tracks pre-release testing, not production write capability; it does not give local owners a consortium-level register of every write action that can touch production mailboxes.

Exam caveat: An inventory documents capability; it does not by itself prevent misuse—pair it with least privilege, approvals, and versioned playbook review. Operational check: maintain a living register of SOAR write actions against mailboxes, require change tickets for additions, and periodically reconcile the inventory against live connector scopes and playbook steps.