Docket_ user guide
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.
How it works
You describe the change you want and submit it. The signage team reviews the request, makes the change on the screens themselves, and marks it deployed. Nothing reaches a screen without a person doing it — and nothing is done without a record here. Docket is the paper trail: what was asked, for which screens, by whom, and what happened.
Your team's Docket workspace has its own address — sign in with your work account.
Your role
Standardcan request
Create and submit change requests, track them, cancel your own while they're still awaiting approval, and clone past requests to run them again.
Viewerread-only
See everything — requests, screens, playlists, activity — without the ability to submit. Same pages, minus the New request button.
Finding your way
| Group | Page | What it's for |
|---|---|---|
| Work | Dashboard | Your requests at a glance, and anything waiting on you. |
| Requests | Every request, filterable by type and status. Open one for the full story. | |
| Calendar | When submitted changes go up, and when they come down. | |
| Activity | A team-wide history of who did what, and when. | |
| Inventory | Screens | Every screen in the estate — location, size, orientation, language. |
| Playlists | What each screen is playing right now. | |
| Assets | The images behind those playlists. |
Inventory pages mirror MagicINFO — the system that drives the screens — and are read-only for everyone.
Making a request
Five steps. Your draft saves as you go, so you can gather images before you know your dates and come back any time.
-
01
Type
What kind of screens is this for — computer monitors, 1×3 video walls, Spotlight, and so on? This choice shapes every step after it. A change that fits nothing on the list goes in as Other changes: describe it in words, attach images if helpful.
-
02
Which screens
Pick a predefined group (say, all French stores) or individual screens. Docket shows a live count of the screens your choice reaches — expand it to see the exact list before you commit. "This playlist" and "these 250 stores" look identical until you check.
-
03
Images
Publishing? Upload artwork, set the order and how long each image shows. Replacing? Pair each upload with the current image it takes over from. Removing? No upload at all — just tick the images to take down from what's playing today.
-
04
Timing
When it goes up and, optionally, when it comes down. Times fall on weekdays between 9:00 and 17:00 — these dates describe when the team does the work, so they stay inside working hours.
-
05
Review & submit
One summary — screens, images, dates. If anything is missing, you'll get every problem listed at once, not one at a time. Happy? Submit.
After you submit
Always comes with a reason. Clone the request, adjust, resubmit.
You can cancel your own request any time before review starts.
A submitted request is sealed — its images and screens can't be edited, because that's what was approved. Need to change something? Cancel it, clone it, fix the copy, submit again. You'll get an email as your request moves through each stage.
Keeping track
Open any request to see its full story: a timeline of every action with names and timestamps, the images going up or coming down, and the exact screens affected. Every list filters by change type and status — the two things you're usually scanning for.
Good to know
Running the same promo again?
Don't rebuild it. Clone copies the type, screens and images into a fresh draft — you just set the new dates.
Your images are kept exactly as uploaded
Byte for byte — nothing is resized, re-encoded or stripped. What the team deploys is precisely the file you sent.
Originals retire after deployment
Thirty days after a request is deployed, the full-resolution original is replaced by a preview thumbnail to save space. The request still shows the original's filename and size, and the deployed file itself lives on in the signage system.
Screen data is a mirror
Screens, playlists and assets are read from MagicINFO on a regular sync. Docket never writes back — deployments are always made by the team, in MagicINFO, by hand.
Deployed and Rejected are final
A finished request is never edited or reopened — that keeps the record honest. The way forward is always a clone.
Questions, or need a different role? Ask your administrator.
OnyourX_ Digital solutions, delivered.