Set up Enterprise administration
Enable the management service on your Mac, initialize its owner locally, then open the web console from an authorized computer.
Enterprise Settings requires an Enterprise license.
Enable the service on the Mac

- Open General → Enterprise Settings in Secure Pipes. Choose an unused API port; the default is 10790.
- Enable Allow control actions only if browser users need to change configuration or operate services. Role permissions still apply. Stop the API before changing its port or permissions.
- Start the Local API and use its displayed loopback management URL on this Mac. Without a configured certificate, the default is
http://127.0.0.1:10790/admin. - On first use, enter a display name, email, password and matching password confirmation. Use at least 12 characters for the password. Copy the Local API token from Enterprise Settings into the initialization form; do not put it in a URL or share it.
- Submit to create the owner account. Subsequent logins use the administrator email and password, not the API token.
Permit another computer
Initialize the owner locally first. Stop the API, enable Allow LAN access to the web console, then restart it. Open the displayed current LAN address from the other computer. 127.0.0.1 on that computer refers to itself, not this Mac.
Use trusted HTTPS before sending credentials over an untrusted link. LAN access does not configure DNS, routers or firewalls automatically. Do not publish an unencrypted management port. If access fails, check the displayed address, API state, certificate trust and firewall before changing permissions.
Find your workspace
Use Overview for service status, SSH connections and recorded usage. The sidebar opens saved SSH hosts, forwarding/SOCKS profiles, routing rules, proxy servers, DNS and logs. Runtime views show connections and traffic. Controls depend on your role, the Mac’s permissions and reported capabilities; SSH trust or authentication may still require attention on the Mac.
Continue with administrators and access, proxy users and risks and safeguards.
Based on Secure Pipes 2.0.15 · Updated October 25, 2026