The Workspace API checks access to shared cases and records supported actions with the acting user. The EMP Intake Teams pilot is planned for 2027, on infrastructure you control. Clients use the API rather than connecting directly to the database.
1. One door in, audit out
Remote clients connect to the Workspace API over HTTPS. The service handles database access, case permissions and the audit events that apply.
2. Why route everything through an audited edge
EMP Intake WS runs on one workstation. Teams moves permission checks and supported audit recording to the Workspace API so several workstations can use shared cases.
3. The role model and per-case access
Teams supports Owner, Manager, Contributor, Reviewer and Viewer roles. Roles govern viewing, editing and export. Case membership controls ordinary user access; Managers and Administrators retain broader workspace access.
4. Audit semantics: what gets recorded
The API records supported material case, file, export and administrative actions with the acting user and server-assigned time. The audit trail does not record every navigation step or playback action.
5. Identity, authentication, and SSO
Local accounts use invite-based onboarding, with no external identity provider required. Discuss SSO requirements when planning your pilot.
6. Operational concerns
The Workspace API is a service you run. Your administrator is responsible for service availability, storage, backups and access controls.
Running EMP Intake at team scale? The Workspace API is what makes shared cases and role-scoped access possible across the team, with supported application actions attributed in the audit trail (pilot planned for 2027). Apply to the Teams pilot →