Domino uses feature flags to control the functionality available to individual users, organizations, or entire deployments, giving administrators the ability to customize Domino’s functionality and safely test and release new features.
Administrators (and support staff) can access feature flags from the advanced drop down of the admin console (Username > Admin).
From the feature flags console, user-specific flags (that only impact you) will show up in the “User-Scope Overrides” Section, while flags that impact all users appear in the “Deployment Global” Section. Also on this page you’ll find a brief description of what each flag does, any relevant warning messages, and an activation toggle.
Setting Feature Flags
- To set feature flags you must either be Support Staff or an administrator for your deployment.
- Navigate to the feature flags page of the admin console (Username > Admin > Advanced > Feature Flags)
- From this page you can set user-specific flags for yourself or global flags for all users
- For setting user-specific flags for another user, replace your username in the URL of the feature flags page with that of the desired user. Note: Global feature flags do not depend on the username in the URL.
- Find the desired feature flag.
- Change the status of the flag using the drop down list - the default will be indicated.
- While global flags require choosing true or false, user flags have the option to default to the global setting, which will simply match the value set in the global flag.
- After making a selection, a status message will verify that the flag was set successfully.
Additional Notes
- Priority - User-specific flags will override global settings, allowing you to enable (or disable) a feature for a subset of users.
- Latency - Feature flag changes should propagate in only a few seconds, and do not require a restart of the server.
- Central Configuration Conflicts - Some feature flags override a setting defined in the central configuration. If this is the case, Domino will provide a warning and reference the relevant configuration setting, but will ignore the central configuration and adhere to the feature flag. If this is the case, we recommend you remove the setting from the central configuration to prevent future conflicts.
Comments
0 comments
Please sign in to leave a comment.