Administrators and access policies

Separate browser administration from proxy authentication, and grant only the control and file-access permissions each person needs.

Manage administrator roles

Sign in as the owner and open Administrators to add or edit an administrator. The email is the login name; choose the role and enabled state before saving.

• Owner: Manages administrators and privileged console/file workspaces, subject to Mac-side authorization.
• Operator: Manages proxy accounts and permitted configuration/service actions.
• Viewer: Reads operational data without write controls.

The owner cannot be disabled on this page. A proxy user is a separate account and cannot sign in as an administrator merely by having proxy credentials. A disabled button can also indicate that Allow control actions is off or a capability is unavailable.

Console, files and saved configuration

Use the relevant sidebar entry or host action to open Console or SFTP. Owner access and Mac-side control permission are required. Local Console and local files use the Mac account’s permissions and configured approval method; they are not restricted to a harmless proxy-settings view. Complete Mac approval or app OTP when requested. Keep private-key authentication configuration in the Mac App.

Browser session tabs can remain open when changing pages. Explicitly disconnect or close a session when finished. Review file-operation confirmations; deletions cannot be undone and existing files are not silently replaced by uploads. A successful configuration save is not proof that every running connection has adopted it.

Recover access safely

• Forgotten owner password: on the Mac, stop the API, choose Reset administrator password…, authorize locally, enter and confirm the new password, then restart the API and sign in again. Users, rules and usage data are preserved.
• Changed API token: update authorized scripts that use it. The token also authorizes initial owner setup; resetting it is not a browser sign-out command.
• End browser access with Sign out. Stopping the API closes management workspaces and sessions, without stopping unrelated SSH/proxy connections.

Access policies summarize proxy identity rules; configure accounts under Proxy users and destinations under Routing rules. Audit records aid investigation but do not constitute a complete security audit. See proxy-user policies.