The approval and audit layer for MagicINFO networks
Docket works alongside Samsung MagicINFO. It mirrors screens, playlists, and content on a regular sync so your team can request and review changes against what is actually there.
It never writes back. Deployment stays a deliberate human act in MagicINFO.
A mirror, not a remote control
Docket's MagicINFO integration is read-only by design. The API client has no mutating methods, and an endpoint allowlist limits it to reads. Docket cannot deploy content, change a playlist, or touch a live screen.
That separation is intentional. Docket is the system of record around the work. MagicINFO remains where the human operator carries out the deployment.
Request changes from what is playing now
When someone needs to replace or remove content, they select from the screens, playlists, and assets mirrored from MagicINFO. The content is grouped by the playlist a human will actually edit.
The requester can see the exact screen reach before submitting. Removing an item from a playlist can affect many stores; Docket makes that scope visible before approval.
Fall campaign · EN stores
Playlist grouping · 214 screens
Keep the screen inventory useful
Docket mirrors screen and playlist information from MagicINFO, including device classification and inventory. Requesters can work from predefined groups or individual screens instead of reconstructing the network in an email thread.
For new content, Docket keeps uploaded files exactly as sent. For replacements, each upload is paired with the current item it takes over from. For removals, there is no upload at all.
Approval that covers the whole change
MagicINFO can remain the place where deployment happens. Docket gives the surrounding work a clear request lifecycle: Draft, Awaiting approval, In progress, and Deployed, with Rejected and Cancelled branches recorded on the same paper trail.
The reviewer sees screens, images, and dates together. A submitted request is sealed. The operator records who deployed it and when.
See how the request lifecycle worksBuilt for teams that need to be precise
Use Docket for store networks where a campaign can span groups, individual screens, bilingual store targeting, or video-wall rows. It was built inside and runs in production for a national retail signage network in Canada.
See the retail workflowQuestions
Does Docket replace Samsung MagicINFO?
No. Docket works alongside Samsung MagicINFO. MagicINFO remains where a human operator deploys content. Docket keeps the request, approval, and audit record around that work.
Can Docket change a playlist or deploy content in MagicINFO?
No. Docket's MagicINFO integration is read-only. It cannot write to MagicINFO, deploy content, change a playlist, or touch live screens.
How does Docket handle a content removal?
Docket mirrors what is playing from MagicINFO. The requester selects the existing content to take down, sees the screen reach, and submits the removal for review. No upload is needed.
Can I edit a request after it is submitted?
No. A submitted request is sealed, and finished requests are never edited or reopened. Clone the request into a fresh Draft to run it again or make changes.