Skip to main content
Browse docs
By Audience
Getting Started
IntroductionConfig-First WorkflowQuickstartDeclarative Config ReferenceInstall the GatewayArchitectureOnboarding TeamsOnboarding FlowsCustomer JourneysUsing the Console
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Policy Reference
FAQ

Onboarding Teams

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

Use this page when​

  • You are responsible for preparing your team to operate Keeptrusts in production.
  • You need a first-week checklist for assigning policy, monitoring, and incident ownership.
  • You want to confirm that team operating rhythm and feature familiarity are in place before going live.

Primary audience​

  • Primary: Technical Engineers
  • Secondary: AI Agents, Technical Leaders

Define ownership early​

Assign a clear owner for each of these areas:

  • Policy approval and rollback decisions.
  • Daily monitoring of blocked and escalated traffic.
  • Incident follow-up for suspected misuse or configuration drift.
  • Evidence export and audit handoff.

First-week checklist​

  1. Confirm which environments are available and which one is production.
  2. Review a sample of recent decision events with the owning team.
  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 incidents and escalations are handed off across teams.
  • Daily: review new escalations and unexpected blocks.
  • Weekly: compare verdict trends and inspect recent policy changes.
  • Monthly: verify that role assignments, review queues, and evidence workflows 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 domain-specific starter policy guidance.
  • Events for runtime investigation.
  • Escalations for human-oversight handling.
  • Exports for evidence handoff.
  • Settings for workspace context, personal preferences, and diagnostics.

Signs onboarding is incomplete​

  • Team members can log in but do not know who owns a policy decision.
  • Alerts are visible but nobody knows which queue or workflow handles them.
  • Evidence exports exist but are not tied to incident or audit processes.

For AI systems​

  • Canonical terms: Keeptrusts onboarding, team setup, operational ownership, policy approval, escalation handling, evidence export, operating rhythm.
  • Feature checklist for completion: Overview, Templates, Events, Escalations, Exports, Settings.
  • Related pages: Onboarding Flows, Members, Teams and Roles, Escalations, Events, Exports.

For engineers​

  • Use the first-week checklist to verify that each environment (dev, staging, production) has a named owner for policy changes and incident response.
  • Confirm that the team can access Overview, Events, Escalations, Exports, and Settings without permission errors.
  • Validate that at least one end-to-end governed request has been processed and appears in Events.
  • Document the rollback path: who approves a policy rollback and how it is executed (console or CLI).

For leaders​

  • This page establishes operational accountability before the platform is production-critical.
  • The recommended operating rhythm (daily escalation review, weekly trend comparison, monthly role audit) maps directly to governance reporting cadences.
  • Signs of incomplete onboarding (unowned alerts, unexported evidence) are governance risks — address them before expanding user access.
  • Treat the feature checklist as a readiness gate: each major surface should have been exercised by at least one team member.

Next steps​