Partners are highly encouraged to take advantage of the free, yet powerful, tools offered by the Control Cloud. There are The two most common ways that for partners can to utilize the Control Cloud . Both offer full control of the CMS UI that end users will interact with while also providing partners with essential capabilities like player provisioning, remote diagnostics, and more.
Control Cloud Integration
This method will appeal to many partners because the services and features of the Control Cloud can be accessed using the partner CMS' UI enabling the partners' end users to have a single UI for authoring, publishing, content management, and player management.
...
Control Cloud “Swivel”
Some partners may desire the capabilities of the Control Cloud but are not yet ready for full integration with it. These partners can offer the Control Cloud alongside their CMS.
...
are:
The “Swivel Chair” approach
API integration between the partner CMS and the Control Cloud
“Swivel Chair”
One of the easiest ways for a partner to get up and running is with the “Swivel Chair” approach. With this method, end users utilize the Control Cloud alongside the partner CMS.
...
With this architecture, end users have full access to the capabilities of the Control Cloud via the default Control Cloud web interface, accessible at control.bsn.cloud. By having a one browser tab for the CMS and a another browser tab for the Control Cloud, users can quickly “swivel” back and forth between the CMS and Control Cloud.
...
API Integration
With this method, the partner CMS integrates with the Control Cloud using APIs. End users will have a single user interface for player management as well as authoring, publishing, and content management.
...
Next, let’s take a look at how the Control Cloud can used to remotely provision players.players can be remotely provisioned for the App URL publishing mode.