Admin onboarding

If you're the person rolling Validera out to your team, this is your sequence. Ten minutes to first agent on the system.

1. Sign in to the dashboard

1. Go to app.validera.io.
2. Paste the tenant API key supplied by your Validera contact (it starts with vld_ or qag_). The key is your team's identity — it's what scopes everything you see in the dashboard to your team only.
3. You'll land on the Metrics page. Empty for now if no agents are running yet.

2. Add your agents

An “agent” is a person on your team who will use the Chrome extension to verify bookings. Each agent needs to be added to the dashboard before they can install and sign in.

1. Click Setup in the dashboard nav.
2. Scroll to the Agents section.
3. For each agent, fill in three fields:
   • Agent ID — a short identifier you'll use in reports. Often the staff number or the email local-part (e.g. jsmith).
   • Display name — how the agent appears in the override audit trail (e.g. Jane Smith).
   • Google email — the work Google account the agent will sign in with. This is the one that matters most: the extension reads the agent's Google profile email and looks up which team they belong to. If this email doesn't match, the agent gets a “not found” error.
4. Click Add agent. The new row appears in the agents table.

3. Share the install link with your agents

Send your team the unlisted Chrome Web Store install link (your Validera contact will provide this). Point them at our install guide for the steps. Five minutes per person.

If you'd rather force-install via Google Workspace so your agents don't have to do anything, the install guide also covers the admin console steps.

4. Read the metrics

Once agents are running, the dashboard fills in. Here's what you'll see and how to read it:

Top tiles

• Prevented dollars — the dollar amount of overspend on blocked bookings that agents did not override. This is the headline number for your manager: it's the saving Validera produced this window.
• Total verdicts — how many bookings the team ran past Validera, with the pass / warn / block split.
• Block rate — what fraction of all verdicts came back as block. A very high block rate suggests rules are too strict; a very low one suggests they're too loose.
• Override rate — what fraction of warns and blocks the team chose to override. A high override rate may mean the rules don't reflect reality on the ground — check the Recent overrides table for patterns and tell us.

Verdict outcomes per day

Stacked bar chart. Each bar is one day, segmented green/amber/red. Use this to spot trends: a spike in blocks one day usually correlates with a specific incident worth investigating.

Extractions per day & cost

Below the verdict chart you'll see how many tickets the team processed each day, and an estimated Anthropic API spend. Use this to forecast monthly burn for your finance team. The estimate is rate-based today — it'll get more precise as we add token-level logging.

Recent overrides

The bottom-left panel lists the last 20 overrides — who overrode what, on what verdict, with what reason. Read these regularly. Override reasons that are short, vague, or repetitive are a signal that someone needs coaching, or that a rule needs adjusting.

Top firing rules

Bottom-right. The rules that fired the most this window. If a rule is firing constantly and being overridden constantly, it's probably calibrated wrong — tell us.

5. Use the Overrides page for compliance review

Click Overrides in the nav. This is your audit page:

• Default view: every override in the last 90 days.
• Filters: date range, agent, verdict status (warn/block), specific rule ID.
• Export CSV in the top-right of the filter panel: re-runs your current filter and downloads the results. This is what you give to internal audit or external auditors.

6. When something looks wrong

Two channels:

• Product feedback (verdicts that look off, agents struggling, missing features): feedback@validera.io.
• Suspected security or privacy issue: security@validera.io.