Configuration
The Configuration page in the admin dashboard has four tabs: License, Reverse Proxy, Logging, and Terms of Service. When a change requires a server restart, the page shows a banner with a Restart Now button.
License
Section titled “License”View your current license status: seat counts, trial days remaining (if applicable), and activation state. If the deployment isn’t licensed yet, this tab leads with Buy Broch — start the 15-day free trial or purchase seats and check out through Stripe, the same flow as first-run setup. Once licensed, manage or cancel your subscription here. Already hold a key (renewal or marketplace)? Paste it here to replace or upgrade your license.
Reverse Proxy
Section titled “Reverse Proxy”Set the IP ranges of your reverse proxy or load balancer so Broch can correctly extract the real client IP from X-Forwarded-For headers. This is required for Share Policy network rules to work — without it, every request appears to come from the proxy and network rules will not behave as expected.
10.0.0.0/8, 172.31.0.0/16This tab also reports the ingress IP as seen by the server, along with its network classification (loopback, private, CGNAT, or unknown). If the ingress IP does not match your configured CIDRs, a warning appears with suggested ranges.
Logging
Section titled “Logging”Configure where logs are sent.
Logging provider — choose one:
| Option | Description |
|---|---|
| None | Stdout only (default) |
| DataDog | Ship structured logs to DataDog |
| Seq | Ship structured logs to a Seq server |
| OpenTelemetry | Ship structured logs to any OTLP collector |
Log level — Verbose, Debug, Information, Warning, Error, or Fatal.
Console logging — toggle to enable or disable logging to stdout alongside the configured provider.
Provider-specific fields (API keys, connection strings) appear when the relevant provider is selected. Secret values are masked in the UI and are not overwritten if left unchanged.
Changes to logging settings require a server restart.
Terms of Service
Section titled “Terms of Service”Enable a required Terms of Service acceptance gate for all users.
- Required — toggle to enable. When enabled, users must accept before using any feature.
- Content — Markdown, up to 50,000 characters.
- Version — read-only, auto-generated timestamp (
yyyy-MM-dd-HHmmss). Updating the content automatically increments the version and requires all users to re-accept.
Terms take effect immediately — no restart required.