Control public web access

Open the app’s Access section to see the rules available for its connection.

Access page with public web rules and private-network settings. Example data; available controls vary by app and connection.

Access page with public web rules and private-network settings. Example data; available controls vary by app and connection.

Before adding a restriction

Decide who should reach the website. An allowlist can block your own browser if your public address changes, and country-based restrictions can also affect legitimate visitors or external integrations.

Use the rule types offered by the panel. Add or edit the intended rule, save it, and test from a connection that should be allowed. Where practical, also test from a separate connection that should be denied.

What web access rules do not replace

They are not the application’s user permissions, and do not automatically protect unrelated ports such as SFTP or a dedicated database endpoint. Continue to use application logins and appropriate credentials.

If an integration stops working, check whether a webhook provider or monitoring service has been blocked. Avoid granting broad access solely to fix a problem you have not identified.

For apps that should only be accessible to your devices or team, consider Tailscale or Headscale rather than a public allowlist.

Rule availability depends on the app’s public connection. If controls are absent or disabled, read the explanation in the panel before changing DNS or networking.