For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Introduction
    • Getting Started
    • Tia — Operations Assistant
    • Architecture
    • Security Architecture
  • Onboarding & Plans
    • Onboarding Overview
    • Plans & Subscriptions
    • Tia Credits
  • Tenancy & Governance
    • Roles & Members
    • Audit Log
    • Notifications
    • Economic Operators
  • Authoring Studios
    • Content Studio
    • Theme Studio
    • Advanced Studio (Track B)
  • Product Module
    • Products
    • Custom Fields
    • Global Search
    • Identifiers
    • Product Import
    • Bulk Editing
    • Bulk Updates
    • Resolver & GS1 Digital Link
    • GS1 Digital Link Contract
  • Localisations
    • Overview
    • Market Packs
    • Multilingual Content
  • Domains & Custom Hostnames
    • Domain Architecture
    • Resolver Domain Flow
    • Custom Hostname Setup
    • DNS Setup Guide
    • Resolver & Passport Rendering
    • Custom Hostname Lifecycle
    • Troubleshooting
  • Passports
    • Overview
    • Passport Operations
    • Lifecycle States
    • Controlled Update & Break-Glass
    • Content & Templates
    • Themes & Presentation
    • Consumer Experience
    • Publication Lifecycle
    • Brand Setup & Readiness
    • Drafts
  • Passport Intelligence
    • Passport Intelligence
    • Intelligence Overview
    • Scan Visibility
    • Trust Signals
    • Engagement Insights
    • Investigation Timelines
    • Data & Privacy
    • Roadmap
  • Minting
    • Overview
    • Lifecycle
    • Architecture
    • Limits & Performance
    • Token Preview
    • Exports & Print Jobs
    • Carrier Output Profiles
    • Bring-Your-Own Serials
    • Security
    • FAQ
  • API Reference
    • API Credentials Guide
    • API: Credentials
    • API: Products
    • API: Identifiers
    • API: Import
    • API: Batches
    • API: Attachments
    • API: Bulk Updates
    • API: Minting
    • API: Resolver
    • API: Search
On this page
  • What a Timeline Contains
  • Identity-Aware Scoping
  • Why It Matters
  • How It Connects
Passport Intelligence

Investigation Timelines

Was this page helpful?
Previous

Data & Privacy

Next
Built with

Investigation Timelines bring scan, trust, lifecycle, and governance events together against a single identity — so brand-protection, compliance, and operations teams can investigate without assembling evidence from disconnected sources.

What a Timeline Contains

Where supported, an investigation timeline can include:

SourceExamples
Lifecycle eventsIssuance, publication, revocation, controlled updates
Scan historyResolver attempts, valid scans, activation events, outcome distribution
Trust eventsDetected signals, severity changes, manual investigations
Governance eventsAuthorised changes, break-glass actions, role-aware operations

These are presented in a single chronological view, scoped to the entity under investigation.

Identity-Aware Scoping

Timelines respect the platform’s identity model. Investigations can be scoped to:

  • a product
  • a passport
  • a batch or lot

This allows operators to ask precise operational questions — for example, “what happened to this lot after activation?” or “why does this passport have a low Trust Score?” — without manually correlating multiple data sources.

Why It Matters

Trust and compliance decisions require evidence. Investigation Timelines turn the platform’s underlying event history into a coherent, defensible record that can support:

  • brand-protection investigations
  • compliance and audit conversations
  • internal incident review
  • partner and customer support

How It Connects

Timelines are surfaced within the relevant Passport Intelligence views so investigators don’t have to leave their workflow. From a Trust Signal drawer, for example, an operator can move directly into the timeline for the affected entity.

For credibility interpretation see Trust Signals; for activity context see Scan Visibility.