Every settings page of a project, where each is documented, who may change it, and what the audit log records.
Settings apply per project and are grouped on the left of Settings into Project, Features and Record. The pages that configure a topic with a life of its own are documented with that topic; the pages that are only settings are documented here.
The pages
| Group | Page | What it holds | Documented on |
|---|---|---|---|
| Project | General | The project's name, slug, id, plan and Frontend API URL; data retention; transfer and deletion | General and Retention |
| Project | Access | Anonymous access, allowed browser origins, auth rules | Anonymous sessions, Allowed origins, Auth providers |
| Project | API keys | Keys for your server, with their expiry and last use | API keys |
| Project | Telemetry | The project's endpoints, the trace link template, the renderer URL, the SDK versions seen | Telemetry settings |
| Project | Model prices | Price overrides for models the catalog lacks or prices you negotiated, and the unpriced models of the month | Model prices |
| Features | Thread titles | The model that names conversations, its language and length, and what it wrote | Thread titles |
| Features | Intelligence | The analysis of conversations into topics, tasks and signals | Intelligence |
| Features | Evaluators | Model judges that score a sample of new conversations | Evaluators |
| Features | Alerts | Rules that watch one metric an hour and deliver a signed webhook | Alerts |
| Record | Audit log | Every change, who made it and the fields before and after | Audit log |
Billing and Usage sit under Project in the sidebar rather than under Settings; they are on Billing. LLM providers, Assistants and Harnesses are under Build and have their own pages in Cloud features.
Who may change what
| Owners and admins only | Every member |
|---|---|
| Allowed origins, the renderer URL, data retention and its cancellation, every alert rule action, reading the audit log, Upgrade and Open Stripe portal | Everything else on these pages. On Billing, the pricing dialog from a plan badge, including its Free choice |
A change on the demo project is refused with The demo is read only.
What the audit log records
Every write made through the dashboard writes one audit entry: the actor, the action, the resource and the fields that changed, before and after. Credentials, secrets and key material are redacted by name before the entry is written, so an API key, a provider credential or a webhook secret never appears in the log. A user erasure made through the API with a key is recorded there too, with the key as the actor. Audit log lists every resource and action.