AMSystem documents

The governing documents an organisation actually has to follow, searchable without exporting them first — plus a working area for analyses that span more documents than fit in one answer.

What it is

AMSystem is a third-party document management product. This integration reads whichever tenant it is pointed at: rules, regulations, processes, policies and checklists.

Alongside the reading tools it carries a working store. When an assistant is reviewing many documents at once, it can set aside text and findings under named keys and pick them up again later, rather than trying to hold everything in one conversation. That store belongs to the integration; it is not written back to AMSystem.

Use it for

• “What does our policy say about handling this kind of incident?”
• “Find every governing document that mentions this requirement.”
• “List all document titles so I can see what exists.”
• “Work through these twenty documents and collect the findings as you go.”

Tools

Function	Answers
Usage guide	How search, retrieval and the working store fit together — the assistant reads this first
Search documents	Governing documents matching a query
Get document	One document in full
List all titles	Every document title, for when search comes up thin
Working store — text	Set aside, retrieve, delete and list text under named keys
Working store — findings	Record findings, retrieve them all, clear them, and clear a whole analysis run

Data and permissions

• Read-only against AMSystem. No tool writes anything back to the document management system.
• The working store writes, but only to itself. Text and findings the assistant sets aside live in the integration, not in AMSystem, and are cleared per analysis run.
• Scoped to the tenant the integration is configured against.

Getting started

The integration needs API access to your AMSystem tenant. Talk to your Customer Success Manager.

Limitations

• Governing documents, not case files. This is the rules layer, not the operational records.
• The working store is not permanent. It exists for the duration of an analysis and is cleared; nothing there should be treated as a record.
• A governing document is only as current as its owner keeps it. The integration returns what AMSystem holds, including a policy nobody has revised.
• Search quality depends on how documents were titled and written, not on how the question was phrased.