Skip to content →
Log in

Access policies

Control which subjects receive routes to private services.

Access policies decide which users, groups and devices receive routes to which services, and through which gateways. They live under Network → Access on the Access Policies tab. Access is default deny: traffic that matches no policy is denied by an implicit lowest-priority rule. Access policies are separate from gateway Firewall rules and from egress policies.

Sanitized Access policy list showing status, effect, subjects, services, gateways, and order

The list exposes the fields that determine policy evaluation and provides simulation and history actions.

Before you start#

  • Viewing needs policies:view. Add Policy and Clone policy need policies:create (owners, admins and users). Editing, toggling and reordering need policies:update; Delete policy needs policies:delete (owners and admins).
  • A policy must reference at least one service, and the control plane skips policies with no services when it builds routes. You can publish the service first, or create it from the policy form with + New service, which needs services:create.
  • The page loads devices, policies, groups, users, egress policies and routing rules together. If any call fails you see Policy data is unavailable. Reload before making changes. Do not recreate policies that appear to be missing while that banner is up.

Create or edit a policy#

  1. Open Network → Access and click Add Policy, or choose Edit policy on a row.
  2. Under Basic Information enter a Policy Name (3 to 100 characters, unique within the tenant), optional Notes and Tags.
  3. Under Effect & Priority choose Allow or Deny and set Priority (0 to 10000, default 100). Lower numbers evaluate first. The Position: X of Y line shows where the policy lands relative to the others.
  4. Under Who (Subjects) either tick All subjects or select Users, Groups and Devices. Selections form a union. A selected scope with nothing selected matches nobody.
  5. Under What (Resources) select at least one Service, then tick All tenant gateways or select specific Gateways. A selected gateway scope cannot be empty. Each service in the picker shows its address and its protocol and ports, for example 10.0.0.5 · TCP:22.
    • To add a service that does not exist yet, click + New service beside Services (or Create a service when there are none). See Create a service from the policy form.
    • If a selected service has a port list or range and a gateway in scope runs a release older than 2.21.8, the form shows Some gateways enforce only one port. Those gateways enforce only the lowest port until they are updated.
  6. Review When (Conditions). Conditional policies are unavailable until their restrictions can be enforced. The console will not save a policy that carries conditions, and the control plane refuses to publish the tenant’s routes while any enabled policy still has them.
  7. Read any Potential Policy Conflicts warning, then click Create Policy or Save Changes.

Validation messages include Policy name is required, Policy name must be at least 3 characters, Policy name must be less than 100 characters, A policy with this name already exists, Priority cannot be negative, Priority cannot exceed 10000 and Select services and any required subjects or gateways, and remove unsupported conditions.

Create a service from the policy form#

+ New service opens the New Service dialog without leaving the policy form, so nothing you have entered is lost.

  1. Optionally pick an Application Type. SSH, RDP and Web fill in the protocol, ports and health check, as on the Services page.
  2. Enter the IP address or CIDR, for example 10.0.0.5 or 10.0.0.0/24.
  3. Check Protocol and Ports. Ports take a list or ranges, such as 22, 80, 443 or 8000-8100; leave it empty for all ports.
  4. Under Gateways, pick the gateways that can reach the address. Leave it empty to advertise it on all gateways.
  5. Service Name is filled in from the type and address, for example SSH 10.0.0.5, until you change it.
  6. Click Create Service. The dialog closes and the new service is selected in the policy.

The dialog shows the health check the service will get and uses the same validation as the Services page. It creates IP address or CIDR services only; for a service on the gateway itself, use open the full service form.

Clone policy opens the form prefilled as Copy of <name> with priority one higher than the source.

Add Policy form with name, notes, tags, effect, priority and subject pickers

Name, notes and tags come first; the Position line under Priority shows where the policy lands in the evaluation order.

Read the list#

