For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
      • Create views
      • Manage views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Edit a view
  • Delete a view
  • Require resources to be linked to a view
Your accountViews

Manage views

Was this page helpful?
Previous

Environments

Next
Built with

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, AgentControl configs, 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, AgentControl configs, or segments, require that they are associated with a view.

To require that resources 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 more checkboxes:
    • Require flags and AgentControl configs to be linked to a view
    • Require segments to be linked to a view

After you enable this setting, all new selected resources must be associated with at least one view. Existing resources are unaffected.

An alternative way to enforce this is to create a role that allows the createFlag, createAIConfig, or createSegment action only within a particular view. To learn how, read the View-specific permissions example policy.