Security overview
Shift Relay holds operational information that organizations are accountable for. The architecture assumes that access control has to hold up even when the interface is bypassed entirely.
Every organization-owned record carries an organization identifier, and access is enforced by row-level security policies in the database rather than by the interface. A user who is not a member of an organization cannot read its records through any path.
Organization Owner, Administrator, Command Staff, Supervisor, Member and Read-Only Auditor each have a defined capability set. Permission checks run server-side; hiding a control in the interface is never the enforcement mechanism.
Email and password sign-in with email verification, password recovery and session expiration handling. Sessions are held in secure browser storage and validated on every privileged request.
Sign-in security events, role changes, briefing publication and acknowledgment, shift opening and closing, handoff publication, review, acceptance, reassignment and resolution, asset status changes, administrative corrections and exports are all recorded. Normal users cannot modify audit records.
Mutations are validated against shared schemas before they reach the database. Rich text is sanitized, and error messages returned to the browser avoid leaking internal detail.
Storage paths are organization-scoped, buckets are never publicly readable, and authorization is checked before upload and download. File type and size are validated, and sensitive downloads can be recorded in the audit trail.
Generated drafts use only records the requesting user is already permitted to read, cite their sources, and never publish, assign, acknowledge, close or delete anything. Uploaded documents are treated as untrusted content and instructions inside them are never executed.
Privileged credentials and AI provider keys are read only in server-side code. No service credential is included in the browser bundle.
Stated plainly
Shift Relay is not marketed as CJIS compliant and holds no compliance certification at this stage. It is designed with tenant isolation, least-privilege access, auditability and retention controls so that formal compliance work has a credible foundation. It is not an evidence management system, and it should not be used to store criminal history data, NCIC returns or protected health information.
No external integration is represented as connected until it has actually been configured. Connector states are shown explicitly as not configured, configuration incomplete, connected, error or disabled.
Ask a security question →Shift Relay is in early access for organizations that run around the clock. Tell us how your shifts change hands and we will show you the workflow end to end.