Hi! Enterprise edition should get extra mobility features. One of those will allow enterprise users to distribute mobile app outside public stores and even without a need for QR code provisioning! This can give you idea what is needed to accomplish something similar. Your business customers can use third-party Mobile Device Management (MDM) solutions to help manage and distribute their apps. 3CX should also join to the AppConfig EDIT: Single Sign-On Use Case Organizations want to allow users to log into an application using their existing work credentials, as well as customize the security around the login experience to require various factors of authentication. Once a user has logged into one application successfully, that login process should automatically translate to other applications so users do not have to enter their credentials multiple times. Your idea would be next step towards SSO via SAML or JWT. It is important to note that MDM solution can be used even on small scale of just 10 managed devices with web client credentials. The following document describes the technical capabilities and deployment the native mobile 3CX app to devices based on the best practices documented by the AppConfig Community. Using this capability, the 3CX app that is in the public app store can be installed automatically or via a self-service catalog with EMM platforms participating in AppConfig Community. Alternatively, some customers may choose to build a custom app built using the Force.com[?] development platform. In this case, the resulting app will likely be deployed as an internal or in-house app. App developers builds in support for SAML (or equivalent) standard for identity federation into the mobile app and the mobile app’s backend service iOS 7+ device enrolled with Apple’s mobile device management protocol(initial release 4 years ago!) Android 5.0+ with Android for Work enrolled device App’s backend SaaS authorization service must support identity federation to an organization’s identity provider (IDP) via a standard such as SAML or OpenID Connect The Security Assertion Markup Language (SAML) is an XML-based federation technology used in some enterprise and academic use cases. OpenID Connect can satisfy these same use cases but with a simpler, JSON/REST based protocol. OpenID Connect was designed to also support native apps and mobile applications, whereas SAML was designed only for Web-based applications. SAML and OpenID Connect will likely coexist for quite some time, with each being deployed in situations where they make sense.