Authentication events

An authentication event is the record of a single product check. Each event carries an outcome, a processing state, the product and brand it belongs to, where and when it was captured, and the evidence behind the result. Triaging events is the core operational task in the dashboard.

Outcomes

Every authentication event resolves to one of four outcomes:

• Authentic — the product passed authentication. No action is normally required.
• Not Authentic — the product failed authentication. Treat as a likely counterfeit and follow your brand’s escalation process.
• Uncertain — the result is ambiguous and needs a human decision. These are the events that most reward attention, and they are often caused by image quality rather than by the product itself.
• Error — the check could not be completed because something went wrong during processing.

Outcomes are never communicated by colour alone; each carries a text label so the state is unambiguous. Your tenant can customise the wording for a given product — for example, a cap-type product may read Sealed / Open instead of Authentic / Not Authentic — but the colour always follows the canonical meaning (green for positive, red for negative).

States

Alongside its outcome, an event has a processing state that tells you where it is in its lifecycle:

• Pending — received, not yet processed.
• In Progress — being processed.
• Completed — finished, with a final outcome.
• Expired — the capture session timed out before it could complete.

Event types

• Authentication — a standard check that produces an outcome.
• Data collection — a capture submitted as labelled training data. It is stored and labelled by the inspector but produces no authentication verdict.

Triaging the queue

1. Scan the queue. Work newest-first, or filter to a brand, product, outcome, or time window to focus.
2. Open an event. Review its outcome, state, and the evidence and metadata captured with it. You can zoom and pan the evidence images to inspect detail — scroll or use the on-screen controls to zoom, drag to move around, and reset to fit.
3. Decide. Confirm the outcome or route the event for follow-up according to your process. Uncertain events and inspector disagreements flow to the Review Center.
4. Clear your queue. The goal of a session is to leave no event unreviewed.

Tip

A run of Uncertain results usually points to capture conditions rather than the products themselves. Before escalating, check the captures against Capturing good images.

Removing an event

When an event needs to be taken down — for example a capture that contains inappropriate or sensitive content — you can delete it from the event’s detail view with Delete event. This permanently removes the event and its captured images and cannot be undone, so you are asked to confirm.

You can delete only your own events, and only once they have finished processing (a Completed or Expired state). Deleting an event from the dashboard also removes it from the capturing device’s Event History.

Use the dashboard’s filters to cut the queue down to what matters — see Using the dashboard for the full set of filters and the review workflow.