Beeldbank.nl: Permissions per Team or Department: Roles from Administrator to Read-Only Guest

Why Departments Need Different Permissions in One Image Library

Organisations with multiple departments face control problems. Marketing needs campaign photos but shouldn't see HR images. Facilities manages building photos but can't give global edit rights to everyone. One library serves everyone, but different teams need different access. The common workaround, separate folders and hoping people follow rules, fails immediately.

Files get mixed up, wrong versions circulate, and nobody knows who was allowed to do what. A role-based approach controls not only what people see, but also what they can do with it.

Beeldbank.nl lets organisations set permissions per team or department so that everyone only sees the images meant for them. The sections below look at how roles are built, which rights exist, and what you should decide before you set anything.

One Environment with Separation of View, Not Separate Systems

The core idea is that teams work in the same place but get different views. Beeldbank.nl supports user roles from administrator to guest user with read-only rights, with permissions set per user, team or department. That gives you three handles: the individual, the team and the department.

Think of it as a design exercise on paper first. Which groups exist? Who needs to upload, who only needs to look, and who may change settings? A marketing lead, a colleague in a branch office and an external agency will have different answers, and the roles you create should reflect those differences. Resist the urge to create a role for every person. A short list of roles is easier to explain and to check.

If your organisation has several branches, Central Image Management for an Organisation with shows how this fits with menu structure and approved assets.

Creating Roles: Allowed or Not Allowed, Per Item

New user roles in Beeldbank.nl are created under Instellingen > Gebruikers > Gebruikersrechten via "Groep toevoegen". For each item you indicate whether the role is allowed to use it or not. You build the role from the items you choose, rather than picking from a fixed list.

One warning deserves attention: if you give a user permission for an item, that user can also make changes there. So "allowed" means more than "may look". Take that into account for every item you switch on, especially the settings items.

The rights cover these settings items: Adres en huisstijl, Menu, Quitclaim beheren, Gebruikers overzicht, Gebruikersrechten, Upload instellingen, Download instellingen, Watermerk, Voorkeurs instellingen, Velden, Bestandsinfo, Filters, Lijst weergave, Dashboard and Prullenbak. For example, Quitclaim beheren means creating, editing and deleting quitclaims. Go through the list once and ask for each item which role really needs it. When you work with images that show people, Portrait Rights, Quitclaims and Image Management Software explains what to require in your system and from your contributors.

The Upload Right: Who Adds Files and Who Approves

The Uploaden right in Beeldbank.nl decides whether a role can add files, whether those files are placed directly or first go to the temporary folder for approval, and whether the role may approve files itself. These are three separate decisions packed into one right.

Think about which of your teams should be trusted to publish directly. Someone who uploads a few photos per month for their own department may be a candidate. A new colleague, or an external party, may be better served by the temporary folder, where someone else approves the files first. Name the approver in advance. A temporary folder nobody looks at is a bottleneck.

For detailed guidance on upload workflows, Photographer Uploads Without Chaos walks through how to use temporary folders and approval roles to keep uploads organized.

The Share Right: Original or Watermarked Only

Seeing an image and sending it on are different things. The Delen right in Beeldbank.nl decides whether a role may share the original file, or only a version with a watermark, for example a copyright sign or the company logo.

That gives you a simple rule to apply per role. Colleagues who work with the images daily may need the original. A role for people who only need to show or review images can be limited to the watermarked version. Decide this per role and write the reason down, so that the next administrator understands why the setting is what it is.

A Worked Planning Example

Take an imaginary organisation with a head office, a team that photographs locations and a communications team. The sketch below is a planning aid, not a description of preset roles.

Head office needs someone who can manage users and rights. That is the administrator role, and it should be given to very few people. The photographing team uploads, so its role gets the Uploaden right, and you decide whether its files go directly into the collection or first to the temporary folder. The communications team mostly searches and downloads, so its role gets no settings items at all, and you decide whether it may share originals or only watermarked versions.

Then add a guest role with read-only rights for people outside the organisation who only need to look. After that, assign users to the roles, and when someone changes department, you change the role.

Permissions Overview: What Beeldbank.nl Delivers

Permission Type	What Beeldbank.nl Controls	Why It Matters
Roles per user, team or department	From administrator to guest user with read-only rights	Fine-grained control at three levels keeps permissions manageable
Uploaden right	Whether a role can add files, and whether they go live directly or require approval	Prevents chaos from uncontrolled uploads; ensures quality review
Delen right	Original file, or only a watermarked version	Protects drafts and ensures final-approved versions are shared
Settings items	Per item allowed or not; allowed also means the user can change it	Prevents accidental misconfiguration by limiting who can edit settings
Guest role	Guest user with read-only rights	Partners and external teams can view without risking changes

Principles for Permission Design

A few principles keep the setup manageable. First, give each role the minimum it needs. If a role can reach the Gebruikersrechten item, it can change rights, so hand that out sparingly. Second, be explicit about uploads: directly live, or via approval? Third, separate looking from sharing, and decide who gets originals.

Fourth, write down who is responsible for the rights. Roles drift over time as people change jobs. Plan a moment, for instance twice a year, to go through the user overview and ask whether each person still has the right role. The dashboard and the user overview are the places to start.

Before You Start: Questions to Answer on Paper

Before you open the settings, answer a few questions. Which teams or departments exist? Which images does each group need to find? Who approves new uploads? Who may share originals? Who becomes administrator, and who is their deputy?

The structure of your collection influences the answers. If you have not yet decided how to organise it, Designing Your Image Bank Structure guides you through the questions colleagues ask most. For the security and hosting side, Image Management Software from a Dutch Supplier covers hosting, security and login questions to put to any vendor. Permissions limit what people can do inside the tool; hosting and login security are separate questions that you also have to ask.