Onboarding Flows

Use this page to select the shortest correct onboarding path for a new Verdictan user or team.

Select the right flow

Starting point	Best for	Primary outcome
Console access	New users who examine or manage the organization	Verify organization access and open the correct working surface
Application integration	Developers sending traffic through Verdictan	Create a request token and send the first governed request
Gateway setup	Teams running verdictan gateway run in their own environment	Register a runtime, connect it, and verify traffic
Team setup	Organizations onboarding multiple groups	Invite members, assign access, and clarify ownership

Workflow map

Flow 1: Console access

Use this flow when the user starts from the Verdictan console.

1. Open the console URL for the correct environment.
2. Sign in with the identity method your organization supports.
3. Open the account menu and make sure that the organization name and ID are correct.
4. Open core pages such as Overview, Gateways, and History. Verify that they show the correct organization.

The shell does not display an environment or role label. Verify access by opening the permitted surfaces or examining the role assignment in IAM.

This flow is complete when the user can open the correct organization with no permission errors.

Flow 2: Application integration

Use this flow for a developer who sends governed requests from an application.

1. Create or get the request token for the application.
2. Point the SDK or client at the Verdictan gateway URL. Do not use the upstream provider URL.
3. Send a test request.
4. Make sure that the authenticated response succeeds.
5. Find its request ID with verdictan events tail --since 10m --json or GET /v1/events?since=10m.
6. When history capture and control-plane delivery are enabled, verify the retained session context in History.

Use this flow for application traffic. Keep runtime tokens different from ordinary request tokens.

Flow 3: Gateway setup

Use this flow when your team runs the gateway in its own environment.

1. Install verdictan on the target machine.
2. Export the runtime connection variables for your deployment.
3. Start the gateway with verdictan gateway run.
4. Verify that Gateways shows the runtime as healthy.
5. Send a representative request and verify its request ID and outcome with verdictan events tail --since 10m --json or GET /v1/events?since=10m. Examine History only when conversation capture is enabled.

Use Install the Gateway and Quickstart for the setup steps.

Flow 4: Team setup

Use this flow when more than one team or working group will use the organization.

1. Invite the team members.
2. Assign the minimum access that is necessary for each person.
3. Name the owners of policy changes, inbox review, audit exports, and spend oversight.
4. Verify that each person can open only the surfaces specified for their role.

This flow is complete when ownership is clear and the organization is usable without manual intervention.

Signs onboarding is complete

Onboarding is complete when all of these statements are true:

• The necessary users can sign in to the correct organization.
• One governed request succeeded.
• verdictan events tail or the Events API returns the matching request activity.
• For a capture-enabled flow, History also shows the session context.
• The team knows which token or credential is used for request traffic versus runtime connectivity.
• Ownership for policy changes and investigations is clear.

Next steps

• Quickstart
• Install the Gateway
• Customer Journeys