Features and audit
This page covers two platform-level admin areas: system feature flags that turn capabilities on and off, and the audit log that records who changed what.
System features
Features are system-wide flags that enable or disable platform capabilities. Each flag shows its key, a description, and its current on/off state.
- Toggle a flag to enable or disable the capability it controls.
- Unknown flags are shown with their raw key and description, so newly added flags appear automatically.
The current feature flags:
| Flag | Controls |
|---|---|
signups_enabled | Whether people can self-sign-up or the platform is invite-only. |
ai | The in-context AI assists and AI survey generation. |
executive | The AI Executive view. |
benchmarking | Competitor benchmarking. |
keith | The Keith assistant (text + voice). |
feedback | In-app product feedback. |
global_search | Universal search across responses. |
The AI/insights flags are off by default — turn them on to release those capabilities to your workspace. A system admin can always preview a gated feature regardless of the flag.
Feature flags are a platform-administration capability and change behaviour across the client account, so change them deliberately.
Audit
The Audit page has three views:
- Admin changes — append-only administrative changes recorded with the operation that produced them.
- Response amendments — account-wide answer and custom-data changes, with editor, date, and target filters.
- Coding activity — the verbatim-coding audit trail.
Admin-change entries record:
| Column | Meaning |
|---|---|
| When | The timestamp of the action. |
| Actor | The member (by email) who performed it. |
| Action | Create, update, or delete. |
| Target | The resource that changed (for example a survey or webhook). |
| Details | Metadata about the change. |
Viewing the Audit page requires account.manage. Use it to answer compliance and forensic questions —
who changed a setting or response, when, and what it affected.
The Admin changes bounded CSV remains an immediate download. In Response amendments, members who
also hold responses.export can click Queue CSV to export the full filtered trail durably. The status
drawer can be closed while the build continues; reopen the run from the Exports page and download its
retained CSV part(s) when ready. Without responses.export, the amendment trail remains visible but the
bulk export control is hidden.
Next steps
- Integrations & API keys — actions here are audited too.
- Compliance — the deletion audit trail for GDPR actions.