Operations manual

How to configure and operate the policy and procedure management system: setting up approval workflows, finding the audit trail, granting permissions, and revising policies that are already published.

How this manual is produced

Every page is generated from the application's own source code. A merge that changes what the application does regenerates the pages that describe it, and the screenshots are re-taken from a running copy rather than pasted in — so a control that moves or is renamed breaks the build instead of quietly leaving a page wrong.

Each page states the permissions a task needs and where the screen lives, both rendered directly from the code rather than written by hand.

Where a capability exists but no screen reaches it, the page says so and names what an administrator would have to call instead. It will not invent a click path.

Where the source does not settle a question, the page says that too, and the question is collected on Known gaps.

Start here

Use the search box, or pick a section from the navigation. What's new lists what changed in the application at each release, computed by comparing releases rather than written from memory.