Skip to content

Network Access Control

Arrow automatically manages VPN access control to ensure that only authorized consultants can connect to Arrow devices and virtual machines. This security feature restricts device access to specific team members, enhancing security and compliance.

Access control is managed automatically by VTEM Labs based on your consultant assignments. When consultants are assigned to devices in Arrow, the system automatically synchronizes these permissions to the VPN.


When you assign consultants to a device in the Arrow Console, the following happens automatically:

  1. Consultant Assignment: You add consultants to a device request
  2. Automatic Sync: Arrow creates appropriate VPN groups and access policies
  3. VPN Access Granted: Assigned consultants can now connect to the device via VPN
  4. Removal Sync: When consultants are removed, their VPN access is revoked
flowchart LR
    A[Assign Consultant<br/>to Device] --> B[Arrow Creates<br/>VPN Groups]
    B --> C[Access Policy<br/>Created]
    C --> D[Consultant Can<br/>Connect via VPN]

    E[Remove Consultant<br/>from Device] --> F[VPN Access<br/>Revoked]

VPN access policies are configured as one-way for security:

DirectionAllowed
Consultants to DevicesYes - SSH, VNC, management access
Devices to ConsultantsNo - Blocked by policy

This security model ensures that even if a device is compromised, it cannot be used to attack consultant workstations or other infrastructure.


When viewing VPN details in the Arrow Console (VPN > NetBird > View Details):

The Policies tab shows access control policies in effect. These are managed by VTEM Labs and cannot be modified directly. Policies you may see include:

Policy TypePurpose
users-to-infrastructureAllows consultants to access Arrow devices
Device-specific policiesPer-device access for assigned consultants
VM access policiesAccess control for virtual machines

The Groups tab shows VPN peer groups:

GroupDescription
usersUser workstations authenticated via IDP
pvePhysical Arrow devices (Proxmox hosts)
pvmVirtual machines on physical Arrow hardware
vmVirtual machines on other infrastructure

To grant a consultant access to a device:

  1. Navigate to the device in the Arrow Console
  2. Edit the device request or device settings
  3. Add the consultant to the assignment list
  4. Save changes

VPN access is updated automatically within minutes.

To revoke a consultant’s access:

  1. Navigate to the device in the Arrow Console
  2. Edit the device request or device settings
  3. Remove the consultant from the assignment list
  4. Save changes

VPN access is revoked automatically.


Virtual machines provisioned through Arrow follow the same access control model:

When VMs are provisioned:

  1. Device Group: Created for the VM
  2. Consultant Group: Created for assigned users
  3. Access Policy: One-way policy allowing consultants to reach the VM

When VMs are completed, access control resources are automatically removed:

  • VPN peer registration removed
  • Device and consultant groups deleted
  • Access policies removed

For automatic access control to work correctly:

  • Consultants must have VPN user accounts
  • Email addresses must match between Arrow and the VPN system
  • Users authenticate via your organization’s identity provider

  1. Regular Review: Periodically review consultant assignments to ensure they’re current
  2. Prompt Removal: Remove consultant access when team members leave projects
  3. Document Assignments: Note why specific consultants are assigned in device requests