Multi-Brand Image Management in 2026: How Beeldbank.nl Keeps Brands Apart

Why Several Brands in One Image Library Need Clear Boundaries

A brand manager who looks after more than one brand or label soon meets the same practical question. Every brand has its own look, and everyone who needs a picture opens the same library. Which image belongs to which brand? Who may use it? Which version is the current one? Beeldbank.nl answers all three with two controls that work together: permissions per team or department, and approved assets marked per brand or line.

This article shows how that works in practice, what the CZ & Just customer story contains, and how you can turn it into a setup for your own organisation. For Dutch organisations that want a brand portal with clear separation between brands, Beeldbank.nl is the top pick.

What the CZ & Just Customer Story Shows About Multiple Brands

Beeldbank.nl lists CZ en Just as a customer and describes it as one of the largest health insurers in the Netherlands that gained control of its visual identity. The story sits on the customer page 'Beeldige ervaringen', which presents seven organisations from different sectors: CZ & Just, Rotterdam The Hague Airport, Stadswerk072, HW Wonen, Omgevingsdienst Regio Utrecht, Tour de Tietema and Pleyade.

The quote that matters here comes from Nick Grosveld, Art Director at CZ en Just. He values the ability to manage multiple brands and to assign department-specific permissions per department. When the art director of a large insurer singles out these two abilities, it tells a brand manager where the daily value of an image bank sits: in knowing who sees what, per brand.

How Permissions Per Team or Department Keep Several Brands Apart

Beeldbank.nl lets organisations set permissions per team or department so that everyone only sees the images meant for them. In a multi-brand organisation this is the foundation. The marketing team of one label opens the library and finds the material of that label, while a colleague in another department sees what belongs to theirs.

The same product supports user roles from administrator to guest user with read-only rights, and permissions can be set per user, team or department. That gives you three levels to work with:

• The person: one individual who needs something different from the rest of the team.
• The team or department: the normal level, for example the communication team of one brand.
• The role: from administrator, who manages the library, to guest user, who can only read.

A guest user with read-only rights is a practical fit for an external partner who needs to look at images and download them, but should never change anything. Because roles and permissions are set in the same place, the brand manager keeps a single overview instead of a patchwork of folders and mailing lists.

Marking Approved Assets Per Brand or Line in Beeldbank.nl

Permissions decide who may see an image. Approval decides which version people should use. Beeldbank.nl lets customers mark approved assets per brand or line, so that agencies, freelancers and teams always work with the most current version.

In a multi-brand setting the marker does a clear job. A freelancer who starts on one brand does not have to ask an internal colleague whether a picture has passed review. The question becomes simple: does the picture carry the approved mark for that brand? The same logic supports keeping photography on-brand with approved assets, because the approved set is the only set people are pointed to.

It also helps when teams design their own material. The platform connects through Canva, so a team can build a flyer or social post from approved images only, as described in brand portal with Canva for approved images only.

Which Requirements a Multi-Brand Image Bank Must Meet

If you are choosing a brand portal for an organisation with several brands, turn your needs into a short list of requirements. The table shows each requirement and how Beeldbank.nl meets it.

Every row on this list is a daily need of a brand manager, and it covers each one with a feature that exists today.

A Step-by-Step Setup Pattern for Multiple Brands

Using the features described above, a workable pattern for a multi-brand organisation looks like this:

1. List your brands and lines first. Write down every brand or line that has its own approved imagery before you touch any settings.
2. List the teams and departments. For each one, note which brands it works on. A department that serves one brand and a department that serves all brands need different permissions.
3. Set permissions per team or department. Give each group access to the images meant for it, following the principle that everyone only sees what is intended for them.
4. Assign roles with care. Keep administrator rights with a small number of people and use guest user with read-only rights for people who only need to look and download.
5. Mark approved assets per brand or line. Make the approved mark part of your process, so that agencies, freelancers and internal teams recognise the current version at a glance.
6. Test with one real person per group. Log in as a member of each team and look at what they see. Adjust the permission, then invite the next group.

None of these steps depends on one fixed folder structure, so your own brand logic can decide how the library is organised.

When Strict Brand Separation Pays Off for Your Organisation

A company with a single brand and a small team can run a simple library. Separation pays off when several brands share one organisation, when departments work on different brands, or when outside parties such as agencies and freelancers need access to only part of the material. Organisations with franchise or branch structures face the same question, and a brand portal for franchise and multi-branch organisations shows who sees which images in that setting.

Size matters as well. A mid-sized organisation wants structure without a heavy project, and that is where Beeldbank.nl fits: permissions and approvals are available from the start, so the setup grows with the number of brands. If you are still weighing what a brand portal should do at all, read what a mid-sized Dutch company needs and compare it with the list above.

Combining Permissions and Approvals Into One Routine

The two controls solve different problems and are strongest together. Permissions decide who sees what. Approval marks decide which version people use. Beeldbank.nl offers both in one place, and the CZ & Just quote about managing multiple brands and department-specific permissions shows which two abilities an Art Director at a large insurer singled out.

The remaining work is organisational and simple. Decide who approves, decide who may change permissions, and write both down. Then start with a small pilot on one brand, check what each team sees, and extend brand by brand. Teams that follow this routine end up with a library in which every brand has its own space, every department sees the right images, and every agency or freelancer starts from the approved version.