Feature Flags

Feature flags let instance administrators enable or disable specific platform capabilities across the entire SetGet instance. This gives you control over which features are available to users, allowing for gradual rollout and customized deployments.

Navigate to Admin Panel > Feature Flags or go directly to /backoffice/settings/features.

How feature flags work

Each feature flag is a boolean toggle (on/off) that controls the visibility and availability of a specific platform capability. When a feature is disabled:

• Its UI elements (sidebar links, buttons, menus) are hidden from all users.
• Its API endpoints return 403 Forbidden.
• Existing data created while the feature was enabled is preserved but inaccessible until re-enabled.

Feature flags are evaluated on every request, so changes take effect immediately without requiring a restart or deployment.

Available feature flags

Feature	Description	Default
Chat	Real-time messaging within workspaces	Enabled
AI Assistant	AI-powered conversational assistant and suggestions	Disabled
Intake	Intake forms for collecting work requests from external users	Enabled
Time Tracking	Log and report time spent on work items	Enabled
Pages / Wiki	Knowledge base and documentation pages	Enabled
Cycles	Sprint/cycle-based planning	Enabled
Modules	Module-based project grouping	Enabled
Views	Custom saved views and filters	Enabled
Automations	Rule-based workflow automations	Enabled
Analytics	Workspace and project analytics dashboards	Enabled
Notifications	In-app and email notifications	Enabled
Import / Export	Data import and export tools	Enabled
Integrations	Third-party integrations (GitHub, Slack, etc.)	Enabled
API Access	Developer API access	Enabled

Enabling or disabling a feature

1. Navigate to Admin Panel > Feature Flags.
2. Find the feature in the list.
3. Toggle the switch to On (enabled) or Off (disabled).
4. A confirmation dialog appears for features that affect active users.
5. Click Confirm to apply the change.
6. The change takes effect immediately for all users.

WARNING

Disabling a feature that is actively used by teams will immediately remove it from their interface. Communicate planned changes to workspace administrators before toggling features off.

Feature flag effects

When a feature is disabled

Aspect	Behavior
Sidebar navigation	Feature link removed from sidebar
Workspace settings	Feature configuration section hidden
API endpoints	Requests return 403 with message "Feature not available"
Existing data	Preserved in database, not deleted
Search results	Feature-specific results excluded
Notifications	Feature-related notifications suppressed

When a feature is re-enabled

Aspect	Behavior
Sidebar navigation	Feature link reappears
Data	All previously created data is accessible again
Ongoing work	Cycles, modules, and other time-bound features resume
User settings	Per-user feature preferences are restored

Gradual rollout

For new or experimental features, you can roll out access gradually instead of enabling a feature for the entire instance at once.

Rollout method	Description
By workspace	Enable the feature for specific workspaces only
By percentage	Enable for a random percentage of workspaces
By user role	Enable for users with specific roles (e.g., Admins only)

Workspace-specific rollout

1. Set the feature flag to Gradual Rollout mode instead of On/Off.
2. Select the workspaces that should have access.
3. Monitor usage and feedback.
4. Expand to additional workspaces or enable globally when ready.

Percentage-based rollout

1. Set the feature flag to Percentage mode.
2. Enter the percentage (e.g., 25%).
3. SetGet deterministically assigns workspaces to the enabled group based on workspace ID.
4. Increase the percentage over time.
5. Set to 100% to enable globally.

TIP

Gradual rollout is especially useful for the AI Assistant feature, where you may want to validate usage patterns and costs with a small group before enabling it for everyone.

Feature dependencies

Some features depend on other features or configurations:

Feature	Dependencies
AI Assistant	AI provider must be configured in AI Configuration
Chat	Redis must be available for real-time messaging
Notifications	SMTP must be configured for email notifications
Import / Export	Storage must be configured for file handling
Intake	Email (SMTP) required for intake form notifications

If a dependency is not met, the feature flag toggle shows a warning indicating what must be configured first.

Monitoring feature usage

The Feature Flags page includes usage statistics for each feature:

Metric	Description
Active users (7 days)	Number of unique users who used the feature in the last 7 days
Workspaces using	Number of workspaces with active feature usage
API calls (30 days)	Number of API calls to feature-specific endpoints

This data helps you decide whether to keep, expand, or disable features based on actual adoption.

Best practices

Practice	Reason
Disable unused features	Reduces UI clutter and attack surface
Use gradual rollout for new features	Limits risk and allows feedback collection
Monitor usage before disabling	Avoid removing features teams rely on
Communicate changes in advance	Teams need time to adapt workflows
Document feature flag decisions	Helps future admins understand the current state

Feature flag audit trail

All feature flag changes are recorded in the Audit Logs with the action settings.features.updated. Each entry includes:

• Which feature was toggled
• Previous state (on/off)
• New state (on/off)
• Who made the change
• When the change occurred

Related pages

• Admin Panel Overview — Navigate the Admin Panel
• AI Configuration — Configure AI provider (required for AI features)
• Email / SMTP Settings — Required for notification-dependent features
• Storage Configuration — Required for import/export features