- Preventing accidental exposure of development services
- Enforcing network security policies
- Restricting access to internal services
Port access levels
When port authentication is available, each shared port can use one of these access levels:
If you narrow a port from
everyone to a more restrictive level, existing browser sessions must authenticate again before the port loads.
Settings
Disable port sharing
Check Disable port sharing to block user-initiated shared ports in the dashboard and CLI. Use this when your organization does not allow externally reachable development services at all.Maximum port admission level
Use Maximum port admission level to cap the most permissive access level members can choose when opening or editing a port.
When the cap is lower than a user’s requested access level, the dashboard disables the blocked options and the CLI/API rejects wider access levels.
How the controls interact
These controls are orthogonal:- Disable port sharing answers “can users open shared ports at all?”
- Maximum port admission level answers “if they can open a port, how broadly may they share it?”
Exemptions
VS Code Browser and agents are exempt from this policy and continue to work when port sharing is disabled. Only user-initiated port sharing is affected.Effect on users
- Dashboard users cannot choose admission levels above the configured cap
- CLI users cannot open ports when port sharing is disabled, and
ona environment port open --admission ...fails if the requested level exceeds the cap - Users see a notification or error explaining the restriction
- VS Code Browser and agents remain functional