Passwordless sign-in
Users authenticate with emailed codes and optional passkeys. There are no passwords to reuse, phish, or reset.
Security
Passwordless access. Explicit authorization.
Authentication proves identity; RCVanta still resolves access through entitlements, associations, roles, and tenant scope before data moves.
Designed for controlled visibility
Passkeys and email codes keep sign-in approachable while granular permission checks protect operational records at runtime boundaries.
Explicit authorization
Authentication proves identity; permissions still resolve by entitlement, tenant association, role, and scope on every request.
Tenant-scoped visibility
Data access keeps parent, child, program, and role boundaries intact in everyday workflows.
Audited actions
Administrative changes are written to an audit log, so who changed what and when is answerable after the fact.
Scoped API tokens
Non-interactive callers use personal access tokens that expire, name the tenants they may reach, and can never exceed their owner’s own access.
Access ends when employment does
Deactivating a person immediately invalidates their sessions and every token they hold, in every region, with no deployment required.