> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/workspace-settings/configure-static-ips-for-your-workspace.md).

# Configure static IPs for your workspace

This article describes how Cerby supports running its automations using static IPs for behind-WAF apps.

{% hint style="info" %}
**Who can use this feature?**

* Workspace **Owners**, **Super Admins**, and **Admins**
  {% endhint %}

With Cerby, you can run your apps behind web application firewalls (WAFs) or sophisticated bot-detection mechanisms that frequently block standard IP ranges for all automation jobs.

Cerby ensures that automations originate from a fixed pool of reliable IPs rather than ephemeral cloud addresses. This guarantees that whenever the Cerby agent interacts with an application to perform a job, it comes from a trusted, reputable address that security teams have already allowed-listed. Additionally, the implementation provides session persistence (one IP address per session), so the Cerby agent does not switch identities mid-login, which is a common trigger for security blocks.

## Common use cases

This feature is a universal solution designed for any service that requires IP-based allowlisting, such as the following cases:

* Banking and financial portals with restricted access to known corporate addresses.
* Internal company systems with VPN-less access to internal tools that only permit traffic from trusted origins.
* SaaS platforms with IP restrictions, meaning any app, such as Salesforce or Okta, that enforces an IP allow list.

## Configuration and flexibility levels

The solution is designed with four levels of flexibility, enabling both widespread and granular control over where your automations originate:

* **Workspace (base level):** Sets a default IP pool for your entire organization.
* **App level:** Enables or disables proxying for specific applications or workflows, which is useful for testing a new setup before a full rollout.
* **Account level:** Allows specific accounts to always log in from a specific location or IP address.
* **Automation job (highest priority):** Settings can be passed directly during a specific job execution for one-time troubleshooting or high-priority rotations.

## Enable static IPs for your workspace

The feature is not enabled by default and must be activated by a Cerby Engineer during onboarding or upon request. To enable static IPs for your workspace, complete the following steps:

1. **Activation:** Contact the [Cerby Support](mailto:support@cerby.com) team to request the feature.
2. **Allow-list IPs:** Update the IP addresses to be allow-listed within your target application or corporate firewall. Cerby's Support team will provide you with the list of IPs.
3. **Validation:** Test an automation, such as a password rotation, to ensure the target WAF recognizes the static Cerby IP address as the origin.

Now you are done.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.cerby.com/setup-and-admin/workspace-settings/configure-static-ips-for-your-workspace.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.