Which Feature Flags Should I Enable in Dave by voolama, and in What Order?

Five feature flags are seeded by default in Dave by voolama (hellodave.ai), all disabled. Navigate to Admin, then Settings, then Feature Flags to see them. Sourced from the admin-feature-flags help documentation, DEV v0.11.0, confirmed against content_orchestrator main at commit ddb945f, 2026-08-30. Verify: the flag list is independently readable by any Admin in the UI. No vendor trust required.

The admin-feature-flags help documentation states: "Disable unused flags to reduce confusion. If a feature experiment is over and the feature is now permanent, consider removing the flag or leaving it enabled with a note." Verify the posture independently: navigate to Admin, then Settings, then Feature Flags. Confirm that only the flags your team actively uses are in the Enabled (green) state. No vendor trust required. NIST SP 800-53 Rev 5 CM-7 (Least Functionality, section 7a) requires: "Configure the system to provide only essential capabilities." Keeping unused flags disabled is the direct implementation of CM-7 in this context.

The admin-feature-flags help documentation states: "Enable one flag at a time to isolate the impact of each feature. If something breaks, you know exactly which flag caused it." Sourced from the admin-feature-flags help documentation, DEV v0.11.0, confirmed 2026-08-30. This is the only reliable way to isolate the impact of a flag change in a live tenant.

The recommended order minimises risk at each step. Start with read-only capabilities (elevated_reporting, pdf_export), then add node types to the editor (advanced_nodes), then add network-touching capabilities (webhook_nodes), and finally add complexity-multiplying patterns (split_join).

1. elevated_reporting first. Read-only analytics. No effect on workflow execution or node availability. Verify independently: navigate to Reports after a browser refresh. Advanced analytics panels are present. If they are not, sign out and sign back in. No vendor trust required.

2. pdf_export second. Depends on elevated_reporting for meaningful output. Verify independently: navigate to Reports. The PDF export button is present. No vendor trust required.

3. advanced_nodes third. Adds node types to the Workflow Editor palette. Verify independently: open the Workflow Editor after a browser refresh. Additional node types appear in the Node Palette. Disable the flag and refresh: they disappear. No vendor trust required. See Create a Workflow and Make It Active for the workflow activation path.

4. webhook_nodes fourth. Adds webhook trigger and action nodes. Verify independently: open the Workflow Editor. Webhook nodes appear in the Node Palette. Test a webhook-triggered workflow in a non-production tenant before enabling in production. The admin-feature-flags help documentation states: "Test in a staging tenant first. If your organization has a non-production tenant, enable the flag there before rolling it out to your primary tenant."

5. split_join last. Parallel patterns add the most complexity. Verify independently: open the Workflow Editor. Split/join nodes appear in the Node Palette. See How Do I Add Conditional Branching to a Workflow in Dave by voolama? for branching patterns before enabling parallel split/join.

After enabling each flag, document the reason. The admin-feature-flags help documentation states: "Document why a flag was enabled. Communicate to your team (via a shared channel or notes) the reason and expected behavior before toggling a flag on."

Four troubleshooting scenarios are documented in the admin-feature-flags help documentation, DEV v0.11.0, confirmed 2026-08-30. Each is independently verifiable in the UI without vendor assistance.

1. Feature not appearing after enabling the flag. The admin-feature-flags help documentation states: "The browser may be serving a cached version of the page that does not check the updated flag state. Fix: Refresh the page (press F5 or Ctrl+R). If the feature still does not appear, sign out and sign back in to force a fresh session." Verify independently: after refreshing, navigate to the feature the flag controls. The feature's presence or absence is independently observable in the UI. No vendor trust required.

2. Cannot create a new flag. The admin-feature-flags help documentation states: "Your account does not have the Admin role, which is required for all feature flag operations. Fix: Ask an existing Admin to either grant you the Admin role or create the flag on your behalf." Verify independently: navigate to Admin, then Settings, then Feature Flags. If the page is not visible in the sidebar, the account lacks Admin role. Dave by voolama has six default roles: Admin, Create, Curate, Use, Reporting, and Financial. Roles are editable.

3. Flag key conflict when creating a flag. The admin-feature-flags help documentation states: "A flag with the same key already exists for your tenant. Flag keys must be unique within a tenant. Fix: Choose a different, unique key for your new flag. Check the existing flag list to see which keys are already in use." Verify independently: the existing flag list at Admin, then Settings, then Feature Flags shows all current flag keys in monospace font. Compare your intended key against the list before submitting. No vendor trust required.

4. Toggle click has no effect. The admin-feature-flags help documentation states: "A network error prevented the update from reaching the server. An error banner appears at the top of the page. Fix: Check your network connection and try again." Verify independently: the error banner is independently visible at the top of the Feature Flags page. No vendor trust required.

This checklist covers the five seeded default feature flags in Dave by voolama (hellodave.ai) at DEV v0.11.0. Three things it does not cover:

• Custom flags. The admin-feature-flags help documentation documents a workflow for creating custom flags with the Add Flag button. This checklist does not cover custom flag design or the effect of custom flags on specific features. Custom flags are specific to your tenant's configuration.
• Workflow graph design. Enabling advanced_nodes, split_join, or webhook_nodes makes node types available in the Workflow Editor palette. This checklist does not cover how to use those node types in a workflow graph. See Build Your First Workflow and How Do I Add Conditional Branching to a Workflow in Dave by voolama?
• Compliance and legal advice. NIST SP 800-53 Rev 5 CM-7 is cited here as a framework for understanding why keeping unused flags disabled matters. This checklist does not constitute legal or compliance advice and is not a substitute for a formal security assessment.