Responsible access to sensitive shelter operations.
ShelterCurrent is designed around individual accounts, organization boundaries, minimal data collection, and visible accountability.
No account needed. Fictional data.Implemented access controlsIndividual accountsAdmin-only team and billing controlsOrganization-scoped accessRevocable invitations
Identity and access
- One authentication entry point serves Admin and Staff accounts.
- Administrators can invite each person by email, resend or revoke pending invitations, and disable or reactivate members.
- Server-side authorization reserves team access and billing controls for Admins.
- Production session cookies are host-only, HTTP-only, secure, limited to twelve hours, and locked after thirty minutes of inactivity.
Organization isolation
- Organization billing belongs to the organization, so Staff never need a personal subscription.
- Every tenant-owned operational record includes an organization identifier.
- The database migration forces row-level policies on tenant tables and supports an authenticated membership-discovery path.
- A separate non-owner, NOBYPASSRLS production database credential is still required before live-client use.
Launch controls still required
- Managed TOTP MFA must be enabled for every Admin and Staff account.
- Existing-organization membership remains invitation-only; public verified owner signup is a separate onboarding path.
- Signed lifecycle webhook handling is implemented; production endpoint delivery and missed-event reconciliation must be exercised.
- Restore rehearsals, client-level export controls, retention terms, and legal/privacy review must pass before real shelter-client data is accepted.
No broad compliance claim. ShelterCurrent does not use “compliant” as a marketing adjective without a defined framework, scope, evidence, and shared customer responsibilities.