Server settings

Rate limits

Per-scope request limits — login, password resets, messages, uploads, writes, search.

Each scope is a pair — how many requests, per what interval — enforced server-side and applied without restarts. Seven pairs are editable on the tab:

Three more scopes are enforced exactly the same way but have no field on the tab — they live in the settings registry only, so changing them off the defaults means writing to the settings store directly:

Session refresh deserves a word: it is keyed by IP and every browser tab spends one on reload once its access token nears expiry, so the whole office behind a single NAT address draws on the same budget. The default (60 per minute) is sized for that. Setting it too low signs people out mid-session rather than blocking an attack.

Limits apply per user (per IP for unauthenticated scopes like login). When a limit trips, the API returns 429 with a retry hint; the client surfaces it to the user. On a community endpoint a 429 also feeds the auto-timeout counter.