Nothing reaches a screen without the right sign-off.
Nine roles map to how signage teams actually work, from read-only inspectors to field agents who only register devices. And the approval workflow closes the loop: the person who edits content is not necessarily the person who can put it on 500 screens.
Draft, request, approve, publish.
A content author saves a draft and hits Request Approval. An Editor or Manager reviews exactly what will play and approves or sends it back. Only then does it publish. The 2 a.m. typo on every screen in the chain stops being possible.
- Authors edit and request, approvers publish
- Review shows the actual content, not a description
- Full separation between building and broadcasting
Nine roles, from all-access to read-only.
Manager and Editor run the account. Contributor creates without touching devices. Developer builds and debugs on development screens but cannot publish. Inspector sees everything and changes nothing. System Integrator, Field Agent, Service Account, and Technical Support cover installs, field work, and support without over-granting.
Locks at the network edge, too.
Panel access can be restricted to whitelisted user IPs, and data sources accept feeds only from allowed domains and IPs. The same governance that gates who can publish also gates where data may come from.
Governance in an afternoon.
- 1
Assign roles
Invite the team; each person gets one of the nine roles, nothing more.
- 2
Turn on approvals
Authors request, Editors and Managers approve. The gate applies account-wide.
- 3
Lock the edges
Whitelist panel IPs and allow-list the domains your data may arrive from.
Access and approval questions, answered.
Built for brands that answer to auditors.
Bring your security checklist and your publishing horror story. We will map both onto roles, approvals, and allowlists in one call.