Asana

QuotaGuard routes customer-controlled Asana API traffic through the two fixed IPv4 addresses assigned to its subscription. Add both addresses to the Enterprise+ IP allowlist, then separately enable Apply to API traffic so controlled integrations keep an approved network source. QuotaGuard has provided static-IP proxy service since 2013.

• Two-Minute QuotaGuard Setup: Add the QuotaGuard connection URL to the application, configure its HTTP client to proxy Asana requests, and register both dashboard IPs. Enabling and validating Asana's administrative policy is a separate cutover step.
• Enterprise+ API Filtering: Asana's API option is separate from browser allowlisting and off by default. A super admin enables it under IP Allowlisting in the admin console.
• Programmatic Access Coverage: Asana says the network rule covers personal access tokens, OAuth apps, service accounts, SCIM, and other identity-provider provisioning endpoints.
• Controlled Integration Path: Use QuotaGuard for custom applications and internally managed clients that can route HTTPS through a proxy. Public integrations without network or proxy controls remain outside this path.
• Production-Grade Reliability: Each subscription receives two load-balanced static IPs with health checks and automated failover. Add both to Asana so either approved route can reach the API.
• Shield for Regulated Workflows: QuotaGuard Shield encrypts the customer-to-proxy hop while preserving the application's HTTPS session to Asana without decrypting its payload. Use Shield when QuotaGuard's regulated-data position or an internal control requires that protected hop. It does not make the Asana environment compliant by itself.

Asana policy note: Asana recommends API filtering for integrations behind a controlled network or proxy with stable addresses. For public or cloud-hosted apps whose source cannot be controlled, Asana recommends App Management and Integrations controls instead of relying on an IP rule.