← Trust Center

Authentication & access

Authentication & access control

SwiftCode verifies identity on every request and scopes access to the caller's role and facility. Sign-in is centralized through SwiftCode ID — a standards-based identity layer — while authorization stays inside SwiftCode. Controls are built so that patient safety always comes first: authentication never stands in the way of an emergency.

SwiftCode ID single sign-on

Authentication is centralized on a dedicated identity provider using open standards; authorization stays in SwiftCode.

  • Sign-in uses OpenID Connect (OAuth 2.0 with PKCE) across web and native apps.
  • The identity token carries identity only — never roles or permissions; SwiftCode resolves access itself, so revoking a user or changing a role takes effect immediately.
  • The identity provider centralizes credentials, MFA, passkeys, password policy, and brute-force protection.
  • Available across all four surfaces: Command (iPad/web), Admin (web), Respond (iPhone), and Watch.

Role-based access control

Permissions are granular, database-backed, and isolated per facility.

  • Database-backed, granular per-role permissions.
  • Per-facility data isolation derived from the verified session, not from client-supplied input.

Multi-factor authentication & passkeys

Strong authentication is available through the identity provider — and it never blocks an emergency.

  • Time-based one-time-password (TOTP) multi-factor authentication.
  • Passkeys / WebAuthn support via the identity provider.
  • Enforcement is configurable for privileged and administrative roles.
  • MFA never blocks triggering an emergency code — patient safety comes first.

Session management

Sessions are short-lived, revocable server-side, and defended against reuse and brute force.

  • Short-lived, signed JWT session tokens.
  • Rotating refresh tokens with reuse detection.
  • Server-side revocation on logout, deactivation, password reset, or role change.
  • Per-account lockout and rate limiting against brute-force attempts.
  • Tokens travel in request headers and are stored in the device keychain.
  • Biometric App Lock and idle timeout on shared devices.

Password security

Credentials are hashed with a modern algorithm.

  • Passwords are bcrypt-hashed.
  • Both PIN and password sign-in are supported.

Account recovery

Recovery is administrator-assisted with a documented break-glass path.

  • Administrator-assisted password and MFA reset.
  • A documented break-glass path for recovery.

Administrative controls

Privileged actions are limited and recorded.

  • Administrative actions are restricted.
  • Administrative actions are recorded via audit middleware.

Control status

An honest summary of where each control stands today.

SwiftCode ID single sign-on (OpenID Connect / OAuth 2.0 + PKCE)

Implemented

Multi-factor authentication (TOTP)

Implemented

Passkeys / WebAuthn

Implemented

Role-based access control

Implemented

Immediate revocation (no permissions in tokens)

Implemented

Enterprise SSO federation to your IdP (SAML / OIDC)

Available on request during a pilot.

Planned
Configured per facility: authentication enforcement (MFA/passkey policy, session lifetime, lockout) is set per facility during onboarding. Enterprise SSO federation to your own identity provider can be discussed during procurement.

Evaluating SwiftCode for your facility?

Enterprise customers may request our security questionnaire, architecture overview, and pilot materials during procurement — under NDA where required.

Security questions? security@swiftcode.tech