Platform Settings
Audience: Super Admin Page Type: Configuration
Overview
Admin → Platform Settings holds the settings that apply to the whole platform. Settings are stored in the database. Most apply after saving; startup settings such as the OTLP endpoint and authorization header take effect after a server restart. Only a Super Admin can open the page.
Secret values (such as the SMTP password) are write-only: after saving, the page shows only that a value is stored. Every change is recorded with who made it and when; for secrets only the fact that they changed is recorded.
E-mail tab
COS sends invitations, password links and assessment results by e-mail through an SMTP server.
| Field | Meaning |
|---|---|
| SMTP server | Host name of the mail server. Empty = no e-mail server. |
| Port | Usually 587 (STARTTLS) or 465 (direct TLS). |
| Direct TLS (SMTPS) | On for port 465, off for 587. |
| User name / Password | SMTP credentials. Leave the password empty to keep the stored one; Clear removes it. When you change the server or the user name, enter the password again (a stored password is never sent to a new server). |
| Sender e-mail | The From address. When empty, the user name is used. |
| Sender name | The name shown next to the sender address. |
After saving, click Send test e-mail: a test message goes to your own address with the saved settings. If it fails, the message shows the SMTP error code (for example EAUTH 535 for wrong credentials).
Without an e-mail server
Invitations and password links are still created; only the e-mail is skipped. The Users and Invitations screens show No e-mail server configured; Super Admins see a link to this page.
Transition from environment variables
When migrating an older configuration, if no email setting has been saved on this page, the server may read the SMTP_* environment variables; and the page marks those fields as read from the environment. The first save copies all e-mail settings into the database.
Other tabs (0.5.65)
| Tab | What it holds |
|---|---|
| Also New registration notice recipient (SaaS only): a new company registration sends an e-mail here; empty = none. | |
| Sign-in | Google sign-in on/off, the web client ID and additional client IDs. Off or no client ID = no Google button on the login screen. |
| AI | Chat history retention (one value for every company, default 90 days; expired chats are deleted permanently by the nightly job), the lifetime of an AI action waiting for approval, and the web search key and engine ID (either empty = web search off). |
| Observability | Grafana OTLP endpoint and authorization header (read at startup: a change takes effect after the server restarts), Faro collector URL, Microsoft Clarity project ID. Empty = off. |
| Retention | Days to keep AI tool logs, AI usage logs (0 = keep), read notifications and integration run logs. |
| Product behavior | Personal dashboard refresh interval, rows on home page lists, longest invitation validity, whether pushed measurements need an active integration binding. |
| Scheduler | The time of each nightly job (server time; UTC on SaaS). Saving reschedules at once. |
Changing the OTLP endpoint also requires entering the authorization header again (or clearing it). The login screen may take up to 5 minutes to reflect a Google, Clarity or Faro change.