Documentation
Read the manual before you buy the software.
The complete OCM documentation is public. Not a sales overview, and not a gated PDF: the manuals our own customers use, the security references a reviewer would ask for, and the developer documentation for the people who will integrate with it.
Start here
The manuals
Written for the people who use the system, not for the people who sell it.
- User manual
Intake through closing, for advocates and support staff.
- Administrator manual
Configuration, users, permissions, installation.
- Feature toggles reference
Every switch in System Settings and what it does.
- Release notes
Per-version index of what shipped. Current release v9.6.0.
- What is new
Feature-by-feature breakdown of the current year.
- Aurora interface
Command palette, themes, three-pane case detail.
AI
AI documentation
Including what each feature can read, where the call goes, and what it will not do.
- Matter AI
Summarize, ask with document retrieval, draft email.
- Casey chatbot
The wiki-grounded helper that never reads case content.
- Motion drafter
Preflight gate, .docx filed on accept.
- Semantic conflict check
Catching the near-matches a string search misses.
- Audio transcription
Recordings to a case document and note.
- AI quality monitoring
What administrators can see about usage, failures and cost.
Trust
Security and authentication
The pages a security reviewer will want, published rather than sent under an agreement.
- Single sign-on
OIDC against Entra or Google.
- Authentication and sessions
Timeouts, re-auth on sensitive actions, forced password change.
- Two-factor authentication
TOTP enrollment and administrator flows.
- Ethical wall
Where the wall is enforced, and what happens when it is hit.
- Security levels
Authorization groups, office scoping, export permissions.
- Audit log
Every action recorded, and why the viewer is read-only.
Build on it
Developer references
Your technical staff do not need our permission to understand the system they are running.
- REST API
Bearer-token API over cases, contacts and activities.
- Data model
The tables your data actually lives in.
- Services and webhooks
Integration endpoints and inbound handlers.
- Template tags
Document assembly and template vocabulary.
- Report endpoints
Pulling report output programmatically.
Why it is all public
Documentation you cannot read is a claim you cannot check
Every vendor in this market will tell you their system is secure, configurable and easy to use. Only some of them will hand you the pages that let you decide for yourself.
Publishing all of it costs us the ability to be vague in a sales call, which we consider a fair trade. If something in these pages is wrong or out of date, tell us and we will fix the page.
It is also how Casey works. The in-product helper answers from these same documents and links back to the page it used, so the answer is checkable rather than confident.