# Public Beta - Quickstart {% hint style="success" %} **Secure Contacts App 3.0 is here** 🎉 Released on **18 September 2025 - available in** [**AppStore**](https://apps.apple.com/de/app/secure-contacts/id1617596880) **/** [**PlayStore**](https://play.google.com/store/apps/details?id=de.provectus.securecontacts.droid) {% endhint %} ## Welcome to the public beta of SCA 3.0. Discover what’s new in this release - [click here to learn more](/sca-3.0-public-beta/whats-new-in-sca-3.0.md).
## Downloading the Beta Version The **beta** version of Secure Contacts 3.0 can be downloaded via Apple’s TestFlight app or the Google Play Store. * iOS link: [SCA 3.0 beta @ Apple's TestFlight](https://testflight.apple.com/join/X4TU6ZRK) * Android link: [SCA 3.0 beta @ Google's PlayStore](https://play.google.com/store/apps/details?id=de.provectus.securecontacts.droid) {% hint style="success" %} Installation Prerequisite: To install the SCA 3.0 Beta, users must be allowed to install new apps on their device.\ This must not be restricted by MDM (Mobile Device Management) policies. {% endhint %} ## Installing the SCA 3.0 Beta On **iOS**, the beta version can be installed manually for both management types: * **Managed Apps (MAM)** * **Managed Devices (MDM)** with some limitations On **Android**, the beta version can only be installed manually for management type: * **Managed Apps (MAM)** {% hint style="warning" %} **Note:** Pushing or auto-install of beta versions via your MDM system will not work. Most MDM solutions require that apps come from the official app stores. Therefore, beta versions must be manually installed. {% endhint %} {% hint style="danger" %} Installing SCA 3.0 Beta will overwrite any existing SCA 2.0 installation on the user's device. {% endhint %} ## App Configuration for SCA 3.0 Beta Secure Contacts 3.0 uses the same AppConfig settings as version 2.0. Any existing configurations for SCA 2.0 in your policies will still be recognized. As well as your SCA License. With version 3.0, additional AppConfig settings have been introduced, and some legacy ones have been removed. Please refer to the [documentation](/sca-3.0-public-beta/whats-new-in-sca-3.0.md) for details. When using management type "**Managed Apps" (MAM)**, whether on iOS or Android, SCA 3.0 can access and apply AppConfig policy settings without issue. When using management type "**Managed Devices" (MDM) on IOS**, certain limitations may apply - particularly if **SCA 2.0** is **already** defined as the target version in your MDM system configuration. Some MDM systems (e.g., Microsoft Intune and others) may not apply AppConfig settings if a different app version is installed on the device than the one defined in the MDM system. This can lead to errors such as “no applicable,” meaning the AppConfig will no longer be actively pushed. **What does this mean?** If you install SCA 3.0 over SCA 2.0, the older AppConfig might still be on the device. SCA 3.0 will be able to use this exact configuration since it was transferred before the update, even if the MDM doesn't push it again. However, if you need to **modify or customize the AppConfig** for use with SCA 3.0, while **SCA 2.0** is **still** defined as the target version in your MDM system, follow this sequence: 1. Ensure **SCA 2.0 is installed** on the device. 2. Make and **save your changes** in the AppConfig settings via your MDM system. 3. **Verify** that the updated configuration is successfully applied to the device. 4. Once confirmed, install **SCA 3.0 over the existing SCA 2.0**. This ensures that the updated AppConfig is present and will be recognized by SCA 3.0. {% hint style="success" %} **This limitation only applies to management type Managed Devices (MDM) for iOS** {% endhint %} **Why is this important?** Because some of the new features in **SCA 3.0** need to be **activated or configured** before they can be used. Additionally, the **app license** is delivered via **AppConfig policies**, and most of the key features in SCA 3.0 **require a valid license** to function properly. {% hint style="warning" %} **Note:** This AppConfig limitation for **Managed Devices (MDM)** will no longer apply once **SCA 3.0 is officially released to the public app stores** and defined as the target version in your MDM system. {% endhint %} ## Create and Edit personal outlook contacts in SCA 3.0 With SCA version 3.0, users can now create, edit, and delete their personal Outlook contacts directly in the app. To enable this feature, an administrator must grant consent for the newly added permission **`Contacts.ReadWrite`** to the [SCA Enterprise App](/documentation/authentication/enterprise-application.md). ⚠️ Go to and sign in with a **Global Administrator** or **Privileged Role Administrator** account. In the left menu, select **Enterprise Applications**, then find and select **Secure Contacts App**. Open **Permissions**, click **Refresh**, and then click on **Grant admin consent for …**. Wait a few seconds, then verify that the permission with the claim value **`Contacts.ReadWrite`** appears in the list and is marked as granted. Done. {% hint style="warning" %} **Note:** This action is only required if the [**SCA Enterprise App**](/documentation/authentication/enterprise-application.md) has already been registered and used in your Azure tenant. {% endhint %} {% hint style="success" %} If the [**SCA Enterprise App**](/documentation/authentication/enterprise-application.md) is being registered for the first time, no further action is required - all current permissions, including Contacts.ReadWrite, will be included automatically. {% endhint %} --- # Agent Instructions: 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: ``` GET https://docs.secure-contacts.com/sca-3.0-public-beta/public-beta-quickstart.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.