Permissions

An overview of different access policies and their permissions within the system.

Permissions define which parts of the system a user can access. When an account is created, it is assigned a role and one or more policies that determine available actions. The sections below describe each policy and its associated permissions, along with the conditions under which additional policies can be granted.

Base policies

All users with API access receive the following base policies:

  • Read and update self — Allows reading and updating your own profile.

  • Content read — Grants read access to published items in the content, media, and global category collections.

  • Read published media — Allows retrieval of media assets with a publication_date in the past.

  • Asset read — Grants read access to directus_files and their metadata.

Additional policies

Additional policies may be assigned to extend access to specific data sets:

  • Navigator — Read access to programs, educational_institutions, regional_education_desks, locations, and areas where vendor = 'onderwijsloket'.

  • HOVI — Read access to programs, educational_institutions, and locations where vendor = 'hovi'.

  • KiesMBO — Read access to programs, educational_institutions, and locations where vendor = 'kiesmbo'.

  • Scholen op de kaart — Read access to schools and locations where vendor = 'sodk'.

  • Read stats — Read access to anonymous usage statistics for Onderwijsloket services.

  • Algolia token — Grants access to the algolia_token field on the user account.

How to acquire additional policies

Additional access can be requested by contacting us. Eligibility depends on the policy:

  • Navigator — Available to anyone at no cost; a description of intended use is required.

  • HOVI — Requires a signed contract with the vendor.

  • KiesMBO — Requires a signed contract with the vendor.

  • Scholen op de kaart — Requires a signed contract with the vendor.

  • Read stats — Available to anyone at no cost; a description of intended use is required.

  • Algolia token — Available to anyone for a prepaid fee based on expected usage. If actual usage exceeds the estimate, additional charges apply. Pricing follows Algolia’s model at €0.50 per 1,000 requests.

Contact us

The policies described in this article, including any associated fees, may change over time. We may update access requirements, adjust pricing, or introduce new conditions as our services evolve. Users are responsible for reviewing the most current information, and changes take effect once published.