Feature toggles
Some Kumkuat features are switched on for every workspace; others are enabled per workspace, usually because they are new, carry cost, or need a conversation about data. Kumkuat sets the toggles for your workspace, under Workspace settings → Features, a panel only Kumkuat staff see; ask your Kumkuat contact to turn a feature on or off. Kumkuat staff see disabled features dimmed rather than hidden.
| Feature | Default | Notes |
|---|---|---|
| Audience Dashboard, Scorecards, Chat | On | Core |
| Why this matters to them on scorecard reactions | On | Grounded in current web sources; on for every workspace since 15 October 2026 |
| Narrative Testing Studio | On | Core |
| Content Writing | On | Core |
| Compare Narratives, Themes, Auto tags | On | Core |
| Marketplace | On | Install rights governed by permissions |
| Alerts and the notification bell | Off | Enable when you have chosen delivery channels |
| Audience Surveys | Off | Enable on request |
| Knowledge bases | Off | Enable when you want crawled sources |
| Comms Sources page | Off | Feeds are otherwise managed from Workspace Status |
| Projects | Off | Rolling out |
| Audience Library | Off | Rolling out |
| Persona asset links (social and file discovery per persona) | Off | Enable on request |
| Persona health drift checks | Off | Enable on request. Real-event tests and the Validation Center are in preview |
| Scheduled reports | Off | Enable when you want reports to self-deliver |
| Demo mode | Off | Sets a run budget and an expiry for the workspace |
How toggles behave
- A toggle protects both the page and the API routes behind it: a disabled feature refuses writes, not just navigation.
- Some pickers in the app only list features that are enabled, so a newly enabled feature can change what other pages offer.
- Toggling a feature does not delete anything. Turning Alerts off pauses schedules; turning it back on resumes them.