Bring new images in with consent attached.
New images enter the library all the time: a campaign shoot, an event folder, match-day photos, a batch from a photographer. This workflow shows how Ansikt helps you define what the images are for, gather any missing consent, and review use before publication.
What you decide before images arrive.
You define the Campaign: what the images are for, which Purposes they may support, where the files will land, and when the consent expires.
Sometimes that starts before a photographer leaves for a venue. Sometimes it starts when a new folder arrives from an event. Either way, the work is the same: make the intended use explicit before the images are published.
If you're not yet running Ansikt, the setup walkthrough covers the first source and first Campaign every workflow builds on.
Eleven steps from "new images are coming" to
"we know what can be used."
-
Create the Campaign.
Name the Campaign. Pick the legal basis that applies. The Campaign is the scope your team works inside: the Purposes, the image folder or files, the consent records, and the end date.
This gives your DPO one boundary to audit later, instead of a folder of images and a separate trail of consent forms.
-
Define Purposes and Channels.
Write one Purpose per intended use: the campaign page, the annual report, the match recap, the internal training pack.
Subjects consent to Purposes. Channels are selected during publication. If a Purpose is missing, asking the subject is one click away in Ansikt.
-
Prepare consent collection.
If the images come from a planned shoot, prepare the consent flow before anyone starts taking photos. Ansikt gives you a QR code for the Campaign context.
When a subject scans the QR code, they see the Campaign Purposes in plain language and decide what they agree to. Ansikt records the decision against the Campaign.
-
Brief the people collecting images.
For a venue shoot, brief the photographer and the person handling consent. They need the Campaign QR code, the image destination, and the practical boundary for who should be asked.
For a folder import, the same preparation is quieter: confirm the source folder, the Purpose, and whether consent is already known or still missing.
-
Collect or attach consent.
For a planned shoot, the subject scans the QR code, reviews the Campaign Purposes, and gives or refuses consent before publication. For imported images, you attach the consent records you already hold or mark the missing ones for follow-up.
Where the subject is known, Ansikt can help you request consent for a missing Purpose before reuse.
-
Take or receive the images.
Your photographer takes the photos, or your team receives a folder from an event, agency or existing source.
The important thing is that the images arrive inside the Campaign scope, with the intended use already defined.
-
Put the images where your organisation keeps them.
Upload the images to your DAM, Drive, SharePoint, CMS or S3 bucket. Originals stay in your infrastructure.
You attach the folder, subfolder or selected files to the Campaign. Ansikt reads them through the connector.
-
Add the images to the working view.
Ansikt reads the Campaign image scope and records what was found. You get one working view of the images, people, consent records and missing decisions.
-
Match known people to consent records.
For people with a consent record, Ansikt links matching appearances in the new images and flags uncertain matches for review.
Unresolved appearances have no decision on file. Before publication, you either attach the right record, ask the subject for consent, or leave the image out of use.
-
Preview as published.
Your editor opens each candidate image and reviews it against the Purpose. Ansikt shows where consent supports the use, where it is missing, and where the decision needs review.
If the same image is considered for a different Purpose later, it gets checked again. The editor does not have to rely on memory or a separate spreadsheet.
-
Optional: publish via URL Proxy.
For public images you choose to serve through the Ansikt URL Proxy, the publish decision can be enforced at request time. Faces without permission are blurred in the served image.
If a subject withdraws later, the proxy enacts the takedown on the next request. See URL Proxy and Workflow C: Operate & maintain.
Originals in your systems. Consent and audit in Ansikt.
Original images stay in your DAM, your Drive, your SharePoint, your CMS — wherever your campaign folder lives. Ansikt reads via the connector. Originals never leave your infrastructure.
Consent records and subject decisions sit with Ansikt on your behalf, as your processor. You remain the controller. Decisions are written to the audit log per Purpose.
The working view and audit log sit with Ansikt. See Security for hosting, access control and retention details, and Consent for what the consent record contains.
The Campaign has an end date. Consents collected for it expire on that date. You can extend the end date before expiry; subjects see the expiry at sign time.
The places that need a human.
You touch three things by hand: defining the Purpose, collecting or attaching consent, and confirming uncertain matches before publication. Ansikt narrows the work. You still own the decision.
The point is not to pretend the work disappears. It is to show the gaps before an image is used, while there is still time to ask the subject or choose another image.