Docket
Menu
Blog

How to Add a Content Approval Workflow to Samsung MagicINFO

Samsung MagicINFO is the backbone of thousands of retail screen networks. It schedules playlists, pushes content to displays, and keeps everything running. But there is one thing it was never designed to do: manage who gets to change what goes on those screens and make sure the right people approve it first.

If your team manages more than a handful of screens, you have probably felt this gap. A regional manager emails a request to swap a promotion. Someone on the signage team makes the change but was it the right content? For the right screens? Did anyone actually approve it? And three months later, when someone asks why that creative ran on 200 screens for an extra week, who has the answer?

This post walks through why a structured approval workflow matters for MagicINFO networks, what that workflow looks like in practice, and how to set one up without replacing your existing CMS.

The problem: MagicINFO manages playback, not people

MagicINFO excels at content delivery. You upload files, build playlists, assign them to devices, and schedule when they play. That is its job, and it does it well.

But most signage teams manage the process around content changes using a patchwork of tools that were never built for it:

  • Email threads where requests get buried under reply-alls
  • Spreadsheets tracking what was requested, deployed, and still pending
  • Chat messages with file attachments that get lost in the scroll
  • Verbal requests that leave no paper trail at all

This works when you have 10 screens and two people. It breaks down fast at 50, 150, or 500 screens across multiple locations. Common failure modes:

  • Wrong content on wrong screens because a vague request was misinterpreted
  • Unapproved changes going live without sign-off
  • No audit trail when legal or compliance asks who approved this content and when
  • Missed deadlines because the request sat in someone’s inbox over the weekend
  • Content staying up too long because no one tracked the takedown date

What a proper approval workflow looks like

A structured signage change workflow does not replace MagicINFO. It wraps around it. Think of it as the process layer that sits between someone wanting a change and the change going live on screens.

1. Request

A stakeholder submits a structured request that captures exactly what needs to change: which screens, which content, what dates, what type of change. Screen counts are visible before submission. Files are attached. Go-up and come-down dates are set.

2. Review and approve

The request lands in front of the right approver. They see exactly what is being asked: the scope, the creative, the timeline. They approve, reject with a reason, or ask for revisions. Once approved, the request is sealed and cannot be quietly changed after sign-off.

3. Deploy

An operator with MagicINFO access executes the approved change in the CMS, following the request spec exactly. When done, they mark the request as deployed.

4. Audit

Every step is logged. Who requested it. Who approved it. Who deployed it. When each step happened. The full history is always available.

A real-world scenario

Imagine you manage a retail signage network across 120 stores in Canada. Your marketing team runs 15 to 20 promotions per month, each requiring screen content updates.

Without a workflow:

  • Marketing emails the signage team with files attached and a Friday deadline
  • The operator starts updating playlists but is unclear on which screens exactly
  • A message goes out to clarify. Marketing responds Monday. The creative goes up two days late.
  • The campaign ends but nobody removes the content. It runs an extra four days.

With a workflow:

  • Marketing opens the request form, selects the Ontario Full Network group (87 screens), uploads creative files, sets go-up to Friday and come-down to Wednesday
  • The brand lead approves within hours. The request is sealed.
  • The operator deploys to the 87 specified screens and marks it deployed.
  • The system flags the come-down date. Content is removed on schedule.
  • A month later, when the VP asks how many screens ran the promo, the answer is one search away.

How Docket adds this workflow to MagicINFO

Docket is a change-management layer purpose-built for MagicINFO signage networks. It reads from MagicINFO (playlists, content, device groups) and adds the request-approval-audit process on top.

Key capabilities:

  • Read-only MagicINFO sync mirrors your MagicINFO setup so requesters select from real data. Docket never writes back to MagicINFO or deploys content directly.
  • Structured requests capture screen selection, content changes, timing, and change type in a standardized format.
  • Sealed submissions prevent scope creep after approval.
  • Role-based access with admins who approve, standard users who request, and viewers who observe.
  • Full audit trail logging every action: who, what, when.
  • Email notifications at each status change.
  • Campaign cloning to repeat successful deployments with new dates.

Pricing starts at $400 CAD/month for up to 50 screens with unlimited users and requests. A 7-day free trial is available for self-managed plans.

Getting started

If your team manages a MagicINFO network and you are still coordinating changes over email, the process gap will only get wider as your screen count grows.

Ask your team:

  • How many content change requests do we process per month?
  • How often does the wrong content end up on the wrong screens?
  • Could we answer a compliance audit about who approved what and when?
  • How much time does the signage team spend clarifying vague requests?

If those questions make you uncomfortable, a structured workflow will pay for itself quickly in time saved, errors avoided, and audit readiness.

Start your free 7-day trial Book a 15-minute walkthrough