---
title: BrightSign Control Integration
slug: develop/brightsign-control-integration
docTags: 
createdAt: 2025-03-11T07:00:15.332Z
---

Partners are highly encouraged to take advantage of the free, yet powerful, tools offered by BrightSign Control. The two most common ways for partners to use BrightSign Control are:

- The “Swivel” approach
- API integration between the partner CMS and BrightSign Control

# “Swivel” Approach

One of the easiest ways for a partner to get up and running is with the “Swivel Chair” approach. With this method, end users use BrightSign Control *alongside* the partner CMS.

![](https://api.archbee.com/api/optimize/0prk6SO2dy9LdU77jB8D1/KkbOdHKHGRjSNLMX7oyiP_screenshot-2026-08-06-at-15544-pm.png)

With this approach, end users have full access to the capabilities of BrightSign Control via the unbranded web interface at *control.bsn.cloud*. By having one browser tab for the CMS and another browser tab for BrightSign Control, users can quickly “swivel” back and forth between the CMS and BrightSign Control.

![image-20230215-213716-20240404-194936.png](https://api.archbee.com/api/optimize/511c8QBH-VHiwWnyzIwUb/AoumrJd1v3PqRy4oTPbt__image-20230215-213716-20240404-194936.png)

# API Integration

Using BrightSign’s APIs, partners are able to design their own custom user interfaces to access the underlying functions of BrightSign Control. End users will then interact with a single UI for authoring, publishing, content management, and player management.

![](https://api.archbee.com/api/optimize/0prk6SO2dy9LdU77jB8D1/mvX1klkFKZWLgFw5o9ZAd_screenshot-2026-08-06-at-15713-pm.png)

Next, let’s take a look at one of the ways BrightSign Control can used to remotely provision players.

[Next - App URL/CMS URL >](docId\:iuUye5z0AJS1MuEqSrRhW)