Settings
Ce contenu n’est pas encore disponible dans votre langue.
Settings (/admin/settings) is where an operator checks what this instance is actually running with. Most of it is a read-only mirror of configuration — the values come from appsettings.json and environment variables, and the only way to change them is to change the configuration and restart. See Configuration for the keys behind every row.
Certificates and Guardrails used to be tabs here; both now have their own pages — see Certificates and Guardrails. Of what’s left, one tab is more than a mirror: Data performs deletions.
| Tab | Direct route | Editable |
|---|---|---|
| Overview | /admin/settings |
No |
| Authentication | — | No |
| Limits | /admin/limits |
Yes — see Policies |
| Pia assistant | — | Yes — see Pia assistant |
| Data | — | Destructive |
Overview
Section titled “Overview”A status strip across the top, then the values behind it.
| Shown | Comes from |
|---|---|
| Encryption ✓ / not set | Encryption:MasterKey. An all-zero placeholder key reads as not set |
| n admins | The number of addresses in Admin:Emails |
| Database: provider | Database:Provider |
The Database section repeats the provider and the connection string with its credentials masked. Encryption reports whether the master key is present, never its value. Admin lists the bootstrap addresses verbatim.
Authentication
Section titled “Authentication”Also read-only: whether the JWT signing key is configured, the issuer and audience, and the two token lifetimes (access token in minutes, refresh token in days). Under OAuth Providers, each of Google, Microsoft, and Entra ID reads Configured or Not configured based on whether a client id is present — the pill in the strip counts them, OAuth: 2 of 3.
A provider showing Not configured is invisible on the sign-in page. For the Entra setup, see Entra OAuth.
Limits
Section titled “Limits”Rate limits, quotas, and identity policy. This tab embeds the same editor documented on its own page: see Policies for every field, and for which settings need a restart.
Pia assistant
Section titled “Pia assistant”Controls for the Pia assistant, the P bubble in the corner of every admin page.
| Field | Default | What it does |
|---|---|---|
| Assistant database access | Off | Lets Pia read this server’s configuration and knowledge-base passages (which can contain personal data); a person’s account data only after you approve each call. What it reads is sent to the configured AI provider; secrets are never readable. See Database access |
| Messages per minute | 6 | How many messages one admin can send per minute (1–60) |
| Messages per hour | 60 | How many per hour (1–1000, at least the per-minute value) |
The switch saves as soon as you flip it; the two limits save with Save limits. Changing any of them needs Manage access to Settings. With View access you see the values but cannot change them. Every change is audited as AdminAssistant.SettingsChanged.
Workspace-wide deletions, one button per storage area. There is no undo.
| Area | Deletes |
|---|---|
| Users | Every account, and by cascade everything owned by one — templates, providers, sessions, memories, todos, kanban columns, devices, tokens, sync state |
| Templates / Providers / Sessions / Memories | That collection, across all users |
| Todos & Kanban | Todo items and kanban columns |
| Sync State | Sync cursors and the sync event log |
| Token Usage | The token usage log |
Each button asks twice — a confirmation, then a final warning naming the area — and the result bar reports how many rows went. Wipes that change what a client would pull also invalidate the affected users’ sync versions, so clients re-pull instead of getting a stale 304.
Wipes are written to the server log with the acting administrator’s address. They do not appear in the audit log — the rows the audit log would reference may no longer exist.
The Storage Areas list is fixed in the page rather than queried, which is why it is the one table in the admin UI with no Refresh button.