Postman console environment variable masking: per‑project toggle

When running a collection during a deployment, the Postman Console is the primary source for debugging failed requests. The console logs the request URL, headers, and response body, but it also redacts any environment variable values that match certain sensitive patterns. This redaction is applied globally across all projects and cannot be disabled or customized per environment or collection.

The lack of a per‑project or per‑environment toggle means that critical values—such as a database connection string or an API key—are replaced with ‘****’ in the logs. Consequently, developers lose visibility into the exact payloads sent to external services, making it difficult to pinpoint why a deployment failed.

What options exist to disable or configure masking for a specific environment or collection? Which regex patterns are used by default, and can they be overridden? Is there a roadmap for adding a per‑project masking toggle in a future release?