Use “The roster” in Recued. See everyone Recued can recognise, whether each person can actually be written to, and who has been retired — and open any of them from here, which is the only way in to a person.
The roster
Use “The roster” in Recued. See everyone Recued can recognise, whether each person can actually be written to, and who has been retired — and open any of them from here, which is the only way in to a person.
Complete workflow
Photo Attribution
16 pinned recipes
Use Photo Attribution in Recued to match one event's photos to the people you know, write a warm line for each picture, review them, and send everyone their own. Faces are matched on your machine; your photos are never copied; sending asks first. First install two programs on the server: face_recognition (pipx) and libvips (brew install vips). Then allow their actions on each tool pack's Access tab. Open “Scan an event folder” for the rest of the setup.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Scan an event folder” in Recued. Compare every photo in one event folder against the people you know, and record who appears in each picture. Photos stay where they are and are never copied. Matching happens on your own machine.
Use “Write the photo lines” in Recued. Look at each scanned photo and write one warm line naming the people recognised in it. A small copy with its embedded details removed is what the model sees, and the original is never sent. Run it again until the queue is empty.
Use “Review photos before sending” in Recued. List the photos waiting for a look, with the line that will arrive alongside each one and the names it was written for. Open a photo to approve it, rewrite the line, or leave it out.
Use “Review one photo” in Recued. See the picture itself beside the names Recued matched in it, correct the line it wrote, and say whether it is ready to send — the one place a wrong name or a wrong sentence can be caught before it reaches somebody.
Use “Look at one person” in Recued. See who a roster entry actually is — their reference photo shown from your own folder, beside the name and address Recued will use for them — so a wrong or duplicated face is something you can see rather than guess at.
Show all 16 recipes
Use “Set someone's details” in Recued. Fill in an email address and the name that messages should use for one person on your roster. A field left blank keeps what is already there rather than clearing it. The key derived from their reference photo cannot be changed.
Use “Retire a person” in Recued. Take somebody off the roster without deleting anything they are attached to — a duplicate left behind by a renamed reference photo, or someone who should not be sent to any more. Their photos stay on record; they simply stop being matched and stop being sent to.
Use “Import the roster (CSV)” in Recued. Add everyone to the roster from a spreadsheet in one go — their key, the name messages should use, and their email address — instead of typing each person in after the first scan.
Use “Export the roster (CSV)” in Recued. Copy out everyone on the roster as a spreadsheet, or - on an empty roster - get the column headings the importer expects, so you can fill them in and import the list instead of typing it.
Use “See who is ready to receive” in Recued. List everyone with approved photos waiting, and separately everyone recognised who has no email address yet. Send each person from here. Nobody is dropped quietly, because a missing address is the usual reason a photo never arrives.
Use “Re-describe a person” in Recued. After changing someone's name, rebuild the stored names on their photos and queue those photos to be written again. Photos already approved are left alone and counted, because somebody signed those off.
Use “Skip a photo” in Recued. Leave one photo out of the sending queue and release everyone who was waiting on it. Their other photos are untouched, so this cancels one picture for everyone in it rather than cancelling a person.
Use “Send one person their photos” in Recued. Send one person a single message carrying every photo of them that has been approved. A fresh copy of each picture is made with its embedded details removed, and that copy is what travels.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “See what has been delivered” in Recued. Show who has received which photo and when, one row per person per picture, with the message it arrived under. It reads information without changing anything.
Everyone on the roster
The list of people Recued can recognise, and the only screen that opens one of them. A person is on the roster because a photo of them sits in your reference folder, or because you imported them from a spreadsheet.
Who can actually be sent to
Ready to hear from you counts the people who have both an email address and a mailbox to send from. Anyone missing either is recognised normally and appears in photos — they simply cannot be written to, and nothing will tell you at the moment of sending unless you look here first.
The Can be sent to column says yes or no per person. If it says no, open them and set their contact details.
Active and retired
Active is the working roster. Retired are people you have taken off it: they stay recorded, they are not matched in new scans, and nothing is sent to them. Retiring is how you remove somebody without deleting what you already know.
Switch Show to see either, or everyone at once.
Opening somebody
Every row has its own button, which opens that person: their reference photo, their details, and the actions that apply to them. That is the only route to them — a roster key is not a name and the row here is where the two are side by side.
Getting people in and out
Import a roster (CSV) adds people in bulk from a spreadsheet, and asks what to do about anyone already on the roster whose details differ. **Export the roster (CSV)** writes the same shape back out, so the file you export is a file you can re-import.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (17 steps)
all_of_them
compare
Check if setting status equals everyone
rows_filtered
recued-core.photo-attribution.face_profile.search
Search face profile on photo attribution
skip: step.all_of_them equal true
rows_all
recued-core.photo-attribution.face_profile.search
Search face profile on photo attribution
skip: step.all_of_them equal false
picked
coalesce
Use the first available value from: rows filtered records, rows all records
list
default
Apply default
shown_n
count
Count items in list
reachable
all
Check if all conditions are true
people
map
Extract from each item
named
coalesce
Use the first available value from: item name, item real name, item roster key, (unnamed)
people_rows
map
Extract from each item
sendable_rows
filter
Filter by condition
sendable_n
count
Count items in sendable rows
ordered
sort
Sort by roster_key
table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
open_actions
map
Extract from each item
bulk_actions
default
Apply default
▼
Output
summary
card
table
table
button
open_actions
button
bulk_actions
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
status
setting
=
active
Uses (1 operation)
Pack operation
Search face profile on photo attribution
recued-core.photo-attribution.face_profile.search
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Read
Pack
Photo Attribution
read-only
Read: face_profile.search · No approval