Beeldbank.nl for Mbo and Roc: Image Management With Consent and Usage Rights

Your roc or mbo institution runs many events every year: open days, career days, graduation ceremonies, program showcases, internship fairs. Each event produces a lot of images. Several programs want to use them in different ways: on social media, on the website, in printed brochures, in internal newsletters, in presentations to future students. The challenge is that consent differs by audience. Younger students may need a parent or legal representative to sign. Adult students, staff and volunteers can sign for themselves. Beeldbank.nl lets you manage this complexity by creating separate consent forms and usage options for each target group.

Why Multiple Consent Forms Matter for Mbo and Roc

Your institution probably photographs many different groups: adult students, younger students, staff, volunteers, guest speakers, visitors. Each group may have different rules about who can sign and for what purposes. Beeldbank.nl allows multiple consent forms for different target groups such as employees, volunteers or participants. That makes it possible to word a form for adult students, another for younger students who need parental permission, and another for staff or volunteers, instead of forcing one text on everybody.

For minors, Beeldbank.nl applies the rule that the parent or legal representative must sign the digital consent form (quitclaim). This is important to get right, so before you configure anything, list the groups you photograph and write down who signs for whom. Then configure one form per group.

Define Usage Options So People Control How Their Image is Used

In Beeldbank.nl the administrator defines which usage options a person can consent to. Examples are within the organisation, information leaflet, website, print, social media, newsletter and presentations. Options can be added, removed or renamed, and the person sees them exactly as you defined them in the form when they sign.

This is powerful when different programs publish in different places. A person who agrees to the website but not to social media can say so on the form, instead of giving an all-or-nothing answer. Keep your list of options short and in plain language, because every option is a question the signer has to understand and answer.

Consent Validity Periods and Automatic Reminders

Consent does not have to last forever. In Beeldbank.nl the validity of a consent form can be set to run indefinitely or for a specific number of months. An automatic reminder is sent to the person before their consent expires, asking them to renew or letting the consent expire. After that, the person can be re-invited to sign or the consent can be left to expire.

The system holds the dates, but your institution sets the policy. Ask yourself: should consent for an open day photo run for the school year or longer? What happens to the photos of a student who has graduated and left? Who contacts people who do not respond to the reminder? Write the answers down before you configure the forms, so every program in your institution applies the rules consistently.

Hiding Images Without Valid Consent Automatically

Beeldbank.nl can hide images without valid consent automatically when this setting is turned on. For a large institution this is a useful safety feature: a colleague preparing a social media post does not have to check a spreadsheet for every photo before publishing.

Before you rely on automatic hiding, test it. Let one form expire on purpose, and look at the normal overview as a colleague would. Check that the setting for hiding images is switched on, and check what your colleagues can still reach through other routes in your own systems. It applies only within Beeldbank.nl itself; images already published on social media or websites remain there.

Organising Photos Across Programs, Campuses and Cohorts

A roc or mbo often has several campuses and many program groups, and the same event may be photographed at each location. The system lets educational institutions search by branch, school year, department or file type. That makes it fast to answer a question like "open day photos, one campus, one school year." The result depends on the quality of what you enter when photos are uploaded. Agree on consistent names for branches and departments, and on who is responsible for filling in those fields after an event.

What Parents, Students and Staff May Ask

Educational organisations in the Netherlands must comply with the AVG (GDPR in Dutch). Parents may ask about what data the institution holds about their child, including photos. They may also ask: Is my child's photo still used? For which channels did I give permission? A consent form with clear usage options and a visible validity period makes those questions easier to answer.

If a person withdraws consent, set them to "geen toestemming" (no consent) in the system. Images where that person is recognisable are then no longer used within the system. Copies already published elsewhere, such as on social media or in print, sit outside the image bank and need separate attention. For more on managing withdrawals step by step, see Finding Every Photo of a Student Who Withdraws Consent.

Consent Workflows in Other Education Settings

The same consent principles apply across educational institutions. For school groups managing photos by branch and cohort, see Image Bank for a School Group. For hogeschool communication departments with higher security or integration requirements, see DAM for a Hogeschool Communication Department. The consent workflow for non-profit organisations follows the same logic; see Image Bank for a Charity.

Setting Up Your Forms Step by Step

Start small. Pick one program and one event, such as an open day, and run the full cycle with it: send the forms, add the consent records to the images, publish one photo, let one consent expire and withdraw one consent. What goes wrong in this small test is cheap to fix, and it shows you where your own process needs clearer roles.

Before you launch broadly, decide on your consent structure. List the target groups (adult students, younger students, staff, volunteers, guests), define the usage options for each group (website, social media, print, newsletter, presentations), and decide on the validity period (one year, two years, or indefinite). Then decide who adds the consent records to the images after an event, and who checks consent before publication. Use the worksheet below to guide these decisions.

For a multi-program institution managing event and campaign photos, Beeldbank.nl ties consent to images and makes them searchable by campus, program and cohort, with expiry reminders and the ability to automatically hide images without current consent. If your institution is planning to professionalise how it handles photos, separate forms per target group and clear expiry rules should be on your requirements list.