Requests get scattered
Email and Teams messages separate the ask from the outcome.
Digital signage change management
Change store screens without losing the paper trail
Docket is where you ask for changes to the screens in stores — new artwork up, old artwork down — and follow each request until it's done.
Nothing reaches a screen from Docket. It mirrors what is in Samsung MagicINFO, keeps the request and approval record, and leaves deployment to a person in MagicINFO.
Fall window refresh — video walls
Awaiting approvalScreens214
Goes upMon 21 Sep
Comes downSun 25 Oct
M. Tremblay · Submitted · 09:42
System · Reach resolved — 214 screens · 09:42
A. Singh · Awaiting review · 10:06
Screen changes should not live in an inbox
When screen changes are managed through email, spreadsheets, and Teams messages, it is hard to tell what was asked, which screens were included, who approved it, or what actually went up. A small misunderstanding can reach live screens.
Docket gives each change one place to be requested, reviewed, deployed, and kept on record.
The record disappears
Approvals and screen scope are hard to reconstruct later.
Mistakes reach screens
A small misunderstanding can become a live-store problem.
Request. Approve. Deploy on record.
1. Describe the change
Pick the change type, choose the screens, add or select the content, and set the dates. Docket shows a live count of the screens your choice reaches before you submit.
2. Review what will happen
The signage team reviews one sealed request with the screens, images, and timing together. If it is rejected, the reason is recorded.
3. Deploy in MagicINFO
A human operator makes the deployment in MagicINFO and marks the request Deployed. The record shows what was asked, approved, and done.
Draft→Awaiting approval→In progress→Deployed
RejectedCancelled
Built for the work around live screens
Read-only by design
Docket reads from Samsung MagicINFO. Its integration cannot write to the CMS, deploy content, or touch live screens.
What is actually playing
For a replacement or removal, pick from the playlists and content mirrored from MagicINFO. You are not working from an old attachment or a guessed screen list.
Exact screen reach
Choose a group or individual screens, see the live count, and expand it to check the exact list before you commit.
A sealed request
Once submitted, screens and images cannot be edited. That is what was approved. Need a change? Cancel or clone it into a fresh Draft.
An honest paper trail
Every action is recorded: who asked, what they asked for, which screens were included, who approved, who deployed, and when.
Files kept exactly as sent
Images are kept byte for byte as uploaded. Nothing is resized, re-encoded, or stripped before the team deploys it.
Roles that match the work
Admins, Standard users, and Viewers each have clear permissions. Agencies and integrators can keep brands separate in their own tenants.
Dates and notifications
Set go-up and optional come-down dates during business hours. The calendar and email notifications keep the right people informed.
A read-only boundary around live screens
Docket mirrors information from MagicINFO in one direction. There is no path back to deploy or change a screen.
Less archaeology. Fewer surprises on screens.
Docket makes accountability visible. The requester sees the scope before submitting. The approver sees what they are approving. The operator sees the work to do. Everyone can return to the same record later.
That means fewer errors on live screens, faster campaign turnaround, and one place to look instead of searching through inboxes and spreadsheets.
Visible scope
The requester sees the reach before submitting.
Clear approval
The approver sees the whole change together.
Deliberate deployment
The operator sees the work to do.
One record
Everyone can return to the same history.
The approval and audit layer for MagicINFO
Docket mirrors screens, playlists, and content from Samsung MagicINFO on a regular sync. It uses that current information to make a request precise, then leaves the actual deployment in the CMS and in human hands.
Questions
Does Docket deploy content to screens?
No. Docket does not deploy content or write back to Samsung MagicINFO. A human operator deploys the approved change in MagicINFO, then records it as Deployed in Docket.
Can a request be changed after it is submitted?
No. A submitted request is sealed: its screens and images cannot be edited because that is what was approved. Before review starts, the requester can Cancel it. To run or revise a finished request, clone it into a fresh Draft.
How does Docket know what content can be removed or replaced?
Docket mirrors screens, playlists, and content from Samsung MagicINFO on a regular sync. For removal or replacement, the requester selects from what is playing now.
Who can use Docket?
Admins manage the tenant and review work. Standard users can create, submit, track, cancel their own requests before review, and clone requests. Viewers can see everything but cannot create a request.
Does Docket support more than one brand or client?
Yes. Docket is multi-tenant, with a per-tenant permission matrix. It suits agencies and integrators managing signage for multiple brands.
What happens when a request is rejected?
Rejected requests always carry a reason. They are not edited or reopened. The way forward is to clone the request into a fresh Draft, make the needed changes, and submit it again.
Put every screen change on record
Docket was built inside and runs in production for a national retail signage network in Canada. See how it fits the way your team works.