User Accounts & Roles¶
Charon keeps a short, simple list of who is allowed to sign in. There is no public "create an account" page — every account is set up on purpose by someone who already has access. That means a stranger who finds your Charon login screen has nothing to do there but look at it.
The Two Kinds of Account¶
Administrator
The full-control account. An admin can change anything: security settings (the firewall, CrowdSec, access lists, security headers), certificates and the credentials used to get them, DNS provider logins, SSH connection details for Sources, tunnels and agents, app settings, plugins, and the user list itself. The very first account you create when you set Charon up is an administrator.
Standard user
A day-to-day account for adding and managing proxy hosts and redirection hosts. A standard user can still open most settings pages and see how things are configured — the certificates list, the access lists, the DNS providers, and so on — but the buttons that change security-sensitive configuration are for admins only. If a standard user tries one anyway, Charon simply refuses it.
Here is what a standard user can and cannot do:
- Can: add, edit and delete proxy hosts and redirection hosts.
- Can: run Test Connection on a proxy host to check its forward target.
- Cannot: choose a DNS provider or turn on the DNS challenge for a host. Those fields are greyed out with a short note. A standard user can still save a host as long as those two settings stay as they are.
- Cannot: edit a proxy host's advanced Caddy configuration. The proxy host form shows a short note where the editor would be, and saving the host keeps the existing configuration.
- Cannot: add, change, delete, or run a manual check on uptime monitors. They can still see the monitor list, each monitor's status and its history.
- Cannot see sensitive details: notification web addresses (webhook URLs) and their settings, a proxy host's advanced configuration, and DNS credential details such as the last error message and zone filter. Charon hides these on the page and leaves them out of the information it sends to a standard user's browser. Charon still shows whether a notification address is set.
- Cannot see these hidden security details: the admin allow-list, the rate limit bypass list, the CrowdSec API address, the mail server details (host, port, username, sender address and encryption), and the text inside each WAF rule set. Charon shows each of these as hidden instead of its value. Standard users still see the names of the WAF rule sets.
Some limits apply to every account, administrators included:
- Charon will not list the containers on a remote server that has been switched off. Turn the server back on first.
- Charon will not send a proxy target to its own internal ports, to link-local addresses, or to cloud instance service addresses. Point the target at your app's address instead. The full list is in Forward Targets.
- Connection tests are limited to 10 per minute for each account. Every account gets the same failure message for an address that cannot be reached. See Diagnosing a Failed Connection Test.
A few areas are admin-only even to look at, because they show sensitive detail: the CrowdSec control panel, the audit log, the remote agent management page, and encryption management. Standard users don't see those in the menu.
Adding Someone New¶
New accounts are always created by an existing administrator, in Settings → Users. There are two ways:
- Invite by email — Charon emails the person a one-time link. They click it, pick their own password, and they're in.
- Create directly — the admin fills in the name, email, and a starting password and hands it over.
Either way, the admin chooses whether the new person is an administrator or a standard user.
Passwords and Sign-In¶
- Same message every time. If a sign-in doesn't work, the login page shows the same "invalid credentials" message, whatever the reason. The sign-in screen doesn't show an account's lock status.
- Locks. After 5 wrong passwords an account is locked for 15 minutes. Once the lock has expired, the count of wrong tries starts again from zero.
- Changing your password signs out your other devices. Use Change Password and Charon ends your other sessions, while you stay signed in on the device you used.
- Resetting someone else's password. An administrator can set a new password for another person without knowing the old one. That person is signed out everywhere and signs in with the new password. Changing your own password through the Users API needs your current password, and signs you out so you sign in again.
The Very First Account¶
The first time you open a brand-new Charon, it shows a first-run page and asks for a setup code before it lets you create the starting administrator account. That's the only time an account is created without an existing admin doing it.
- Finding the code: Charon makes the code when it starts and writes it to
its log. Run
docker logs charon | grep "Setup code"to see it. Full steps are in Create Your First Account. - One code, one use: The code stops working as soon as the first account exists. A restart while no accounts exist issues a new code, and only the newest code works.
- Wrong codes: After 5 wrong tries, Charon makes you wait about a minute before each new try.
- Existing installs: If you already have accounts, nothing changes and you never see this page.
Once that account exists, the first-run page is gone for good and all further accounts go through Settings → Users.
Related¶
- How Charon Keeps You Safe — the bigger security picture
- Access Control Lists — decide who can reach your proxied sites
- Back to Features