Governance and control
Choose how teams share a signage site
A department may need its own screens and messages while sharing branding and company news. An independently administered unit may need separate site-level resources and administration. Both have local responsibilities, but they do not necessarily need the same site structure.

Settle that distinction during onboarding, restructuring, or a larger rollout. Creating a site for every department can fragment work that could be shared; putting independent units together can leave them without the separation they require.
Decide what can be shared
Start with one site when units can share content, templates, branding, settings, and central oversight. Groups can give departments, locations, brands, or other teams their own working resources within it.
Use separate sites when units need separate user assignments, resources, settings, and administration. The same person can be invited to more than one site, with access assigned separately in each. License inventory is not shared between sites. That is a different requirement from wanting different local messages on the screens.
A regional operation can therefore keep corporate resources in one site and delegate local publishing. Separate customers or independently administered units may need separate sites instead. Agree the arrangement with IT, site administrators, and local teams before building it.
Give each structure one clear job
Once teams share a site, distinguish screen organization, publishing, and user access. Confusing them makes it difficult to tell why a person can edit a resource or why a message reaches a particular display.
| Structure | What it represents |
|---|---|
| Screen folder | A lasting operating area: a location, department, ward, store, campus, classroom, or screen type. It can supply inherited Channels & layout, active time, other settings, and group access. Channels and layout are inherited or overridden together. |
| Channel | Content for an audience or purpose. Screens in a folder can receive both central and local channels. |
| Group | Resources a team can reach: channels, screens and folders, media folders, feeds, data sources, template categories, and tag folders. |
| User profile | Access type and permitted actions. With Group Access, resource assignments set scope; Site Access reaches across the site, subject to the profile's action permissions. |
The user-profile overview describes the standard central, local-administration, and publishing profiles. Resource access does not grant a missing action permission. Roles and permissions explains their combined effect.
Work through one department's responsibilities
Suppose the department shares the corporate design and central news but maintains its own notices. Its screen folder provides normal playback settings. A local channel holds departmental bookings. A group gives the team access to the resources it maintains, while profiles distinguish administration from content contribution.

The central team makes selected shared resources available and retains site-wide administration. Local responsibility does not require handing over the whole site. Let local teams publish within their own areas explains the day-to-day working model; Setting up groups and inviting users covers group resources and invitations.
Keep the folder tree understandable to the people operating it. Organize screens by region, department, and location develops that side of the structure.
Allow temporary audiences without changing the organization
A short campaign should not require moving screens out of their location folders. Keep its content and timing in bookings. When the audience crosses the folder tree, use tags and a tag folder to select it while screens retain their usual inherited settings.
Before extending the structure to more teams, check:
- Local and central content reach the intended screens.
- Users can carry out their tasks within the agreed scope, including access accumulated through other memberships or direct grants.
- Everyone understands who may change shared resources.
These checks give local teams room to work while leaving the shared responsibilities visible to administrators and support staff.