How Do I Enable Feature Flags Safely in Dave by voolama Without Breaking My Team's Workflows?

Summary

The steps

1. 1

   Understand what each of the five default flags controls before you touch any of them

   Dave by voolama (hellodave.ai) ships five default feature flags. All are disabled at tenant creation. Sourced from the admin-feature-flags help documentation, DEV v0.11.0, confirmed against content_orchestrator main at commit ddb945f, 2026-08-30. Martin Fowler's feature toggle reference at martinfowler.com classifies these as release toggles: binary, tenant-wide, and intended to control feature exposure. Verify each flag's effect by enabling it and navigating to the location listed in the table below. No vendor trust required.

   Flag key	What it enables	Where the change appears	Safe to enable without staging test?
   advanced_nodes	Advanced node types in the workflow editor	Workflow Editor node palette	No. New node types may affect existing workflows. Test in a staging tenant first if available.
   split_join	Parallel split/join workflow patterns	Workflow Editor node palette	No. Parallel patterns change execution semantics. Test before enabling in production.
   webhook_nodes	Webhook trigger and action nodes	Workflow Editor node palette	No. Webhook nodes make outbound HTTP calls. Verify destination URLs before enabling.
   elevated_reporting	Advanced analytics and dashboards in the Reports section	Reports page	Yes. Read-only analytics. No workflow execution impact.
   pdf_export	PDF export for reports	Reports page export button	Yes. Read-only export. No workflow execution impact. Lowest risk: enable this first.

   The three workflow-editor flags (advanced_nodes, split_join, webhook_nodes) affect what node types appear in the editor palette. Disabling a flag after a workflow has been built using its node types does not remove those nodes from existing workflow versions. The nodes remain in the saved graphJson. The flag controls palette visibility, not saved data.

   Do this

   • Navigate to Admin, then Settings, then Feature Flags.
   • Read the full flag list before toggling anything. Note which flags are currently enabled.
   • For each flag you plan to enable, identify where the change will appear (workflow editor palette or Reports page) and who on your team will notice it.
   • Decide the order: start with pdf_export, then elevated_reporting, then the workflow-editor flags after team briefing.

   Example

   Your team needs PDF export for a compliance report. Navigate to Admin, then Settings, then Feature Flags. Find the pdf_export row showing Disabled (muted). Click the toggle. It switches to Enabled (green) immediately. Navigate to the Reports page. A PDF export button appears. Click it. A PDF is generated. No other page or workflow is affected. This is the lowest-risk flag to enable first because it is read-only and scoped entirely to the Reports page.

   Best practice

   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." Start with pdf_export (narrowest scope, read-only), then elevated_reporting (read-only analytics), then the workflow-editor flags after briefing the Curate-role team. This ordering puts the lowest-risk changes first and preserves the ability to attribute any problem to a specific flag.

2. 2

   Enable a flag and verify it took effect

   Enabling a flag in Dave by voolama (hellodave.ai) is a single click. The change is immediate and server-persisted. Sourced from the admin-feature-flags help documentation, DEV v0.11.0, confirmed 2026-08-30.

   1. Navigate to Admin, then Settings, then Feature Flags.
   2. Locate the flag row. The Flag Key is displayed in monospace font.
   3. Click the toggle button on the right side of the row. The toggle switches from Disabled (muted) to Enabled (green) immediately.
   4. Navigate to the page where the feature appears (Reports page for elevated_reporting and pdf_export; Workflow Editor for the three node flags).
   5. If the feature does not appear: press F5 or Ctrl+R to refresh the page. If it still does not appear after refresh, sign out and sign back in to force a fresh session.

   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." The toggle change itself is always persisted immediately. A missing feature after toggling is a browser cache issue, not a toggle failure. Verify: return to the Feature Flags page and confirm the toggle shows Enabled (green). If it does, the server state is correct and a refresh will surface the feature.

   Do this

   • Click the toggle for the chosen flag. Confirm it shows Enabled (green).
   • Navigate to the feature's location (Reports page or Workflow Editor).
   • If the feature is not visible: press F5 or Ctrl+R. Check again.
   • If still not visible after refresh: sign out, sign back in, navigate to the feature location again.
   • Confirm the feature is visible and functional before enabling the next flag.

   Example

   You enable the elevated_reporting flag. You navigate to the Reports page. The advanced analytics sections are not visible. You press F5. The page reloads. The advanced analytics sections appear. The flag was always enabled on the server; the browser was serving a cached version of the Reports page that predated the flag change.

   Best practice

   Verify each flag in the same browser session where you toggled it. If you toggle a flag and then ask a colleague to verify it in their browser, their session may also be cached. Each user should refresh their own browser after a flag is enabled.

