Emergency access

Emergency access lets trusted contacts request limited access without ever signing in as the owner.

Core rule

Emergency contacts use their own Atlas account. They never receive the owner's password, never impersonate the owner, and only receive access within the owner-approved emergency scope.

How setup works

  1. The owner invites a trusted contact by email.
  2. The contact signs into their own Atlas account.
  3. The contact must verify their email and enable an authenticator app before accepting.
  4. The owner sets a waiting period, an access window, instructions, and scope labels.

Waiting period vs access window

The waiting period is how long Atlas waits after a request before default access can activate if the owner does not respond. The access window is how long the approved emergency grant remains usable.

For example: an 8-hour waiting period and 30-day access window means the contact waits 8 hours before default activation, then can return during the 30-day grant using restricted emergency access.

Reason codes

Contacts choose a reason such as medical emergency, death / estate, incapacitated, unreachable, or other. The reason and details are logged and shown to the owner for approval or denial.

What is available today

Atlas currently supports invitations, accepting invitations, access requests, owner approval/denial, and audit logging. Vault-specific document access will be connected after the vault module is built.

Open Emergency access to configure contacts or request access.