Settings
The Settings page in the admin dashboard has four tabs.
Logging & Telemetry
Section titled “Logging & Telemetry”Configure where logs and traces 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 |
Telemetry provider — choose one:
| Option | Description |
|---|---|
| None | No distributed tracing (default) |
| Application Insights | Azure Monitor integration |
| DataDog | DataDog APM traces |
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. The UI shows a warning and a Restart Now button when a restart is pending.
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.
License
Section titled “License”View your current license status: seat counts, trial days remaining (if applicable), and activation state. Enter a new license key here if you need to replace or upgrade your license.
System Info
Section titled “System Info”Displays the server version and 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 TrustedProxyCidrs, a warning appears here with suggested CIDR ranges.
Trusted proxy CIDRs — set the IP ranges of your reverse proxy / 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 correctly. Example:
10.0.0.0/8, 172.31.0.0/16