How It Works
When you configure an IP access list, Devin enforces it at the enterprise level:- API requests from IPs not in the access list are rejected with a
401 Unauthorizedresponse - Webapp access is restricted to users connecting from allowed IP ranges
Configuring IP Access Lists
IP access lists are managed via the Enterprise API v3. The following operations are available:Viewing the Current Access List
Retrieve the current IP access list for your enterprise:Replacing the Access List
Replace the entire IP access list with a new set of IP ranges:ip_ranges field containing an array of IP ranges in CIDR notation. Individual IP addresses can be specified with a /32 suffix.
Clearing the Access List
Remove all IP restrictions by clearing the access list:Permissions
Viewing and managing IP access lists requires theManageIPWhitelist (“Manage IP Whitelist”) permission. This is typically available to enterprise administrators, and can be granted to a custom role. Note that ManageEnterpriseSettings does not grant IP access list management.
Best Practices
- Include all office and VPN egress IPs before enabling the access list to avoid locking out users
- Use CIDR ranges instead of individual IPs where possible to simplify management
- Test with a broad range first, then narrow down as needed
- Keep a record of configured ranges outside of Devin in case you need to restore access
If you accidentally lock yourself out by configuring an incorrect IP access list, contact support@cognition.ai for assistance.

