Setting Up IP Access Rules for Agent Security
Last updated: August 11, 2026
Use IP Access Rules when you need to restrict or allow Marketing Agent access based on network source.
The Deploy tab describes these rules as a way to restrict or allow agent access by IP address, IP range, or ASN.

Before You Start
You have access to the agent in Docket.
You know which IP address, IP range, or ASN should be allowed or restricted.
You understand who should still be able to access the agent after the rule is added.
Open IP Access Rules
Log in to app.docketai.com.
Click Marketing Agent Configuration in the left sidebar.
Select the agent.
Open the Deploy tab.
Find IP Access Rules.
Rule Types
IP Access Rules can be based on:
Rule Type | Use It For | Example Format |
|---|---|---|
IP address | A single known IP address |
|
IP range | A network range |
|
ASN | A network provider or autonomous system |
|
Use the format your network or security owner provides. If you are not sure which value to use, confirm it before creating the rule.
Add a Rule

In IP Access Rules, choose the rule type.
Enter the IP address, IP range, or ASN.
Choose whether the rule should allow or restrict access.
Save the rule.
Test access from an expected allowed network and, if possible, from a restricted network.
Common Use Cases
Use Case | Rule Strategy |
|---|---|
Internal testing | Allow known office, VPN, or staging-network traffic while validating the agent. |
Security review | Restrict access from networks that should not reach the agent. |
Controlled rollout | Limit early access while a campaign or website launch is still being prepared. |
Noise reduction | Restrict known unwanted network sources when they are creating low-quality traffic. |
Best Practices
Start with the smallest change. Add only the rule you actually need.
Use reviewed network values. IP ranges and ASNs should come from your IT, security, or website owner.
Test after saving. Confirm expected visitors can still access the agent.
Document why the rule exists. Keep a short internal note with the owner and reason.
Review periodically. Network ownership can change, and stale rules can block the wrong visitors.
Troubleshooting
Issue | What to Check |
|---|---|
Expected visitors cannot access the agent | Review recent IP Access Rules and confirm the visitor's source network. |
Rule does not appear to work | Confirm the value format and whether the visitor is actually coming from that IP, range, or ASN. |
Testing is inconsistent | Test from a clean browser session and confirm whether a VPN, proxy, or office network is changing the source IP. |
Verify Access Rules
Save the rule and reopen IP Access Rules to confirm it persists.
Test the agent from a network that should be allowed.
Test from a network that should be blocked.
Confirm the rule uses the public IP address, range, or ASN observed by the service.
Keep a recovery path for administrators before applying broad block rules.