Dashboard

Project Settings

Configure detection, enforcement, and governance settings per project

Overview

Each project has three settings sub-pages, reached at:

/dashboard/{orgId}/{projectId}/settings/{agentshield,bouncer,enforce}

These are the legacy per-project settings pages. They still resolve and work, but the current dashboard surfaces most of the same information elsewhere: Installations for setup status and credentials, and Policy → Auth for authentication-method, consent, and tool-protection configuration. The sections below describe what each legacy page actually shows today.

Detect overview

Detect overview (URL segment settings/agentshield) is a legacy per-project settings page. It shows Detect status and installation details for the project:

  • Project details: project name, site URL, Project ID, creation date, and tracking mode
  • Pixel and Middleware installation snippets

This page does not manage your API key. Your Project ID is at the top of Installations, and the API key is in its install snippets: see Credentials.

Settings for Govern

Settings for Govern (URL segment settings/bouncer) is a legacy per-project settings page managing KYA-OS governance configuration:

  • Project details: the same project identity fields as Detect overview
  • Authentication methods: configure the OAuth or credential providers agents authenticate with, and assign discovered tools to each one (labeled Sign-in methods in the shipped consent-editor UI)

The current primary path to this configuration is Policy → Auth. See Control Access (legacy) for how the two surfaces relate, and Authentication Methods for the underlying concepts.

Enforce overview

Enforce overview (URL segment settings/enforce) is a legacy per-project settings page configuring gateway and enforcement domain settings:

  • Gateway status: connection status for your Vouched KYA Gateway deployment
  • DNS configuration: the DNS records required to enforce this domain

For gateway setup instructions, see Gateway Enforcement.

Next Steps