Operational efficiency
Manage and support your signage site
A support question may begin with one screen or one user, yet depend on the wider site. A screen can inherit a setting from its folder. A user can have an action permission but lack access to the resource. A rollout can reach its available license capacity. Knowing where those decisions live makes the first checks more useful.

This matters when taking over an established site, helping a colleague whose message has not appeared, or preparing an expansion. As departments, integrations, locations, and player types accumulate, informal changes and unclear ownership make the same questions harder to answer.
Establish what the user and screen should be doing
Start with the intended setup before changing it. User profiles define access type and permitted actions; groups connect people to resources. Other memberships and direct assignments can add access, so a role name alone does not explain everything the person can reach. Roles and permissions explains how the two requirements combine.
For a screen, check its folder. Folders can supply inherited Channels & layout, active time, player settings, and group access. Channels and layout are overridden together; other settings can have their own overrides. A screen-level override may explain why one display differs from its neighbors.
The next checks depend on the problem:
| Question | Useful checks |
|---|---|
| Why can this person not complete a task? | Their action permission and access to the specific resource, including all memberships and direct assignments. |
| Why is this screen not showing the expected message? | Its folder and overrides, booking targets, channel subscriptions, schedules, media, and connectivity. |
| Can the next group of screens be added? | Available license capacity and who owns registration and technical preparation. |
The Screen status guide explains connection and license status. Compare the planned setup with what the affected user or screen actually shows before escalating.
Use status and capacity to guide the investigation
Dashboard widgets bring together screen status and map views with media, user, and group information. Use them and the screen details to establish the current situation, then examine the relevant booking to understand what should play.
Widgets and resources depend on permissions. Two people may see different information on the same site, so a missing control does not prove that the operation or information is unavailable. Give responsible staff the user, screen, dashboard, and license access their work needs.
License status shows total, used, and free screen licenses alongside unlicensed devices. Its Update licenses action synchronizes the view with the licensing portal; see License allocation. Use that capacity check before adding screens to an expansion, rather than discovering a shortage during installation.
Distinguish site administration from installation work
A site brings together shared resources and administration. Local teams maintain content and bookings, while site administrators manage the shared structure and involve technical specialists when a question reaches beyond it.
An administrative job title or ordinary site ownership does not grant every technical capability. Reserve site ownership and license-status access for the people responsible for those tasks, and refer installation-level settings, utility actions, and background work to the qualified administrator.
Hand over observations and maintain clear ownership
If the initial checks point to background operations or system-wide configuration, pass qualified support the affected site, screen, operation, and observed result. The technical administrator handles installation-wide changes and requirements for internal sources; the local team keeps responsibility for its content during the investigation.
Internal webpages and integrations need supported authentication and playback on the actual installation, with fallback content if the source is unavailable. Shared configuration does not make every source or player compatible. The Webpage guide describes playback modes and login options to check for these sources.
Review ownership when departments or integrations are added. IT may need to confirm who maintains directory sign-in through Active Directory or Microsoft Entra ID, where supported; that is different from editing an ordinary user. Communications, local administrators, IT, and support should understand their part without needing every technical control.
Use invitations, profiles, and groups to give local teams their intended resources. Create group and invite user covers assigning a profile and resource access. Keep folders and responsibilities understandable as the site grows: the same discipline helps a small installation and a large shared site.