1
0
mirror of https://github.com/bitwarden/help synced 2026-01-18 00:13:32 +00:00
* Remove references to "Zero Trust" and downcase non-header instances of "zero knowledge"

* Morph "Link SSO" and "Access Vault using SSO" articles into a single "Using Login with SSO" one-stop-shop guide for end-users (i.e. non-configuration) + redirects + updated hyperlinks

* Update _articles/getting-started/getting-started-organizations.md

Co-authored-by: Trey Greer <61418192+tgreer-bw@users.noreply.github.com>

Co-authored-by: Trey Greer <61418192+tgreer-bw@users.noreply.github.com>
This commit is contained in:
fred_the_tech_writer
2021-09-15 13:41:17 -04:00
committed by GitHub
parent 3886c57ef4
commit d6c98a6a57
12 changed files with 63 additions and 90 deletions

View File

@@ -19,7 +19,7 @@ Establishing Emergency Access to a Vault is available for Premium users, includi
## How it Works
Emergency Access uses public key exchange and encryption/decryption to allow users to give a [trusted emergency contact](#trusted-emergency-contacts) permission to [access Vault data](#user-access) in a Zero Knowledge/Zero Trust environment:
Emergency Access uses public key exchange and encryption/decryption to allow users to give a [trusted emergency contact](#trusted-emergency-contacts) permission to [access Vault data](#user-access) in a zero knowledge environment:
1. A Bitwarden user (the *grantor*) [invites another Bitwarden user](#invite-a-trusted-emergency-contact) to become a trusted emergency contact (the *grantee*). The invitation (valid for only 5 days) specifies a [user access level](#user-access) and includes a request for the grantee's public key.
2. Grantee is notified of invitation via email and [accepts the invitation](#accept-an-invitation) to become a trusted emergency contact. On acceptance, the grantee's public key is stored with the invite.