> 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/scheduling/scheduling_priority_display_order.md). # Using Priority and Display Order Xibo has a number of scheduling tools to allow for the simple creation of schedules across one or more Displays/Display groups. These tools allow users to define the order of scheduled items to tailor how content should be shown as well as flagging high-priority Events to display those at the top of schedule lists. ## Priority Priority pushes important content to the front of any existing schedules and overrides all other non priority events of the same Event Type (Layouts/Campaigns/Video/Images and Playlists) on the schedule. Schedules with a higher priority take precedence over those with lower priorities, with 0 considered the lowest. For example, you might have an important announcement with information about a fire alarm test which needs to be the only thing to show on Displays at a specific time. Assigning the highest Priority to this Event would ensure that it is the only content to be shown. On reaching the end time of the priority event, the normal schedule will resume on displays. ## Display Order Use Display Order to determine the play order of multiple Events which have been scheduled to show at the same time. Ordering is a simple numerical sort, lowest to highest numbers, Events marked with a 1 will be played before any Events marked with a 2 for example. Leaving the Display Order field blank will default to the order that the Event was first added. {% hint style="info" %} To ensure Layouts play in a defined order we recommend adding and ordering them into a Layout List Campaign. The Display Order can then be used to determine the order in which entire Campaigns should play.\ If Layout List Campaigns have the same Display Order set or this field is left blank, Layouts assigned to the Layout List Campaign will play according to the **Play List order** set. {% endhint %} ### Maximum Plays per Hour There is an additional setting when scheduling Events to limit the number of times the Event should be shown per hour on Displays. You may have a promotional Image which should only be shown once an hour for example. * Set a number here or leave as 0 for unlimited plays. ## FAQs ***What is considered the same Event Type for Priority?*** Layouts/Campaigns/Images/Videos and Playlists will be treated as the same Event Type when taking Priorities into consideration. ***What would happen if I ticked the Run at CMS time checkbox for an event?*** With this ticked, the Event time would be determined by the CMS time rather than using the local Display time for the selected Displays. Scenario: * CMS Time = GMT * Display 1 = GMT * Display 2 = GMT -4 If an event was scheduled to start at 11:00hrs, content would start to show on these Displays at 11:00hrs according to their time zones. These two Displays will not show the same content at the same time as Display 2 is 4 hours behind Display 1. If Run at CMS time was ticked, Display 1 will start to show at 11:00hrs, as it is on the same time zone as the CMS. Display 2 will start to show content at 07:00hrs as it is 4 hours behind the CMS time zone. --- # 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/scheduling/scheduling_priority_display_order.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.