The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
First Published: March 20, 2015
Cisco StadiumVision Director deployments normally have a team of people who are responsible for different aspects of the site setup and event operation. For example, in addition to a system administrator, there is usually an event operator, a content manager, and a technical support person, among other personnel. Each person has different skills and needs for working with the Cisco StadiumVision Director software.
The Cisco StadiumVision Director software implements Role-Based Access Control (RBAC) to control permissions and user access to only the portions of the system for which they are trained and authorized to use. More than one user can be assigned to the same role in the software. However, only a single role can be assigned to each username.
For more details about RBAC in a multi-venue environment, see also “Role-Based Access Control for Hierarchical Management of Multiple Venues” section.
This section includes the following topics:
The Administrator role has unrestricted access to the Cisco StadiumVision Director software, and is the only role that can add users and assign RBAC privileges to them. The Administrator role is pre-configured in Cisco StadiumVision Director and cannot be deleted. However, you can change the password. You also can have more than one user assigned with Administrator privileges.
The Cisco StadiumVision administrator is the person who is responsible for deploying the Cisco StadiumVision solution throughout the venue.
The administrator has sufficient permissions to do the following functions:
Note Administrators have global access to all venues in a multi-venue environment.
Table 1 provides an overview of the roles that can be assigned by the Administrator in Cisco StadiumVision Director.
|
|
---|---|
Concessionaires have access only to the Dynamic Menu Board application, which allows modification of certain text-based and graphics items, and the background graphic on menus. All content uploaded by the concessionaire is available to all users that have sufficient permissions based on the roles assigned to them. The concessionaire role does not have permissions in the Control Panel or the Management Dashboard, and they can only see the DMB themes that they create. |
|
Content Managers are responsible for uploading content and ads provided by the creative services team. They create event scripts so that the correct content displays in the proper area of the venue and the proper area of the TV screen according to the specified schedule. The content manager role has permissions in Cisco StadiumVision Director to configure event states/scripts, zones, groups, screen templates, playlists, and tickers. Content managers can also assign gadgets for custom menus and create playlists for those menus. |
|
Event Operators run the Cisco StadiumVision Director event scripts during an event. The event operator role has permissions to start and stop scripts and modify their states. They can change the transition of an event state from time-based to manual, move an event into one of the three ad hoc states (Inside Emergency, Outside Emergency, or Delay), and approve ticker content (legacy version). Additionally, the event operator keeps track of which break states have played and is responsible for performing the pre-game walk-through. |
|
Facility Operators have access only to the TV Off application. The facility operator must access this application directly using the http:// ipaddress :9090/web/sv/home, where ipaddress is the IP Address of the Cisco StadiumVision Director server. |
|
Help Desk users have read-only permissions to view and monitor information on the Management Dashboard. This role does not have permissions in the Control Panel, except to change their own password. For more information on the tasks performed by the help desk role, see the StadiumVision Director Management Dashboard Guide. |
|
(Release 3.0 and later). Self-Service Content (SSC) users are given access only to the SSC portal area of Cisco StadiumVision Director, where they can upload content into albums and publish that content to authorized TVs. This user-specific workspace contains only the content explicitly uploaded by that user, and only that user can see the content. The administrator authorizes each SSC user for the suites and TVs on which they can display their content. |
|
Support users are responsible for first-level technical support. They have limited access to the Management Dashboard to monitor DMP status, troubleshoot, and manage the DMPs on the Cisco StadiumVision network. The support role does not have permissions in the Control Panel, except to change their own password. For more information on the tasks performed by the help desk role, see the StadiumVision Director Management Dashboard Guide. |
|
(Release 3.1 and later). Venue Operators have script control only, and only for venues authorized by the administrator for that user. In the Management Dashboard, venue operators can view and monitor information on the Management Dashboard with read-only access to the venues for which permissions are granted. Note Venue Operators are the only role that have venue-specific permissions. For more information, see the Configuring Cisco StadiumVision Director for Multiple Venue Support. |
Table 2 provides a summary of the areas of access in the Cisco StadiumVision Director software by each user role.
Note “Yes” indicates that the user role has access to the corresponding functional area, and “—” means that the role does not have authorization there.
|
|
|
|
|
|
|
|
|
|
---|---|---|---|---|---|---|---|---|---|
|
|||||||||
Limited1 |
|||||||||
Limited2 |
|||||||||
Limited3 |
Yes4 |
Limited5 |
|||||||
SSC Portal6 |