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.

Annotated Deploy tab showing IP Access Rules section

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

  1. Log in to app.docketai.com.

  2. Click Marketing Agent Configuration in the left sidebar.

  3. Select the agent.

  4. Open the Deploy tab.

  5. 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

203.0.113.50

IP range

A network range

203.0.113.0/24

ASN

A network provider or autonomous system

AS13335

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

IP Access Rules form with the real network, label, and Add Rule controls
  1. In IP Access Rules, choose the rule type.

  2. Enter the IP address, IP range, or ASN.

  3. Choose whether the rule should allow or restrict access.

  4. Save the rule.

  5. 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

  1. Save the rule and reopen IP Access Rules to confirm it persists.

  2. Test the agent from a network that should be allowed.

  3. Test from a network that should be blocked.

  4. Confirm the rule uses the public IP address, range, or ASN observed by the service.

  5. Keep a recovery path for administrators before applying broad block rules.

Related Articles