3. 3

   Communicate the change to your team before enabling workflow-editor flags

   The three workflow-editor flags (advanced_nodes, split_join, webhook_nodes) change what appears in the Workflow Editor palette for all users with the Curate role immediately on toggle. Sourced from the admin-feature-flags help documentation, DEV v0.11.0, confirmed 2026-08-30. Dave by voolama has six default roles: Admin, Create, Curate, Use, Reporting, and Financial. Roles are editable. Only Admin and Curate roles can open the Workflow Editor.

   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." For workflow-editor flags, the minimum communication is:

   • Which flag key is being enabled and when.
   • What new node types will appear in the editor palette.
   • Whether any existing workflows need to be tested after the flag is enabled.
   • Who to contact if a workflow behaves unexpectedly after the change.

   Do this

   • Before enabling advanced_nodes, split_join, or webhook_nodes: notify all Curate-role users via your team's shared channel.
   • State the flag key, the expected change (new node types in the palette), and the time of the change.
   • After enabling: ask one Curate-role user to open the Workflow Editor and confirm the new node types appear in the palette.
   • Run at least one existing workflow instance to confirm existing workflows are unaffected. See Create a Workflow and Make It Active and Build Your First Workflow.

   Example

   You plan to enable webhook_nodes on a Tuesday morning. On Monday, you post in your team channel: 'Tomorrow at 10am I will enable the webhook_nodes flag in Dave. This adds webhook trigger and action nodes to the Workflow Editor palette. Existing workflows are not affected. If you see unexpected behavior in the editor after 10am, let me know.' On Tuesday at 10am you enable the flag. You ask a Curate-role colleague to open the editor and confirm the webhook nodes appear. They confirm. You run an existing workflow instance and confirm it completes normally.

   Best practice

   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." Flags are tenant-scoped: enabling a flag in a staging tenant has no effect on your production tenant. This is independently verifiable: enable a flag in tenant A, log into tenant B, navigate to the Feature Flags page. The flag is not enabled in tenant B. No vendor trust required.

4. 4

   Troubleshoot the three most common feature flag problems

   Three problems are documented in the admin-feature-flags help documentation for Dave by voolama (hellodave.ai), each with a specific fix. Sourced from the admin-feature-flags help documentation, DEV v0.11.0, confirmed 2026-08-30.

   Problem	Root cause	Fix	Independent verification
   Feature does not appear after enabling the flag	Browser cache serving a pre-flag version of the page	Press F5 or Ctrl+R to refresh. If still missing, sign out and sign back in.	Return to the Feature Flags page. Confirm the toggle shows Enabled (green). If it does, the server state is correct and a refresh will surface the feature.
   Cannot create a new flag (Add Flag button missing or access denied)	Account does not have the Admin role	Ask an existing Admin to either grant the Admin role or create the flag on your behalf.	Log in with an Admin-role account. Navigate to Feature Flags. The Add Flag button appears in the top-right corner.
   Flag key conflict when creating a new flag	A flag with the same key already exists in the tenant	Choose a different, unique key. Check the existing flag list to see which keys are already in use.	After choosing a unique key, click Add. The flag is created in the Disabled state. The new row appears in the flag list.

   A fourth issue: the toggle click has no effect and an error banner appears at the top of the page. The admin-feature-flags help documentation states: "A network error prevented the update from reaching the server." Fix: check your network connection and try again. The flag state on the server is unchanged when this error occurs: the toggle in the UI reverts to its previous state.

   Do this

   • If a feature is missing after toggling: refresh first (F5 or Ctrl+R), then sign out and back in if still missing.
   • If you cannot access the Feature Flags page: confirm your role is Admin at Admin, then Settings, then Users and Roles.
   • If a flag key conflict appears: navigate back to the flag list, read all existing keys, choose a key that does not appear in the list.
   • If the toggle produces an error banner: check your network connection, wait 30 seconds, try again.

   Example

   You try to create a flag with key enable_new_editor. The form returns a key conflict error. You navigate back to the flag list and scan the keys. You see enable_new_editor is already in the list, currently Disabled. You do not need to create a new flag: you can toggle the existing one. You click its toggle. It enables immediately.

   Best practice

   Before creating a new flag, always read the full flag list first. The five default flags cover the most common capabilities. A new flag is only needed for a custom capability not covered by the defaults. Use descriptive flag keys: the admin-feature-flags help documentation states: "Keys like pdf_export are clear; keys like flag1 are not." Flag keys cannot be changed after creation, so choose carefully.

What this guide does not cover