DPP BUYER GUIDES

Digital Product Passport Access Control: Who Sees What?

Digital product passport access control decides who may read or change a specific piece of product information. A public scan does not mean every source document should be public. Use this guide to turn access requirements into a reviewable matrix and a set of tests for your DPP provider.

Start with the applicable rights, then design roles

ESPR Articles 10 and 11 link access and update rights to the applicable product-group rules. The framework does not give every reader the same view or let a provider invent one universal role list. Have the responsible team identify the requirements that apply to your product before configuring permissions.

Our proposed matrix below is a design aid, not a legal allocation of rights. Replace every example with a decision for your product and record who approved it. Include the information, permitted action, product scope and reason for access.

Keep read and edit permissions separate. A person who can inspect a repair instruction does not automatically need to approve a new version. Likewise, a data contributor may need to submit evidence without having the power to make it public.

References: EU ESPR — Regulation (EU) 2024/1781, Articles 9–11

Start with the applicable rights, then design roles
Illustrative actorPossible task to evaluateDecision to record
Public readerRead released product instructionsWhich exact fields and files are public?
Supplier contributorSubmit evidence for supplied componentsWhich products and submission actions are allowed?
Approved repair organisationRead information relevant to a repairHow is entitlement checked for that record?
Product reviewerApprove a proposed data changeCan the reviewer alter access as well as content?
AuthorityRetrieve information under applicable rightsWhich verified route and scope apply?
Service accountTransfer approved machine-readable dataWhich system, organisation and actions are authorised?

Bind access to the right product and organisation

Avoid a role called “partner” that can see everything by default. Give the technical team a concrete request: this organisation may read these fields for this product set, for this reason. Record how the entitlement begins, when it is reviewed and how it ends.

Imagine a fictional electronics brand working with two repair companies. Company A is approved for one product family. A user from A changes a record identifier in a copied link and receives a file for the other family. The role name was correct, but the product boundary failed.

Include that case in a controlled test environment. Check the downloaded file and API response as well as the page. An interface can hide a button while the underlying service still returns the document. Ask for the expected result and observed result for each path.

Use synthetic records and documents in these tests. Do not expose a real supplier’s confidential evidence merely to demonstrate that access restrictions work.

Distinguish identity checks from permission checks

Authentication checks who or what is making a request. Authorization checks what that requester may do. In a provider review, ask for both decisions: how the identity is established and how permission is checked for the requested record and action.

The Commission’s Self-Hosted Authentication Guide describes a specific Registry-to-operator flow. The host validates the presented token and applies its local requestor policy before serving protected content. Anonymous requests receive the public representation. This describes that integration, not a universal login design for every DPP reader.

The separate Service Account guide describes operator systems authenticating to Registry services. Keep those two directions clear in the project diagram. A working service-account connection does not establish correct permissions on the operator’s hosted product records.

Ask the provider to label each connection with the caller, destination and permitted action. Then review it with the people responsible for identity and product data. Resolve any arrow described only as “secure API” into a specific, testable responsibility.

References: European Commission — Self-Hosted Authentication Guide (listed 30 October 2026) · European Commission — Service Account Technical Integration Guide (listed 30 October 2026)

Test denied requests as carefully as allowed ones

For digital product passport access control, a successful login is only a starting point. Build a test set that includes a public visitor, an allowed user, an allowed user requesting the wrong record and a user whose access has ended. Include attempts to edit as well as read.

For the Registry-to-operator flow covered by the Commission guide, test token validation against its documented requirements. These include signature, issuer, lifetime and audience checks, followed by local authorization. The guide also distinguishes an invalid presented token from an anonymous request; have the implementation team demonstrate that handling.

Consider a fictional supplier whose contract ends. Remove its access, then retry an old session and a previously copied download link. Record any remaining access and compare it with the agreed revocation behaviour. Do not assume changing a role label invalidates every earlier grant.

Test exports, search results and error responses too. Ask whether a denied response reveals another organisation’s name or document details. Keep the result report focused on permitted data, without copying protected content into widely shared logs.

References: European Commission — Self-Hosted Authentication Guide (listed 30 October 2026)

Make changes to access reviewable

Treat permission changes as product operations with a named owner. Record who requested the change, which scope changed and who approved it. Keep a way to review past decisions without placing credentials or full confidential documents into the audit record.

Review access when a supplier changes, a staff member leaves or a new product family is added. Assign an owner to shared service accounts as well as people. Ask how the team detects accounts that still exist but no longer have a business purpose.

Include a deliberate public-release decision for documents. A new version may contain information that was absent from the earlier public file. In a fictional materials report, an updated attachment adds a private supplier contact page. Reusing the old file’s visibility without review would miss that change.

Define how an accidental release is handled: stop further access, identify the affected version, review exposure and replace it through the approved process. Have the relevant security and privacy owners define any notification obligations for the actual incident.

Take an access matrix into the provider demonstration

Send a small matrix and fictional test records before the demonstration. Ask the provider to show the allowed and denied paths. A role-management screenshot does not show whether the same rule covers pages, downloads and machine access. Request the following evidence with the results.

Digital product passport access control is ready for your agreed pilot when the responsible owners accept the matrix and the observed tests meet it. Keep unresolved permissions visible as release blockers rather than quietly granting broader access.

Use the data-requirements guide to decide what information is in scope and the implementation checklist to assign sign-off. Include the matrix and revocation process in your migration plan so a future provider change preserves the decisions.

  • A public request that returns only the approved public fields and files.
  • An allowed user reading the right record, then being denied a record outside that scope.
  • A revoked user retrying an old session and a copied file link.
  • A contributor submitting a change without gaining permission to publish it.

Sources and review context

Sources were reviewed for this editorial guide on 4 November 2026. Provider descriptions are attributed public statements. This guide does not report hands-on software testing or certify regulatory compliance. Check the current original source when a detail affects your decision.

  1. EU ESPR — Regulation (EU) 2024/1781, Articles 9–11
  2. European Commission — Self-Hosted Authentication Guide (listed 30 October 2026)
  3. European Commission — Service Account Technical Integration Guide (listed 30 October 2026)
How DPP Atlas reviews evidence