P4A DocumentationGlossary
Quick definitions for the terms you'll see in P4A.
Overview
This page provides concise definitions for the key concepts and terminology used throughout P4A.
A–Z
Active business group — an Anypoint business group that the connection's Connected App can currently reach and has at least one active deployment in. Counted in the per-connection and per-workspace Active BGs tile.
Active deployment — a policy deployment whose runtime status is live (published or released). Failed, deleted, or pending rows are not counted. The Active deployments tile and column reflect only this live set.
Active policy — a policy that has at least one active deployment through the connection or workspace. The same policy deployed to several business groups still counts as one active policy. Surfaced in the Active policies tile and card.
Connected App — an Anypoint Platform credential type used to grant P4A permission to publish policies into your Anypoint organisation. See Deploying a Policy for setup instructions.
Idea — a lightweight request for a policy you'd like to see, distinct from a full submission. Ideas help the community understand demand without requiring you to build the policy yourself. See Submitting an Idea for details.
Lifecycle state — the status of your submission as it moves through the review process: submitted, under_review, needs_improvement, published, or rejected. See Lifecycle states under Submitting a policy for what each means and what actions you can take.
PDK — the Omni Gateway Policy Development Kit, MuleSoft's framework for writing custom policies. All policies submitted to P4A must be built using the PDK.
Policy — a piece of code that runs in the gateway request path to enforce rules or modify behaviour. Common examples include authentication checks, rate-limiting, request transformation, or security filtering.
Policy submission — a public PDK policy project that you've pointed P4A at for review and listing. Once approved, your submission appears in the policy library and can be deployed to Anypoint Platform. See Submitting a Policy for the full process.
Vault — the encrypted store where P4A keeps your Connected App secret at rest. Secrets are encrypted using Supabase Vault and are never exposed in plaintext through the interface.
Workspace — the unit in P4A that owns Anypoint connections and deployments and groups members for sharing. Every account has a personal workspace; users can also create or join shared workspaces. Each membership has a role — Owner, Admin, or Member — that controls what you can do. See Using workspaces.