Connecting to a server

Sign in

Firehall opens to sign-in on the configured default server, or your saved server. Check the server name and address beside Change before requesting a code.

1. Enter your verified email or phone number.
2. Choose email or SMS delivery. SMS is offered when the server has it configured.
3. Enter the six-digit code, or confirm the email link in the requesting browser.
4. Your only approved department opens directly. If you have several departments, Firehall resumes your last authorized selection or asks you to choose one.

Codes and links expire ten minutes after the request and can only be used once. Keep the requesting app or browser open. When opening email on another device, enter the code in the app where you requested it.

Use Join a fire department to apply with a Department code. Confirm the department name and server before requesting membership. Pending requests cannot open department content. Use Your departments in your account controls to manage memberships; Join another department expands the join form there.

Use another server

At sign-in, choose Change → Use another server. Inside a department, open your account controls, then Preferences → Server settings. Enter your department's root HTTPS address and choose Check server. A profile name is optional.

Use an address such as https://firehall.example.org, without a path, query, fragment, or embedded credentials. The client reads /.well-known/firehall to check compatibility. If discovery fails, check the address or retry. Editing and checking an address does not change your current signed-in session. Choose Switch and sign in to commit the change and clear the previous private context.

Sessions and contacts

Browser sessions use an HttpOnly cookie; native sessions use the device's secure credential storage. Signing out revokes the current session. Open Your profile → Verify email or phone to verify another contact before using it for login. Changing a verified contact signs out your other sessions.

Switching departments or servers clears the previous view's drafts and results.

Server configuration

Operators must allow their browser origin in FIREHALL_CORS_ALLOWED_ORIGINS. The browser session broker also requires the API origin in its comma-separated FIREHALL_BROKER_ORIGINS setting. Native clients connect directly to their selected HTTPS server. API credentials are never forwarded to a different origin.