This data flow describes how data travels when a BlackBerry Dynamics app (including the BlackBerry UEM Client) is already activated on a device and is used as an easy activation delegate to activate subsequent BlackBerry Dynamics apps.

1. An administrator assigns one or more BlackBerry Dynamics apps to a user.
2. The user installs the app on the device.
3. The app performs the following actions:
   1. Queries the BlackBerry Dynamics NOC and identifies that another BlackBerry Dynamics app has already been registered and activated on the device.
   2. Requests the activation credentials from the previously activated BlackBerry Dynamics app.
4. The user approves the activation request from the previously activated app on the device.
5. The previously activated app sends the credentials through the BlackBerry Infrastructure to UEM.
6. UEM sends the credentials request and the UEM URL through the BlackBerry Infrastructure to the previously activated app.
7. The previously activated app returns the credentials and the URL to the new app.
8. The new app completes the following actions:
   1. The app registers itself with the BlackBerry Dynamics NOC and receives an ID that UEM can later use to confirm with the BlackBerry Dynamics NOC that the app was successfully activated.
   2. Connects to UEM through the BlackBerry Infrastructure and establishes an end-to-end encrypted session with UEM using the EC-SPEKE protocol.

      This session can be decrypted only by the UEM instance that issued the activation credentials.

   3. Sends the activation request through the secured session.
9. UEM verifies the activation request and sends an encrypted activation response to the app. The activation response includes data required by the app to communicate with UEM, including a client certificate, master session key, list of BlackBerry Proxy instances, and trusted certificate authorities.