Glossary
Categories: Categories are like hashtags; they are used to tag your media for better visibility and usage. It allows you to organize your media structurally in what may make sense for you and your organization.
Channels: The source where media or playlists are loaded into and displayed.
Folder: Used to organize and group medias and templates for easier accessibility.
Framesets: Separate panels that can be displayed in one channel to be assigned a playlist and or widget.
Maintenance Jobs: Scripts that are set to run a specific task on a player.
Media: These are all the fully supported assets in the form of images, videos and web pages. To view the supported formats for each type of assets check the Supported Media Formats section.
Messages: Content that makes use of a specific template layout.
Metadata: Mainly used for adding a weather location for a player to consume.
Network Settings: Place to find the organization’s player username.
Player Groups: Allows for group organization and separation.
Players: Hardware that contains Playback Software to communicate with the Content Manager.
Playlists: A group of media that will be assigned to a channel and played in sequence or shuffle.
Schedules: A time frame given to a media or playlist that will set the boundaries for how long content will be played on the screen.
Templates: Created by the design team to be used to create a message that has a specific layout style.
User Activity: Shows a list of user actions within the Content Manager to track their activity.
User Profiles: A list of user profiles that has access to the Content Manager with their associated Workgroups and User Roles.
User Roles: Gives specific access privileges to a user depending on their authority over the Content Manager.
Workgroups: A hierarchical tree that defines a parent child relationship of the different locations a User, Media, Message, Template or Playlist can be associated to. Access to a parent node will give access and visibility to all the children nodes it’s associated with. Access to a child node will not give visibility to a parent.