Checkpoint Docs
Govern (KYA-OS)

Control Access

Configure agent permissions, consent screens, and tool protection from the dashboard

Overview

Control Access is the legacy dashboard surface for Govern configuration. Most of what it covered — provider and auth-method configuration, consent branding and copy, and per-tool protection — now lives at Policy → Auth:

/dashboard/{orgId}/{projectId}/policy/auth

A few capabilities have not moved yet. They remain on the legacy Control Access pages (and are moving to the future Access surface):

/dashboard/{orgId}/{projectId}/control-access/{config,consent,tools}   (legacy surface)

What Moved to Policy → Auth

The Policy → Auth page walks one three-screen journey — Auth → Consent → Success — and covers:

  • Auth methods and providers — Configure OAuth providers, credential providers, or consent-only access, and the scopes each protection grants
  • Consent branding and copy — Customize the consent and success screens agents see
  • Per-tool protection — Assign each discovered tool an owning protection in the tool coverage table; unassigned tools stay open

For the underlying concepts, see Authentication Methods, Consent Flows, and Tool Protection.

What Still Lives Here (Legacy Surface)

CapabilityLegacy page
Tool discovery and manual removal.../control-access/tools
Per-tool scope display.../control-access/tools
OAuth scope refresh.../control-access/config
Terms of Service / Privacy Policy URLs.../control-access/consent
Secondary brand color.../control-access/consent
Connect-page preview.../control-access/consent?tab=connect

These legacy pages still resolve and work — they are just no longer the primary surface. They are moving to the upcoming Access surface; everything else should be managed at Policy → Auth.

Consent configuration can be read via the API:

GET /api/v1/bouncer/projects/{projectId}/consent-config

The endpoint is read-only — edits happen in the dashboard consent editor (Policy → Auth for branding and copy; the legacy consent page for ToS/privacy URLs, secondary color, and the Connect preview). See Consent Flows for details.

Next Steps