The Studio Queue is a shared board for dividing editing work at a busy event. It lists every team waiting to be edited in the order their photos arrived, shows who is working on what, and hands the next team to whoever is free. This article explains how to open it, claim work, and keep two editors from stepping on each other.
Open the Studio Queue
Click the Queue tab in the top navigation, next to Studio. The board opens full-screen and refreshes on its own, so you can leave it up on a second monitor and watch teams arrive.
Not the same as the Send-To Queue. The Send-To Queue stages finished designs to your presets so you can send a whole batch at once. The Studio Queue is the opposite end of the workflow: it assigns unfinished teams to editors. One is about sending; the other is about dividing up the editing.
The board
Each row is one team, listed top-to-bottom in the order its first photo arrived (first in, first out). The numbered badge on the left is the team's position in line; the next team up is highlighted. Each row shows:
- Team — the team's folder name.
- Event — the event the team belongs to, with its friendly event name underneath when available.
- Photos — how many photos have arrived for the team.
- First upload and Last upload — when photos started and last landed.
- Captured by — the staff who photographed what the team is holding, listed as badges.
- Editing — who is on the team and when they started (or who finished it, with the turnaround time, once it's done).
- Status — a Waiting, In progress, New photos, or Done badge.
Use the event picker at the top to narrow the board to a single event, the Captured by picker to narrow it to one photographer, and the Show done switch to bring completed teams back into view (they sink to the bottom). Refresh forces an immediate update.
The event picker is searchable — type into Search name or number… to find an event by its folder name or its event number, and press Enter to take the top match. It lists only events that actually have teams on the board, so it never fills up with empty events, and it defaults to All events. Your choice is also sticky: once you pick an event it stays selected as you open a team into the editor and come back with Complete & return to queue, so you don't have to re-filter every time.
Who captured the photos
The Captured by column tells you which of your staff took the photos sitting in each team. A team routinely mixes photographers — several staff working one event, or a retake taken on a different device — so every contributor is listed rather than reduced to a single name.
Where the capturing account can't be matched to a member of your organization, the device name stands in instead. Hover the cell to see the devices behind the names.
A dash (—) means there's no capture information for that team. Only signed-in Templified Tether captures carry that information, so a team built from photos uploaded or dropped straight into Studio shows nothing here.
Next to the event picker, the Captured by picker narrows the whole board the same way. It defaults to All staff and devices; open it and you can choose one person, one device, or No capture info to see only the teams with no attribution. Options are grouped under Staff and Devices headings, and the Search staff or device… box filters them as you type. If nothing matches, you'll see No staff or devices match that search.; if the board has no attribution at all, No capture info on the board.
The picker only ever offers people and devices that are actually on the board right now, so a selection can't come back empty by accident. If you do filter down to nothing — because the teams left after your other filters have a different photographer — the board tells you how many teams are still there under the other filters and offers a Show all staff and devices button to clear it.
The position numbers on the left keep counting the full line, not just the rows you've filtered to. That way a graphics person filtered to their own device still sees a team's true place in the queue rather than being told it's next up when six other teams are ahead of it.
Spotting what changed
Because the board refreshes on its own, a team can be claimed by another editor or pick up new photos while you're reading the row above it. When a refresh changes a row's Status or its Photos count, that row briefly highlights so you can see it happen — that's how you catch a New photos badge appearing, or a Waiting team flipping to In progress just before you were going to click Open on it. A team that is genuinely new to the board animates in as it appears instead.
The highlight is a read cue, not a state. It holds for about two and a half seconds and then fades out on its own; nothing about the team changes when it clears, and there's nothing for you to dismiss.
Claim a team
To take a team, find its row and click Open. That claims the team for you and drops you straight into its folder in Studio, ready to edit. The status flips to In progress with your name on it, so everyone else can see it's taken.
When you're free and just want the next team in line, open the next Waiting row from the top of the board — the highlighted one is always next up. Two editors cannot grab the same team at the exact same moment, only one wins it. The other is never silently dropped into a team someone else already owns.
When a team is already claimed
Because the board refreshes on a short delay, it's possible to click Open on a team another editor claimed a moment ago. When that happens, a Team already claimed dialog appears, naming the editor who has it. You have two choices:
- Open anyway — go into the team regardless. Use this if you're collaborating on the same team on purpose.
- Go to next — skip it and claim the next waiting team instead. If nothing is left to claim, you'll get a short message saying the queue is clear (or that the rest are already being edited).
How a "team" is defined
A team is the shallowest folder in a branch that directly holds designs. Whatever folder a team's photos land in first is the team — the rule is purely structural, so it works whether your events nest teams shallowly or several folders deep.
Print sub-products living below a team — for example its Plaques or Plaque-PDF subfolders — are deliberately not listed as separate teams, even though they also contain designs. They're downstream artifacts of the same team, not their own editing assignment, so the board shows the team once instead of duplicating it across every print product underneath it.
The assignment banner
Once you open a team, a green Queue assignment banner appears at the top of its folder in Studio, labeled with the team name. From the banner you can:
- Complete & next — mark this team done and jump straight to claiming the next waiting team.
- Complete & return to queue — mark it done and go back to the board.
- Dismiss the banner (the ✕) to leave the assignment without marking it done.
The banner follows you into the team's subfolders too. If your editing takes you down into a team's Plaques or PDF subfolder, the banner stays visible so a nested editor still sees who owns the work and can finish it without climbing back up to the team folder.
You can also mark a team done straight from the board with Mark done on its row, and bring a finished team back into the line with Reopen (visible when Show done is on). Reopening returns the team to Waiting so any editor can pick it up again.
When new photos arrive for a finished team
Sometimes a straggler photo lands in a team an editor already finished. When that happens the board automatically brings the team back onto the active list with a purple New photos badge, so nobody has to remember to reopen it by hand. The team becomes grabbable again — opening it re-claims it for you, just like any waiting team — and its earlier "done" credit is cleared so it reads as a clean assignment. This only triggers when genuinely new photos come in, not when you re-edit a team's existing photos.
Clear the board at the end of an event
When an event is finished, owners and admins can retire everything still active in one action instead of marking teams done one by one. The button matches whatever the event picker is set to:
- With a single event selected it reads Clear this event. The confirmation is titled Clear this event? and tells you how many active teams in that event it will mark as done, and that teams in other events stay on the board.
- With the picker on All events it reads Clear queue, the confirmation is titled Clear the queue?, and it warns you that That empties the board.
Either way, nothing is deleted — the teams move to the done list and can be brought back with Reopen at any time.
A Captured by filter does not narrow the clear. Clearing follows the event picker only, so teams the capture filter is currently hiding get cleared too. When a capture filter is active, the confirmation dialog names it and says so explicitly, and the team count it shows is the count for the whole event scope, not for what's on screen. If you only meant to retire one photographer's teams, mark them done individually instead.
Event names on the board
For GFcrew/Pro accounts, the Event column shows the friendly event name beneath the folder's event code, matching how Studio's folder tree already labels events.
Comments
0 comments
Please sign in to leave a comment.