Who can see your DPP data?

Full video transcript

Who can see the information in a digital product passport? The answer depends on what has been published and what the viewer is allowed to access. A public product page and a supplier's supporting records serve different purposes. Scanning a code should not automatically open every file behind the product.

Imagine a jacket with a product passport. A shopper wants care instructions and material information. A supplier needs to answer a request about the fabric it provides. An internal reviewer needs the supporting record and the review history. These are three different tasks, even though they relate to the same jacket.

Start with the public view. Choose the information intended for anyone who opens the product link. In our example, that includes the jacket's reviewed material information and care guidance. Treat public information as something people can copy or share. Check the text, attachments, and links before making it available.

Now consider restricted records. A supplier declaration, internal comments, or commercial details may need a narrower audience. Decide who needs each record and why. Access should be checked when the record is requested, not simply hidden behind a menu. Knowing a link should not, by itself, grant permission to open a restricted file.

Separate reading from changing. A supplier may be allowed to contribute information for an assigned request without being allowed to publish the finished passport. A reviewer may check the contribution, while a different person approves publication. Define the responsibilities for your workflow, and avoid giving broader access just because it is easier.

Before launch, test the views with separate accounts. Open the public link while signed out. Then check a supplier account and an internal reviewer account. Confirm both what each can see and what each cannot do. Include linked documents and downloads in the check. A good looking page is only part of the test.

Review access when relationships change. A finished project, a departing colleague, or a supplier change can mean permissions need updating. Removing access limits future use through that access path; it cannot retrieve a copy someone already downloaded. Keep sharing decisions deliberate, and review the records that remain publicly available.

In OriginSpan, public passport information is kept separate from restricted content, with controlled access to supporting evidence. Publication versions preserve the history of what was released. Your team still needs to decide the audience, review the content, and check that the configured workflow matches the intended use.

Start with one product and three questions. What can anyone see? What does each authorized partner need? Who may change or publish the information? This jacket is an illustrative access example; requirements depend on the product and its use. Book an OriginSpan demonstration using the link below to explore the right views for your team.