---
title: Adding Partner CMS Players to  Networks
slug: develop/adding-partner-cms-players-to-networks
docTags: 
createdAt: 2025-03-11T07:00:15.332Z
---

Players that are configured for a partner CMS application can also use a BSN.Cloud network connection to access players for configuration and maintenance. To do this, temporary replace the partner CMS autorun with an *autorun*.*brs* that can make the changes needed to connect to BSN.Cloud. This process is described below.

:::hint{type="warning"}
Players cannot be migrated from one BSN.Cloud network to another unless the player provisioning record is first deleted from the old network and created in the new network (see [Provision](docId\:Cyl9kPm02CO5rgcB9WQQv) for more information). Otherwise, the player will remain in the old network.
:::

# Prerequisites

1. You must be able to access the player on the local DWS through a browser.
2. You must know the name of the target BSN.Cloud network.
3. You will need a registration token. See the Appendix for instructions.
4. After getting the token, you must download the *cloudParameters.json* file from the Appendix and customize it:
   - Edit line 9 to add the registration token.
   - Edit line 10 to add the target network name, then save the file.

## Replace the Autorun and Reboot the Player

1. Open the local DWS for the player you are adding to BSN.Cloud and go to the **SD** tab.
   - Upload the *cloudParameters.json* file to the SD card.
   - Download and open the *standalone-autorun.brs* file in the Appendix. If you saved the *cloudParameters.json* file under a different name on the SD card, make sure that line 4 of *standalone-autorun.brs* references the correct name.
   - Upload the *standalone-autorun.brs* to the SD card.
2. Go to the **SD** tab in the local DWS and locate the *autorun.brs* file.  
3. Select the cogs icon, shown in Image 1, to go to the **Rename** section:
   - Rename *autorun.brs* to *autorun.backup*
   - Rename *standalone-autorun.brs* to *autorun.brs.*
4. Go to the **Control** tab in the local DWS and reboot the player.
5. The player will appear in the BrightAuthor\:connected **Network** tab when it has rebooted, and the *autorun.brs* will again reference the partner CMS application.

![image-20240305-163734.png](https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/1FT_hL8__fNRj36kXP0bN_image-20240305-163734.png)

# Appendix

## BRS and JSON Files

::File{src="https://api.archbee.com/api/presign/0prk6SO2dy9LdU77jB8D1/eAwbh0SjYtO_nFGJb2Zl2_cloudparameters.json" label="cloudParameters.json" isUploading="false"}

::File{src="https://api.archbee.com/api/presign/0prk6SO2dy9LdU77jB8D1/WZUo69-mIN0WR5xTnTdgO_standalone-autorun.brs" label="standalone-autorun.brs" isUploading="false"}

## Get a Registration Token through BSN.Cloud

1. Create a new setup package with BSN.Cloud.
2. Select **Save Setup** and choose a location to save the package on your computer.
3. Open the folder where you saved the package and open the *current-sync.json* file.
4. At the top of the file you will find similar script to Image 2. The long string after `"bsnRegistrationToken"`, is your registration token. The string after “account” should match your target network name inserted in step 4c.

![Screenshot 2024-03-05 at 8.28.20 AM.png](https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/BUS5yj22a8A9lSk3if8Uz_screenshot-2024-03-05-at-82820-am.png)

## Get a Registration Token through an API

First get your OAuth token correctly issued for the target network, then see [Token Entity (v3)](docId\:xFtPKROWdWpe6DqhYNwfE).