Client dashboard: what every section does
A practical map of the DPP Shield client workspace: what each dashboard section owns, who can use it and the usual next step.
DPP Shield editorial team · Updated:
The client dashboard is a role-aware workflow: create product records, build and validate passports, attach evidence, collaborate with suppliers, then publish a redacted public view. Each section owns one stage of that record; the dashboard and passport dossier link the stages together without treating a screen result as certification.
Where should a new product start?
Start with Products, then create the product identity, category and economic-operator details before opening Passports. The category selects the schema and rule pack used by the guided form. Imports and the paid Data-entry service are alternative intake paths; both still create ordinary product and draft-passport records that your team must review.
Dashboard and Analytics are read models, not another place to edit the portfolio. Dashboard highlights published coverage, drafts, evidence expiry, next actions and dated obligations. Analytics groups the same tenant data by category and status, and treats any unavailable metric as unavailable rather than as zero.
How does a passport move from draft to public?
In Passports, complete the category fields, save an immutable version, choose the relevant market scope and run validation. A result is a stored comparison of declared data with the selected versioned rules; it is not a compliance certificate. Use the passport dossier to open the specialist analyses for that same passport, fix supported findings, then inspect the public preview and publish.
Products holds reusable catalogue facts; the passport is the versioned declaration. Labels, carrier formats, GS1 Digital Link, serialization, lifecycle, ownership, leasing, redactions, translations and credentials are passport-level controls, so changes remain attributable to a version and its audit history.
What belongs in evidence and supply chain?
Documents is the evidence vault: upload the source file, check its hash, dates, extracted suggestions, access level and any supersession chain. Suppliers holds counterpart records, capabilities, invitation requests and response/risk signals. Sourcing proposes alternatives only from recorded capabilities, while Cross-reference tests whether declared passport values and evidence statements agree.
Do not use a supplier response or an AI suggestion as verified proof by itself. Review it, connect the supporting document to the declaration and retain the final judgement. Support chat is the shared organization channel for a product or workflow question, not a public passport comment surface.
Which compliance analysis should the team open?
Substances screens declared composition against the reviewed candidate-list subset and prepares SCIP gaps. Materials checks durability, repairability, recycled-content claims and the evidence behind them. Chemicals classifies declared components and prepares a safety-data package; Construction assembles construction-specific DoP, EPD and taxonomy views; Carbon & LCA produces a declared-data report and baseline; Regulatory watch compares captured pack versions and their impact.
These screens describe their source, calculation basis, unresolved data and scope. A clear-looking screen only means the available declarations matched that module's reviewed logic; it never proves that an undeclared substance, supplier fact or law does not apply.
How do publishing and market delivery work?
Localization keeps machine translations as drafts until a reviewer approves them for the public passport. Channels checks a passport against the reviewed Amazon, Zalando or Shopify attribute profile, creates a feed and records its hash, dispatch and any marketplace acknowledgement. A prepared or dispatched feed is not a completed listing until the channel acknowledgement is recorded.
Use the public-preview and redaction controls before any QR, Digital Link, widget, credential or channel feed is shared. Redaction changes the public projection itself, so withheld fields stay out of the public page and its reuse surfaces.
Who administers the workspace?
Users, Workspaces, My account and Team settings manage membership, role and personal context. Owners and admins additionally see the admin overview, audit log, security, SSO, SCIM, notifications, billing, API keys, GS1 prefixes, custom rules, extensions, webhooks, EPCIS, credentials, regulators, privacy and retention. Editors and viewers only see the pages their role permits; a rédacteur sees the assigned data-entry workspace instead.
Use Security before enforcing MFA or SSO, Billing before a capacity limit blocks work, and Audit log after a sensitive change. Custom rules and extensions are organization requirements, not substitute law; privacy erasure and retention have deliberate limits because traceability evidence and the audit log must survive.