Projects created after API Keys (v3) launched can only create API keys scoped by portal role and content-access role. There is no way to generate a single, project-wide credential restricted only by HTTP method, independent of any role or content scope.

Add an option, available regardless of a project’s creation date, to generate a project-wide API credential restricted only by HTTP method (GET, POST, PUT, DELETE), with no role or content-scope configuration required.

Benefit: Administrators could connect simple, method-based integrations without first configuring granular portal and content roles, and could build or migrate automations that depend on a single, unrestricted, method-scoped credential rather than a role-scoped one.