6 docs tagged with "console"

API keys are service identities that let OPA/EOPA instances and automation report decision logs and status to EnforceAuth. They are scoped to an entity and carry explicit permission scopes.

A bundle destination is where EnforceAuth publishes OPA bundles after a successful deployment. Your PDPs (OPA, EOPA, or sidecars) pull bundles from this location.

A deployment is how EnforceAuth turns Git policy sources into OPA bundles at your bundle destination. The Deployments page is the audit trail: who triggered what, for which entity and environment, and whether the pipeline succeeded.

EnforceAuth organizes authorization work under entities — a hierarchy of organizations and systems that own policy sources, bundle destinations, environments, secrets, and API keys.

The Policies page is your operational view of authorization policy across every system in the tenant. Use it to understand coverage, find errors, and open the Git-backed editor when you need to change Rego.

A policy source tells EnforceAuth where your Rego (and related policy files) live. On every deployment, the platform fetches from this source, runs tests, builds an OPA bundle, and publishes to your bundle destination.