What is the difference between Player Setup, Player Activation, and Player Provisioning in BrightAuthor:connected?

Player Setup/Setup Library

Setup allows you to set up a player with your desired settings and publishing type (Standalone, Local Network, BSN.cloud, or Web Folder).

The specific settings of each player that you set up will be saved to the Setup Library where they can be edited, deleted, or used for reference.  


Player Activation

When a player is first powered up and connected to a display, a QR code appears which can be used to provision it. Provisioning via the QR code will automatically apply the following Default Setup:

  • If the player is using the Control Cloud, it will be configured for DHCP with Local Network as the publishing mode.
  • If the player is using the Content Cloud, it will be configured for DHCP with BSN.cloud as the publishing mode.

If you do not want to use the Default Setup, you should first create the desired Setup to apply to your player. If you use the QR code to Setup your players and then try to change to a different Setup type, you will have to go through the re-provisioning process. See this page for more information about that process, and see Activate for more details about Player Activation.


  • If a player has already been provisioned (that is, it already has a Setup assigned to it), the QR code will not be displayed.
  • Any players that are activated are given the name from the "Default Setup" 


Player Provisioning 

Provision is the process of configuring a player (network settings, logging, etc.) and installing a player app on it. The player app tells the player what to do after booting up.

When BrightAuthor:connected is used, the player app consists of an autorun and associated files. It includes information like the publishing mode (Standalone, Local Network, Web Folder, etc.). For partners who prefer to use their own Content Management System (CMS), the player app is used to connect the player to the partner's CMS.

Publishing presentation content is separate from the provisioning process, but these steps can be combined. For example, you can deliver the player app with the content as a single package through an autorun.zip file.


Have more questions? Submit a request


Please sign in to leave a comment.
Can't find what you're looking for? Try to
Powered by Zendesk