Skip to main content

Onboarding Teams

Use this guide after first login and before the platform is treated as business-as-usual infrastructure.

Define ownership early​

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 suspected misuse or configuration drift.
  • Audit and evidence export workflows.
  • Budget and billing oversight.

First-week checklist​

  1. Confirm which environments are available and which one is production.
  2. Review a small sample of governed Events and their request IDs with kt events or GET /v1/events with required since. If history capture is enabled, also review the captured session context permitted by the capture mode and platform retention policy.
  3. Agree on which verdict patterns require same-day follow-up.
  4. Document who approves policy edits and who can execute rollback.
  5. Decide how inbox reviews, audit exports, and billing alerts are handed off across teams.

Connected organization readiness​

Before you treat onboarding as complete, confirm the connected organization can actually route governed traffic:

  1. Add at least one provider key for the providers you plan to use.
  2. Tag the provider key, agents, and gateway/configuration with the same routing labels when your rollout depends on labels.
  3. Use the authenticated provider-key access API to attach the policy role that grants the agent access.
  4. Use that API's simulation endpoint to confirm the decision is allowed before you send production traffic. The current console does not mount these role-binding and simulation controls; follow Providers & BYOK Routing for the exact endpoints and permissions.
  5. Open Bills or Payments and confirm payment readiness if your rollout depends on paid features or auto top-up.
  • Daily: review inbox items and unexpected request outcomes.
  • Weekly: compare rollout changes with Events from kt events or the Events API, their request IDs, and Trail activity. Add History when capture-enabled session context is required.
  • Monthly: verify that role assignments, review queues, and billing controls still match team responsibilities.

Feature checklist for onboarding completion​

Before you consider onboarding complete, make sure the team has touched each major feature at least once:

  • Overview for daily health signals.
  • Templates for starter policy guidance.
  • Configurations for versioned rollout.
  • Gateways for runtime state.
  • kt events or GET /v1/events with required since, plus request IDs, for runtime outcomes.
  • History for captured session context when history capture is enabled and the relevant data remains available under the platform retention policy.
  • Inbox for human-review work.
  • Trail for audit and evidence export.
  • Settings, Organization, Bills, and Payments for access and commercial controls.

Signs onboarding is incomplete​

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

Next steps​