906e2ca0dd
* initial commit
* adding quotes for the array error
* Create Gemfile
* Create Gemfile.lock
* add .nvmrc and .node-version
* removed /article from URL
* update links to work with netlify
* more fixed links
* link fixes
* update bad links
* Update netlify.toml
toml test for redirects
* article redirect
* link fixes
* Update index.html
* Update netlify.toml
* Update _config.yml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* Update netlify.toml
* add article back into URL for launch
* Update netlify.toml
* Update netlify.toml
* add order to categories front matter
* Update netlify.toml
* update
* sidemenu update
* Revert "sidemenu update"
This reverts commit 5441c3d35c.
* update order prop
* Navbar updates per Gary and compiler warnings
* font/style tweaks
* Update sidebar.html
* Stage Release Documentation (#739)
* initial drafts
* rewrite Custom Fields article to prioritize new context-menu option & better organize ancillary information
* edit
* edit
* Custom Field Context Menu & CAPTCHA item in release notes
* SSO relink event
* update rn
* small edits
* improve release notes titles
* fix side menu
* Edits courtest of mportune!
* update order
* link fixes
* link cleanup
* image updates and a link
* fix trailing slash
Co-authored-by: DanHillesheim <79476558+DanHillesheim@users.noreply.github.com>
2.4 KiB
layout, title, categories, featured, popular, tags, order
| layout | title | categories | featured | popular | tags | order | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| article | Vault Timeout Options |
|
false | false |
|
14 |
Vault Timeout behavior will determine how your Vault will behave after a customizable period of inactivity. Timeout is configured individually from and for each Bitwarden client application that you use (Mobile, Web, Desktop, Browser Extension, etc.).
{% callout warning %} Regardless of Vault Timeout settings, closing the Browser or Browser Tab will end your Web Vault or Browser Extension session, meaning you'll be required to log in to access your Vault.
If you're using a Browser Extension, you can bypass this by enabling the Unlock with PIN option and unchecking the Lock with master password on browser restart checkbox. {% endcallout %}
Options
You can configure the following options from the Settings menu of any Bitwarden client application:
Vault Timeout (time-constraint)
Configuring this option will dictate how long Bitwarden can be inactive before timing-out. "Inactivity" is determined by the time since interacting with Bitwarden, not system idle time.
Each client application will have unique options (e.g. On System Idle, or On App Restart), however all applications include standard time-based options (e.g. 1 minute, 15 minutes, 1 hour).
Vault Timeout Action
Configuring this option will dictate what Bitwarden will do once the Vault Timeout time-constraint has lapsed. Bitwarden can either:
-
Lock (default).
Locking your Vault will maintain Vault data on the device. You will only be prompted to enter your Master Password to decrypt your Vault, however no Two-step Login method will be required to unlock your Vault.
Bitwarden client applications don't need to be online to unlock.
{% callout warning %} Due to the storage and reference of your decryption keys within the Web Vault, using the Browser refresh button on the Web Vault will cause it to lock. {% endcallout %}
-
Log Out.
Logging Out of your Vault completely removes all Vault data from your device, and will therefore require you to re-authenticate to access your Vault. You will be required to enter your Email Address, Master Password, and any enabled Two-step Login method in order to access your Vault.
Bitwarden client applications must be online to log in.