BSN.Cloud offers a robust set of permissions features that allow you to protect your content and maintain the efficiency of your digital signage system. These security features are scalable: you can choose exactly how complex you want your permissions system to be depending on the needs of your organization. 

 has a set of operations permissions, which are not editable, and their main purpose is to represent different job responsibilities within a company. If you need a different set of permissions, you can add 

, which allow you to adjust permissions as needed. Aspects of this system are described in more depth on these child pages in this section.

For instructions on using roles in BrightSign Control, see 

. For instructions on using roles in BrightAuthor:connected, see 

 (for information on using object permissions).

 cannot be controlled by user permissions. This means that any user, regardless of their role, will be able to see all setup packages, create and manage provisions, and register players. If this is not appropriate for your needs, consider creating separate networks for users who should not share this functionality.

Scheduling and Publishing

System Roles and Permissions

This is our legacy cloud platform. Our latest cloud platform is BSN.Cloud which consists of the free bsn.Control and the paid bsn.Content tiers. Development of BSN has largely ceased and will eventually be deprecated and replaced with BSN.Cloud.

BrightSign_Network_BSN

BrightSign’s *legacy* app for authoring and managing players. The app's actual name is BrightAuthor but is referred to as BrightAuthor Classic to lessen confusion with BrightAuthor:connected, our latest app.

BrightAuthor_Classic

BrightSign’s latest free, all-in-one app for player setup / management, authoring, and content management.

BrightAuthorconnected

The BSN.Cloud record of a player and its Setup. The Default Setup is assigned to the player unless another Setup has been explicitly set.

Provision_Record

The process where a Setup is delivered and applied to a player by BSN.Cloud.

Provision

A set of files containing player settings (player name, description, time zone, Publishing Mode, network settings, etc.) and an autorun.brs file which instructs the player what to do upon bootup.

Setup

Info

Your documentation's source code where all files and their history are stored. The web editor connects to your documentation repository to access and modify content, or you can edit files locally in your preferred IDE.

repositoryyyyy

TestVASVariable

Are like departments for your users. You can create different groups (like Engineers, Marketing, or Management) and assign users to them. This helps you organize your users and give them different access levels to different parts of your organization

User_Groups

Connect multiple published Spaces for easy navigation between docs (e.g., User Guides, API docs). Add links in Space settings, label them, and publish. Changes to links automatically update across connected Spaces. 

Space_Links

Think of them as folders for your Spaces. You start with one called "Spaces." Make more folders if you need them. You can add, rename, or delete folders (but only if they're empty). To put a Space in a folder, just drag it there, use the move action,

Space_Group

Containers for documents organized by teams or projects. Each account has a personal space, and organizations can create custom ones with access control.

Spaces

Building blocks for your docs. Think of them as Legos for your content. You can use them to create headings, tables, images, code snippets, and more. There are basic, media, developer, and embedded blocks to choose from.

Blocks

dasdasdasdasdasda11

dsadasd3213dd

Glossary lets you define every tricky term, then gives them a sneak peek explanation on hover... Just like I'm doing with this text right here!

Glossary

variable_test_video

variable123

silviu

Bogdan_test

ferwhethgte

target1

google

test

support

product_name

specific

var_miha

new_var_2

new_mih_var

mih_var

This is a plain text that will be inserted in an expandable heading for using this raw as an exampl

testheight

available

testulet

testvar

altscenario

This is a plain text that will be inserted in an expandable heading for using this raw as an example

scenario

exemplu

variabila

Archbee

text

refresh_token

YourBank

MyBank

SEFAS

uptempo

customerName

testName

name1

customername

apilink1-getallmethod

variable_one

capitalize

company_name_adobe

jama_2

jama_1

domain

email

product

programName

customerName1

productName

IntelliSense

GoPilot

DynamicData

JigxApp

HomeHub

JigxManagement

VSCode

JigxBuilder

Jigx

Terms.DryMatter

Terms.WebOnly

Terms.MobileOnly

Terms.NewFeature

Pen.Building.Blocks

Terms.Releases

Terms.Release

Terms.Version

Items.89TECH

Items.87AGE

Items.86DSLH

Items.84RPRO

Items.83VETC

Items.82TODAY

Items.79DCC

Items.78DUE

Items.77DDRY

Items.76DOPN

Items.75DIM

Items.74NOTE

Items.73XDAT

Items.72COD2

Items.71COD1

Items.70CODA

Items.69CALF3

System Roles

User Guides

Languages

Network Status

BSN.Cloud Status

Dashboard and Menus

Undocking Panels

Tagging

Content

Event Properties

Zones

Commands & Conditional Targets

Presentation Settings

Tree View

State Properties

Presentation

Schedule

Network

Users

Roles

Setup Library

Activate

Subscriptions

Preferences

Admin

Unsupported Features

BrightSign Author (BrightAuthor:connected)

Service Status

Players

Users and Roles

Management

Details

Members

Invitations

Domains

Settings

Organizations

Applications (API Access)

Account

Registration

Setup File Library

Provisioning

Player Setup

BrightSign Control

Prerequisites

bsn.Control

Getting Started with bsn.Content

Managing Content

Creating a Presentation

bsn.Content

Custom Roles

Object Permissions

Cloud Data Limits

BSN.Cloud

Using Zipit

Connect Your Modem

Activate Your Modem

Supported Countries

BrightSign Mobile FAQs

View Signal Strength

Data Plans

BrightSign Mobile