Search by name, notes or tag. Filter by All, Allow, Deny and by All, Enabled, Disabled. With the default priority sort and no filters, drag rows to reorder; the console shows Policy order updated.

ColumnMeaning
StatusEnabled switch. Disabled policies are ignored during evaluation
PolicyName, notes, tags and any stored conditions
EffectAllow or Deny
SourcesNamed devices, users and groups, or All devices, or No matching subjects
ServicesServices with protocol, ports and address, or No services (the policy is inactive)
GatewaysNamed gateways, All gateways or No matching gateways. A revoked gateway appears as (revoked) with a warning
UpdatedLast change

Row actions: Edit policy, Simulate access (opens the simulator prefilled from the policy), Clone policy, View history and Delete policy.

Example: SSH to a server behind a gateway#

This grants a group of users SSH to one Linux server at 10.0.0.5, which a gateway on the same network can reach. It assumes the gateway is Online and the users have the agent installed.

  1. Open Network → Access and click Add Policy.
  2. Enter a Policy Name, for example Build server SSH, and keep Allow.
  3. Under What (Resources), click + New service.
  4. In New Service, set Application Type to SSH. Protocol becomes TCP, Ports becomes 22, and the health check becomes a TCP check on port 22.
  5. Enter 10.0.0.5 as the IP address or CIDR. Do not add :22; the port belongs in Ports.
  6. Under Gateways, pick the gateway that can reach 10.0.0.5.
  7. Click Create Service. The service, named SSH 10.0.0.5 unless you changed it, is now selected in the policy.
  8. Under Who (Subjects), select the users or group who need SSH.
  9. Either tick All tenant gateways or select the same gateway, then click Create Policy.

On a user’s device, connected to PulseHA, run:

ssh user@10.0.0.5

The route arrives with the next policy sync; pulsectl refresh forces it. If the connection times out, run Simulate access from the policy’s row for that user, device and service, and check the service’s health on Services.

How policies are evaluated#

The control plane rebuilds routes whenever a policy changes.

  1. Disabled policies and site-to-site policies are skipped. A policy whose gateway scope is Selected only applies on those gateways.
  2. Each policy’s subjects resolve to devices: the listed devices, every device of each listed user, and every device of each member of each listed group. All subjects adds every device in the tenant.
  3. For every device and service pair, the policy with the lowest priority number wins. When two policies share a priority, Deny beats Allow.
  4. Posture policies in enforce mode can then strip a non-compliant device’s routes. See Device posture.

The result is the set of allowed routes served to each agent and enforced on each gateway.

Revisions and history#

Every save carries the revision you loaded. If someone else saved first, the control plane rejects your save with Policies changed; reload before saving (HTTP 409). Reload, compare, then reapply your change. Other save errors read Policy storage unavailable; reload before retrying or Policy save could not be confirmed. Reload before retrying.

View history opens the version drawer. Each version shows its number, a change type (created, updated, enabled, disabled or cloned), a timestamp, and the stored snapshot when expanded. A policy with no saved versions reads No version history yet. History is a record; it does not restore a version.

Version history drawer for an access policy listing each revision

Each revision shows its number, change type and timestamp; expand one to read the stored snapshot.

Troubleshooting#

  • A user is denied although an Allow exists. Check for a Deny with a lower priority number or the same number. Run Simulate access from the row to see the matched policy and the trace.
  • Sources shows “No matching subjects” or Gateways shows “No matching gateways”. The scope is Selected but every selection was removed (for example a deleted group or revoked gateway). Edit the policy and either select subjects or tick the All box.
  • Services shows “No services” and the row is greyed as inactive. Add at least one service. Without one the policy does nothing.
  • A warning triangle appears in the Gateways column. The policy still references a revoked gateway. Edit, click Remove all in the revoked warning, and save.
  • The save button is disabled. A validation message is showing under Policy Name or Priority, or no service is selected.
  • “Some data failed to load: …” banner. Named datasets failed; tables may be incomplete. Reload before editing.