Enterprise digital signage with SSO, audit log and an SLA
This page is for the person signing the invoice and the people reviewing the supplier, not for the person uploading a picture. It says what governance, evidence and procurement look like here.
Access that follows your directory
- SAML single sign-on, so accounts come from your identity provider and leave with it
- Roles of viewer, editor, approver and admin, scoped by location and by group
- Approval before publish on any group you choose, so one store cannot reach the network
- Session control and forced re-authentication for administrative changes
- An audit log of every change: the person, the screen, the setting and the time
Evidence you can put in a report
Proof of play covers every screen: what it rendered, when, for how long, with periodic screenshots and the offline periods marked. It exports to CSV, which means it lands in your reporting rather than staying in our panel. The detail is on the proof of play page.
For a network that carries paid placement, this is the difference between invoicing a brand and hoping about it.
Commitments in writing
| Commitment | Network plan | Enterprise |
|---|---|---|
| Uptime SLA | Yes, with service credits | Yes, negotiated with your team |
| Support response | Priority, with a named response time | Named contact and agreed response times |
| Data residency | Choose your region | Choose your region, including private deployments |
| Security review | Questionnaire answered | Full review with your security team |
| Onboarding | Guided setup | Dedicated onboarding for your locations |
| Payment | Card or invoice | Invoicing and purchase orders |
Procurement without a fight
- Invoicing and purchase orders instead of a card
- Annual terms with a single renewal date across the network
- One line per active screen, so the invoice reconciles against your own asset list
- Vendor forms, insurance and security questionnaires handled by people, not by a contact form
- A named contact through the purchase and afterwards
What running hundreds of screens actually needs
Scale is not a bigger upload button. It is tagging, so an action reaches 200 screens at once. It is permissions, so the number of people who can reach all 200 stays small. It is evidence, so somebody can answer for what those 200 screens showed last quarter. It is alerts, so a dead screen is a task and not a discovery.
The API and webhooks on the Network plan connect this to what you already run: a new location in your own system can create the screen, the group and the schedule without anyone opening the panel.
Talk to someone who knows the product
Send the shape of your network, your identity provider and what procurement needs. We answer with specifics, not a brochure.