> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/mobile/apple-ios/older/ios-version-14.11.0.md). # iOS Version 14.11.0 Released July 17, 2020 ## Features & Benefits * **Privacy Screen -** Admins now have the ability to control the viewing (unmasking) of passwords based on a specified domain. This policy is enforceable by the Admin for individual domains within each of their Generated Password Complexity settings by enabling "Apply Privacy Screen". * **Logins Visible in Vault View -** Each record's username/email are now visible in the "All Records" view of the vault, making it easier for users to locate a record when they have multiple logins for a single site. ## Bug Fixes * **Fixed:** A message reading "A Wi-Fi or Data Connection is required" replaces the existing "client update" message at the login screen. * **Fixed:** A crash occurs when attempting to restore deleted records. * **Fixed:** Although changes are not saved, an error message fails to appear when a user attempts to modify a record when they lack record permissions. * **Fixed:** Restoring a record takes longer than it should when a user's vault exceeds 500 records. * **Fixed:** Various design issues. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.keeper.io/release-notes/jp/mobile/apple-ios/older/ios-version-14.11.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.