FAQs
Common questions about Asana static IPs and QuotaGuard.
Does an Asana API integration need a static IP?
It needs an approved source when an Enterprise+ super admin enables the separate Apply to API traffic option. The main IP allowlist governs browser access by default and does not restrict API requests on its own. A customer-controlled integration with changing cloud egress can use QuotaGuard to arrive from the same two approved IPv4 addresses.
Which Asana plan includes API Traffic Filtering?
Asana currently lists IP allowlisting and API Traffic Filtering on Enterprise+. Its July 2026 release notes describe the API option as extending the same network policy across browser and programmatic access. Confirm the feature in the domain's admin console before planning enforcement.
Where does a super admin enable Asana API filtering?
Open the admin console, find IP Allowlisting under Security, define the approved addresses or ranges, enable the allowlist, and separately select Apply to API traffic. Asana requires the super admin's current IP to be included before the settings can be saved or enabled. The API option is off by default even when browser allowlisting is active.
Which address formats does Asana accept?
Asana accepts individual IPv4 or IPv6 addresses and ranges written in CIDR notation. QuotaGuard provides two individual IPv4 addresses per subscription, so add both dashboard values. Do not add the QuotaGuard proxy hostname because Asana evaluates the source address of the request.
Which Asana credentials and endpoints are covered?
Asana says API Traffic Filtering covers all programmatic access to the domain, including personal access tokens, OAuth apps, service accounts, SCIM, and other identity-provider provisioning endpoints. The network rule works alongside each credential's existing permissions. It does not convert one credential type into another or replace token management.
Will QuotaGuard fix every public Asana integration?
No. The customer must control the application or HTTP client well enough to route its Asana requests through QuotaGuard. Asana warns that public integrations and cloud-hosted apps with uncontrolled dynamic addresses may stop working under API filtering. For apps that cannot use a proxy, Asana recommends its App Management and Integrations controls instead of an IP-based rule.
How do I move a custom Asana integration onto QuotaGuard?
Create the QuotaGuard route in the application's HTTP client, confirm it exits through one of the subscription's two dashboard IPs, and add both IPs to the Asana allowlist. Test a harmless authenticated API request through the proxy before enabling Apply to API traffic. Keep the previous approved network path available until every controlled integration and provisioning client has passed the test.
Should I use QuotaGuard Static or Shield for Asana?
QuotaGuard Static is sufficient for most Asana API integrations. The application's HTTPS session to Asana remains encrypted and QuotaGuard does not decrypt its payload. Shield additionally encrypts the customer-to-proxy hop. Use Shield when the workflow carries regulated data covered by QuotaGuard's HIPAA or PCI-DSS product position, or when an internal control requires TLS on every hop. Neither product makes the Asana environment compliant by itself.
Can I get dedicated IPs for Asana?
Yes. Dedicated IPs and proxy resources are included on direct Enterprise plans, currently $219 per month for QuotaGuard Static and $269 per month for QuotaGuard Shield. Starter, Production, and Business use shared static IP pairs. The two addresses assigned to each subscription remain fixed for the customer to register with Asana.
Does Asana API Traffic Filtering control webhook delivery?
Do not treat the outbound API rule as an inbound webhook rule. Asana webhooks send HTTP POST events from Asana to a customer-controlled target URL, while this integration covers requests traveling from the customer's application through QuotaGuard to the Asana API. Any inbound webhook access policy must be designed and tested separately for the receiving endpoint.