> For the complete documentation index, see [llms.txt](https://newdocs.keeper.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://newdocs.keeper.io/en/release-notes/mobile/android/android-version-18.0.0.md).
# Android Version 18.0.0
### Enhancements
#### **Nested Shared Folders With Role-Based Folder Permissions**
Keeper introduces Nested Shared Folders with Role-Based Folder Permissions on Android, a complete redesign of how you organize, share, and protect your records. You can now build folders and subfolders up to five levels deep, so your vault reflects the way your team actually works instead of forcing everything into a flat list.
Permissions flow down automatically from a parent folder through every subfolder and record inside it, so a single sharing decision applies consistently across an entire branch, with the flexibility to make precise exceptions wherever you need them. When more than one permission applies, the most specific one wins: a permission set directly on a record takes priority over one set on its folder, which in turn takes priority over a permission inherited from a parent folder.
Role-based permissions give you granular control over exactly who can view, edit, share, and manage content at every level, and share managers can add users and teams, make bulk permission changes, set access to expire on a chosen date, or revoke it entirely, though no one can grant access higher than their own.
Creating a folder is simpler too: just tap Create New Folder. There's no longer a separate choice between a regular and a shared folder, and you simply tap Share whenever you want to share one.
This new system runs alongside the existing Classic folder system, with two distinct folder icons so you can always tell them apart, and a Classic option remains available when you need compatibility with older workflows.
{% hint style="info" %}
This feature is currently available by invitation only. To request access or learn more, please contact your Keeper representative or visit [keepersecurity.com/contact](https://www.keepersecurity.com/contact.html).
{% endhint %}
* **AN-9318**: The Notification Center icon now gently pulses when you have new, unread notifications that need your attention, such as an approval request with Approve or Deny buttons. The animation draws your eye to time-sensitive items the moment they arrive, including when they're waiting for you as the app launches, and stops automatically once you open the Notification Center or there's nothing left that needs action.
* **AN-9377**: Keeper can now fill your saved logins directly into the Microsoft Outlook and Microsoft Authenticator apps, so signing in is faster wherever you work. To keep your records accurate and avoid clutter, Keeper fills your existing credentials in these apps without prompting you to save new ones.
* **AN-9280**: Keeper now supports viewing the new PAM Cloud record type on Android, used for secure, just-in-time access to cloud provider environments such as AWS, Azure, and Google Cloud, as well as SaaS applications. You can open these records on your device and see their details, including login URL, account identifier, and configuration, in a clean, read-only view consistent with other PAM record types.
* **AN-9252**: We refreshed the Keeper logo across the Android app for a cleaner, more modern look, including the login and splash screens, the manual Autofill sheet, the Autofill search screen, and the Wear OS companion app.
### Bugs
* AN-8814: Corrected an issue where a record's type icon could fail to update after a record with an attachment was converted to the newer record format.
* AN-9287: Fixed a brief flicker of the red notification badge that could appear when new notifications synced to your device.
* AN-9248: Resolved a crash that could occur during account switching when removing a user and then adding a third account.
\
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://newdocs.keeper.io/en/release-notes/mobile/android/android-version-18.0.0.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.