Skip to main content

​
Overview

This topic explains how to edit and delete views in LaunchDarkly, and how to require resources to be linked to a view. You can use the Views list and other project settings to manage your views.

​
Edit a view

To edit a view:
  1. From Project settings, select Views. The Views list appears.
  2. Find the view you want to edit.
  3. Click the overflow menu for the view.
  4. Select Edit.
  5. Make any changes to the view. You can update the name, description, tags, and maintainer. You cannot change a view’s key.
  6. Click Save changes.

​
Delete a view

To delete a view:
  1. From Project settings, select Views. The Views list appears.
  2. Find the view you want to delete.
  3. Click the overflow menu for the view.
  4. Select Delete view. A “Delete this view?” dialog appears.
  5. Enter the name or key of your view in the confirmation field.
  6. Click Delete.
Deleting a view unlinks all resources from the view. Any members whose roles included access to specific views will no longer have access to the resources linked in that view. For example, members whose roles included access to a particular view will no longer have access to the flags and segments linked to that view. Deleting a view does not delete any of the resources that were linked to it.

​
Require resources to be linked to a view

If you use views to restrict access to sets of flags or segments, require that they are associated with a view. To require that flags or segments are linked to a view:
  1. From Project settings, select Views.
  2. Click the Settings tab.
  3. Find the “Require new resources to be linked to views” section.
  4. Check one or both checkboxes:
    • Require flags to be linked to a view
    • Require segments to be linked to a view
After you enable this setting, all new flags and segments must be associated with at least one view. Existing flags and segments are unaffected. An alternative way to enforce this is to create a role that allows the createFlag or createSegment action only within a particular view. To learn how, read the View-specific permissions example policy.