> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/displays/displays.md). # What is a Display? Xibo shows content on your screens; whether you have existing content or need to create your own, to show on 1 screen or a 100.000, Xibo makes it easy! Xibo uses the concept of Displays which are managed from the CMS to control when and how content is shown as well as provide device management tools for Users. A **Display** is an essential part of digital signage as is it bridges the communication between the **CMS** software (Content Management System) and **Media Player App**. ## How-to Video What is a Display {% embed url="" %} The **Player App** is installed onto a **Media Player**, which can be a separate physical hardware device attached to a screen or an integrated Media Player found in supported System on Chip (SoC) professional signage monitors. A hardware key is generated on installing the Player App which creates a unique **Display** record in the CMS. Once installed, the Player App must be **Connected** to the CMS by using a **Code** or by providing a **CMS Key**. Once connected a **Display** will be registered awaiting **Authorisation** in the CMS before it will become a managed device and start displaying content from the CMS. ## Creating a Display 1. **Download** the Player App 2. **Install** to the Player device. Some supported (SoC) System on Chip models will already have the Player App installed. 3. **Connect** the Player App to the CMS. 4. **Authorise** the Display using the row menu from the **Displays** page in the CMS. The Display will regularly connect to the CMS to check for any updated schedule information or any new content to download. The Displays grid will update to show the status, indicate if the Display has logged in recently, show the date and time stamp of when the Display was last accessed etc, to help you manage your network. {% hint style="success" %} Any updates will be downloaded and saved to the Player App. This means that if a connection issue were to arise between the Display and CMS, the Display would continue to show scheduled content offline until the connection was restored. {% endhint %} Manage **Displays** from the CMS to and use the range of device management tools to effectively control your network. ## FAQs ***Which Players can connect to the CMS using code?*** All Players, at the latest version support connecting via a code, with the exception of the Linux Player. ***Can I easily transfer a Display to another CMS?*** First you need to ensure that you have Two Factor Authentication set up, from the User Profile to use Transfer to another CMS setting from a Display row menu. Multiple Displays can be transferred using the With Selected option at the bottom of the Displays grid. ***Do the Player and CMS versions have to match?*** Our recommendation is that your CMS and Players should be of the same major version for the best results. ***What does it mean to Assign Files / Assign Layouts?*** Library files and Layouts can be directly assigned to a Display so that they are always available in the local library of the Player. This is useful for pre-loading a Layout ahead of time when the Layout will be used for some API integration to trigger a change for example. Content will still need to be scheduled to show on Displays. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xibosignage.com/displays/displays.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.