> 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/mobile/apple-ios/ios-test-flight.md).

# iOS TestFlight

Availability based on scheduled releases

Prior to public release, Keeper's iOS Test Flight version provides early access to upcoming features and functionality.

To install iOS Test Flight use the link below:

{% embed url="<https://testflight.apple.com/join/DPDb3m5N>" %}

**Testing Instructions:**

1. Open the [Test Flight install page](https://testflight.apple.com/join/DPDb3m5N) link
2. Install Test Flight
3. Join the Keeper iOS Beta

Please email us at **<feedback@keepersecurity.com>** if you encounter any issues with this new version.

{% hint style="warning" %}
Important Notes:\
\
\- The Test Flight version of Keeper may or may not be available. We will update the invitation link on this page when it changes.\
\
\- If you need to switch back to the public App Store version, you should perform a local app reset. Go to your Settings app > Keeper > Reset Keeper to reset the local storage. This won't affect your stored cloud data.\
\
\- The Test Flight will eventually expire. After the Test Flight expires, we'll be live with this version on the app store, and you can just switch to the public store version.\
\
\- If you encounter any bugs or issues with this version, please email us right away at <feedback@keepersecurity.com>.
{% endhint %}


---

# 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/mobile/apple-ios/ios-test-flight.md?ask=<question>&goal=<user_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.