Views

This feature is for Early Access Program customers only

Views are only available to members of LaunchDarkly’s Early Access Program (EAP). If you want access to this feature, join the EAP.

Overview

This topic explains what views are in LaunchDarkly and how to use them to organize flags and flag access in your projects.

Views are resources to logically group flags within a project. You can use views to group flags according to the teams in your organization and the features they work on. A given flag can be linked to more than one view.

Views let you restrict access to sets of flags, so that members of your organization can focus on just the flags they work with. Because you can have multiple views per project, you can scale your LaunchDarkly usage to thousands of flags while maintaining the benefits of a single project, such as flag dependencies.

Create a view

To create a new view:

  1. Click the project dropdown. The project menu appears:

    The project menu.

    The project menu.
  2. Select Project settings.

  3. Select Views. The Views list appears.

  4. Click Create view. The “Create view” dialog appears.

  5. Enter a unique, human-readable Name for the view.

  6. (Optional) Update the view Key. A suggested key auto-populates from the name you enter, but you can customize it if you wish.

  7. (Optional) Enter a Description.

  8. (Optional) Click Add tags. Enter a tag name to search for an existing tag or create a new one with that name.

  9. (Optional) Click Choose maintainer to set the maintainer of the view.

  10. Click Create & link flags. The “Link flags” dialog appears.

  11. Check the flags that you want to include in the view.

  12. Click Update flag links.

You can also create a view and then link flags later. To create a view without linking any flags, follow steps 1-9 in the procedure above, and then click Create view & close.

After you create a view, you can use it in role policies to restrict access to sets of flags. For an example of using a view in a role policy, read Example: View-specific permissions.

To link a flag to an existing view when you create the flag, use the Add views dropdown in the “Details” section of the create flag page.

To link a flag to a view from the flag details page:

  1. From the flag detail page, find “Views” in the right sidebar.
  2. Click the pencil icon.
  3. Check the checkbox next to the views that you want to link the flag to.

To link flags to an existing view from the Views list:

  1. From Project settings, select Views. The Views list appears.
  2. Find the view you want to add flags to.
  3. Click the overflow menu for the view.
  4. Select Update flag links. The “Link flags” dialog appears.
  5. Check the flags that you want to include in the view.
  6. Click Update flag links.

Manage views

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 edit.
  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 flags from the view. Any members whose roles included access to specific views will no longer have access to the flags in that view.

Deleting a view does not delete any of the flags that were linked to it.

Require flags to be linked to a view

If you use views to restrict access to sets of flags, it may be helpful to require that flags are associated with a view. One way to enforce this is to create a role that only allows the createFlag action within a particular view. To learn how, read the View-specific permissions example policy.