How Beeldbank.nl Automatically Hides Photos Without Valid Consent for Privacy Officers

Why Privacy Officers Choose Automatic Hiding in Beeldbank.nl

A privacy officer asks a simple question: how do we stop colleagues from using a photo when consent is missing? Beeldbank.nl answers it with one setting. It hides images without valid consent, so they do not show up in the normal overview and nobody picks them by accident. The images stay safely in the system, and the hiding happens without anyone having to remember a rule. This article walks through where the setting lives, who can see the hidden images, how group photos are handled and how the sharing warning completes the picture.

Switching On Automatic Hiding Under Voorkeuren

With the setting 'Beelden zonder toestemming automatisch verbergen' switched on, images without valid consent are not visible in the normal overview. You find it under beheermenu > Instellingen > Bedrijfsinformatie > Voorkeuren, where the menu reads 'Beelden zonder geldige toestemming automatisch verbergen'. It is a single switch for your administrators, and from that moment the default view of the archive shows only images that are ready for use.

The effect for daily work is clear. A communication colleague searching for event photos sees the photos that can be used, not a mix of usable and problematic images. Consent becomes part of the way the archive presents itself, instead of a separate checklist that people consult after they have already chosen an image.

The Verborgen Beelden Page as a Worklist for Administrators

Hidden images are listed on the 'Verborgen beelden' page in the admin menu. The page shows all files with a person without valid consent or a face that has no name yet. For a privacy officer this is a ready-made worklist: every entry is either a consent gap to close, a face to name, or an image to leave out of use. A short weekly look at the page keeps the list shrinking.

Access is deliberately narrow. Only users with the right 'verborgen beelden bekijken' can see hidden images. That fits the principle of giving people only what their role needs. The colleague who follows up on consent and the colleague who approves publications can each get the access that suits their task, and everyone else simply works in the clean overview.

The page also works well together with the way consent is collected. If your organisation moves from signed forms to e-mail invitations, the explanation in paper or digital quitclaims for collecting consent shows how quickly entries on the hidden list can be resolved.

Why Every Person in a Group Photo Needs Valid Consent

Images with multiple people only become visible once everyone in the image has valid consent. Picture a group photo of three colleagues where two quitclaims are in place and the third is still missing. The image stays hidden until the third consent is recorded, and the moment it is, the photo appears in the overview without any manual step. Nobody has to guess whether a group image is complete, because the archive checks every person for you.

This strictness matches how privacy guidance describes publishing. Publishing images requires permission from the people shown, given freely, with the purpose made clear in advance. The GDPR points the same way: Article 6(1)(a) makes processing lawful where the data subject has given consent for one or more specific purposes. Beeldbank.nl turns that principle into a rule the system applies to every group photo, every day.

The Sharing Pop-Up Warning Before an Image Leaves the Archive

Hiding protects the overview, and the warning protects the moment of sharing. When sharing, a pop-up shows a warning if not all persons in the images to be shared have given consent. A colleague preparing a download for an external partner sees the warning at exactly the point where the image is about to leave the archive. Together, hiding and warning cover both everyday browsing and outgoing files.

Because the warning is built into the share flow, it works for every user without training sessions or reminder e-mails. New colleagues, temporary staff and freelancers all get the same protection from their first day.

Faces Without a Name and Images That Need a Decision

The hidden images page also lists files with a face that has no name yet. That is useful, because a person who has not been named cannot have valid consent on record, and the page puts those faces in front of someone who can act. The administrator opens the entry and chooses: name the person and link a quitclaim, discard the face, or keep the image out of use. For faces of people in a crowd that nobody can name, see crowd shots and unknown faces, which describes the discard and "geen toestemming" options in detail.

A quitclaim in the system records that a person agreed. The purpose stays your own editorial choice: your team reads the quitclaim and decides whether a planned campaign fits what was agreed. Beeldbank.nl takes care of the status, the hiding and the warnings, and your team applies its own purpose check, which keeps the roles clear. A well designed form makes that check easy, and the quitclaim template checklist for digital consent forms lists what such a form should contain.

A Test Plan That Proves the Setting Works in Your Archive

An afternoon of testing gives your privacy officer a concrete record to show to colleagues. Use a small set of images you control and work through these cases.

• An image with one person who has valid consent: it is visible in the normal overview.
• An image with one person without consent: it disappears from the overview and appears on the Verborgen beelden page.
• A group image where only one of several people lacks consent: the whole image stays hidden until that consent is recorded.
• An image with a face that has no name yet: it is listed on the hidden images page for an administrator to handle.
• A share attempt with a consent gap: the pop-up warning appears before the image is shared.
• A user without the 'verborgen beelden bekijken' right: this person works in the normal overview only.

Write down what you see, and use the notes as the internal guidance for staff. Then close the gaps you found: ask the people with missing consent to sign, and name or discard the faces that wait for a decision. The aim is a hidden list that gets shorter every week.

When a Person Withdraws Consent

Consent is not permanent, and an archive that hides images based on status is well placed to handle a withdrawal. When a person withdraws, the status on that person changes, and the consent checks that hide and warn follow the new status. The full routine, from receiving the request to checking the overview, is described in withdrawing consent for photos in a step-by-step workflow. Used together, hiding, warnings and a clear withdrawal routine give an organisation of any size a consent process that people actually follow.

Part of the Feature	What It Does in Beeldbank.nl	Benefit for the Privacy Officer
Automatic hiding setting	Images without valid consent are not visible in the normal overview; found under beheermenu > Instellingen > Bedrijfsinformatie > Voorkeuren	Consent is applied before an image is picked
Verborgen beelden page	Lists files with a person without valid consent or a face without a name	A ready worklist for follow-up
Right to view hidden images	Only users with 'verborgen beelden bekijken' can see them	Access matches the role
Images with several people	Visible only once everyone in the image has valid consent	No incomplete group photos in circulation
Sharing	A pop-up warns if not all persons have given consent	A check at the moment an image leaves the archive