Managing Projects
Create, configure, and manage Vouched KYA projects for AI agent detection
What Are Projects?
A project in Vouched KYA represents a single property (website, API, or application) that you want to protect. Each project has its own:
- Project ID and API Key: Credentials for SDK integration
- Detection settings: Classification preferences and sensitivity
- Enforcement policies: How to handle detected agents
- Analytics: Detection data, trends, and reports
Prerequisites
- A Vouched KYA account. If you don't have an organization yet, you'll be prompted to create one the first time you sign in.
Creating a Project
- Sign in to the Vouched KYA dashboard
- Select your organization (or create one)
- Click New in the top navigation, then select New project
- Enter:
- Project Name: A descriptive name (e.g., "Production Website")
- Site URL: The domain you want to protect (e.g.,
https://example.com)
- Click Add Domain
The project is created immediately, and the same dialog expands in place to show the installation steps (toggle them with Hide installation code / Show installation code). Opening the full Installations page for the same integration instructions is a separate action you can take any time afterward.
You can create multiple projects per organization. Use separate projects for different environments (production, staging) or different properties (website, API, mobile).
Project Credentials
Every project has two credentials:
Find both under Installations in the dashboard. See Credentials for the full walkthrough.
Keep your API Key secret. Never expose it in client-side code. The Project ID is safe to use in client-side integrations (Pixel, Beacon).
Project Settings
A project has no separate settings area. Each setting lives on the page that uses it (see Project Settings):
- Installations: setup status, install snippets, and your Project ID and API key (Credentials)
- Policy: the Cedar policies that decide what happens to detected agents (Policies)
- Policy → Auth: the auth methods agents authenticate with, the consent and success screens their users see, and the auth method that protects each discovered tool (Govern)
- Enforce overview: your Gateway and Middleware enforcement; on a project with a Gateway, Configure policy there sets the minimum confidence, default action, allow and deny lists, and path rules (Gateway, Deny List (Legacy))
Installations
Installations provides integration instructions for each detection method:
- Pixel: Copy the script tag, GTM, or React snippet
- Beacon: npm install command and initialization code
- Middleware: Next.js or Express setup code
- Gateway: DNS record configuration, see Gateway
Pixel and Beacon snippets are client-side, so they include your Project ID only, never the API key. Middleware snippets include your API key too when one is available. Gateway needs no code snippet at all; set it up from the Gateway settings page. See Credentials if you need these values elsewhere.
Team Management
Members belong to your organization. To invite one:
- Navigate to Org Settings → Team
- Invite members by email
- Choose a role for the invite:
- Admin: can manage organization settings and members (everything except transferring ownership)
- Member: can access organization projects and basic features
Owner isn't an invite option. It's assigned by transferring ownership of the organization.
Multiple Projects
Common multi-project setups:
Each project has independent settings, policies, and analytics. Use the project switcher in the dashboard sidebar to navigate between them.
Next Steps
- Analytics & Reporting: Understand your detection data
- Detect: Choose and configure detection methods
- Enforce: Set up enforcement policies
- Govern: Configure KYA-OS governance