JPPS

Users and Roles

Updated Oct 15, 2026

You can give other people their own sign-in to the admin panel instead of sharing one password. Each person gets one of three roles.

The three roles

RoleWhat they can do
AdminEverything
OperatorLook at every page and change how the proxy works: sites, port rules, access lists, certificates
ViewerLook at everything except Users and API tokens. Can't change anything

Some settings are admin-only so an operator can't give themselves more power: Users, API tokens, DNS credentials, certificate (ACME) settings, firewall settings, log forwarding, hosted address pools and the default site. Operators and viewers can still see most of those.

Pages a person can't use are simply hidden, and a viewer sees the rest as read-only.

The owner

The account you created in the first-run setup is the owner. The owner is always an admin, always listed first, and can't be edited, disabled or deleted from the Users tab. That means a slip in the Users tab can never lock everyone out.

Adding a person

  1. Open the Users tab and choose Add user.
  2. Pick a username (letters, numbers, and . _ @ -; capitals don't matter) and a password of at least 8 characters.
  3. Choose a role.

Later you can change someone's role, disable or re-enable them, reset their password or delete them.

Changes happen instantly

Take a person's access away and their very next click is blocked, even though their browser is still signed in.

Passwords

Scripts and automation

Tools that call the proxy use API tokens, and a token has a role too. Give a monitoring script a viewer token and a deployment script an operator token, so a leaked token can only do what that job needs.

Who did what

The logs record which user (and role) made each change, so you can always answer "who changed that?"