Designing Stakeholder-Specific Passport Experiences

See what the public sees on a scan, and what signed-in staff see, from one passport record.

By Jack Cook 12 March 2024
Experience Digital Product Passport Stakeholders

Under the ESPR, delegated acts set the access rights for each product group (Article 9(2)), so not every stakeholder can see the same data. Traced keeps one record per product and shows it in two places: a public scan page that anyone can open, and a batch block that signed-in staff also see.

Define who sees what

Delegated acts set the access rights for each actor, under Article 9(2). Traced's access today is simpler. Anyone can open the public scan page. Signed-in staff also see the batch block, and their access follows one of four roles: Super Admin, Client Admin, Client Manager or Client User.

Control access by role

Traced does not build separate microsites for each stakeholder. Staff sign in with email and password, a six-digit email code, or Google or Microsoft Entra ID single sign-on. Invitations carry a role, so each person sees what that role allows.

Keep earlier versions

Each new version of a passport you upload is saved with its SHA-256 checksum, and earlier versions are kept.

A single scan opens a public page for anyone, and signed-in staff see more. Talk with the TraceID team about how the scan page could work for your products.

Share this article:

Need a clearer record model?

Discuss a practical Traced or Verified setup for your product and inspection workflow.

Talk to us

Related Articles

Book a demo