SSE user guide
Follow the history and choose an export
Find a request, understand its activity, and distinguish the release package from the internal audit file.
Use the request reference to find the case. Use its history to understand what was recorded and which copies were approved.
Find a request
Open Requests and search a reference such as OPRA-2026-0001, words from the request, or a supplied requester name. Filter by Status and change Order to show the newest, oldest, or earliest deadline.
Lists show ten rows per page and become labeled cards on smaller screens. Request details expands the full description. Request links use the reference, not the requester’s name or description.
Read activity across requests
Activity combines intake and routing, records and responses, and deadline events. Search a reference or action, choose an activity filter, or change the order. Audit details reveals the source history, original sequence, event type, recorded time, and fingerprints.
The global list searches the latest 500 entries. If more exist, the page states that limit. A request’s own history and internal audit export provide its retained evidence.
Choose the right download
For the response
Approved release package
Downloaded from Response. The ZIP contains response.txt, manifest.json, and the actual approved release files. Inspect it before using your delivery process.
For internal review
Internal audit file
Downloaded from History with Download internal audit file. It retains case evidence and can include unredacted originals. Keep it internal; it is not the requester’s release package.
Understand what verification establishes
Intake, deadline, and record-review histories keep their own event chains. Their fingerprints and snapshots support checks for inconsistencies in the recorded evidence and retained files.
A valid check does not prove that every real-world event was recorded, authenticate the staff member, verify delivery, or establish legal compliance. Review the underlying evidence as well as the verification result.
Close the request and preserve its context
After production and recorded delivery, use Close the completed request in History. Preservation holds record a retention need; they do not pause deadlines or stop response and closure actions.
The public demo is temporary even when a hold is recorded. A session reset or expiry removes that sample workspace. Read the storage and deployment limits.