Skip to main content

Onboarding Teams

Use this guide after the first login. Complete it before the platform becomes part of the production infrastructure.

Define ownership at the start​

Assign a clear owner for each of these areas:

  • Policy approval and rollback decisions.
  • Daily monitoring of blocked or escalated traffic.
  • Incident follow-up for evidence of misuse or configuration drift.
  • Audit and evidence export workflows.
  • Budget and billing oversight.

First-week checklist​

  1. Make sure that you know the available environments and the production environment.
  2. Review a small sample of governed Events and their request IDs with verdictan events or GET /v1/events. Set since. If history capture is enabled, review the permitted session context.
  3. Identify the applicable capture mode and platform retention policy.
  4. Agree on the verdict patterns that must have same-day follow-up.
  5. Document who approves policy edits and who can start a rollback.
  6. Define the team handoffs for inbox reviews, audit exports, and billing alerts.

Connected organization readiness​

Before you complete onboarding, make sure that the connected organization can route governed traffic:

  1. Add one provider key for each provider that you plan to use.
  2. If your rollout uses labels, add the same routing labels to each related resource.
  3. Use the authenticated provider-key access API to attach the policy role that grants the agent access.
  4. Use the simulation endpoint of that API. Make sure that the decision is allowed.
  5. Do not send production traffic until the simulation returns this decision.
  6. The active console does not give these role-binding and simulation controls. Follow Providers & BYOK Routing for the necessary endpoints and permissions.
  7. If your rollout uses paid features or automatic top-up, open Bills or Payments. Verify payment readiness.
  • Daily: review inbox items and unexpected request outcomes.
  • Weekly: compare rollout changes with Events from verdictan events or the Events API, their request IDs, and Trail activity. Add History when you must examine capture-enabled session context.
  • Monthly: verify that role assignments, review queues, and billing controls match team responsibilities.

Feature checklist for onboarding completion​

Before onboarding is complete, make sure that the team used each primary feature one time:

  • Overview for daily health signals.
  • Templates for starter policy guidance.
  • Configurations for versioned rollout.
  • Gateways for runtime state.
  • verdictan events or GET /v1/events with since set, plus request IDs, for runtime outcomes.
  • History for captured session context if history capture is enabled. The data must also be available for the period that the platform retention policy allows.
  • Inbox for human-review work.
  • Trail for audit and evidence export.
  • Settings, Organization, Bills, and Payments for access and commercial controls.

Signs that onboarding is not complete​

  • Team members can log in but do not know who owns a policy decision.
  • Review work is shown but nobody knows which workflow or queue handles it.
  • Evidence exports are available but are not connected to incident or audit processes.
  • Spend controls are available but nobody owns payment readiness or budget changes.

Next steps​