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
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
      • Member role concepts
      • Managing role assignments
        • Assigning roles to members
        • Viewing member roles
        • Changing member roles
        • Removing member roles
        • Assigning roles to teams
        • Changing account Owners
      • Managing roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • How team roles interact with individual member roles
  • Assign roles to teams
  • Remove a role from a team
Your accountRolesManaging role assignments

Assigning roles to teams

Was this page helpful?
Previous

Changing account Owners

Next
Built with

Overview

This topic explains how to assign roles to teams in LaunchDarkly.

How team roles interact with individual member roles

Every organization using LaunchDarkly is made up of members. Members are people who work for your organization or use your organization’s LaunchDarkly account.

You assign roles directly to members when you invite them to LaunchDarkly. You must assign a role to each member when they are invited, even if that role allows no access.

After a member has been invited, you can assign additional roles to them at any time. You can use either of the following methods:

  • You can assign the additional roles directly to an account member. When a member is directly assigned a role, that role is used instead of the member’s base role to determine the member’s access. To learn more, read Assigning roles to members.
  • You can assign the additional roles to a team the account member is on. When a member is given a role as part of a team, that role is used in addition to the member’s base role or other directly assigned roles to determine the member’s access.

A team can have one or more roles assigned to it. In cases where a team’s roles have conflicting permission levels, or a team’s role has conflicting permission levels with the permissions assigned to a member of that team, the more permissive set of permissions will be applied. For example, if a team has one role that allows access to a resource, and a member of that team has another role that restricts access to a resource, the team member will be able to access that resource.

Team role permissions are cumulative

If a team has one or more roles, then for each account member on the team, the account member’s access is defined by both the member’s role and the roles assigned to the team.

For example, if a member has a Reader base role and is assigned another role through their team, then the member will continue to have read access to all resources through the Reader role, in addition to the access granted through their team. As another example, if a member is assigned the LaunchDarkly Member role directly, and is assigned the LaunchDarkly Developer role through their team, the Developer access is used in addition to Member access.

To learn more, read How roles interact.

Assign roles to teams

You can assign roles to a team from the Access tab for the team you manage.

To assign a role to a team:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Teams.
  3. Click on the name of the team. The team’s Members tab appears.
  4. Click on the team’s Access tab.
  5. Click Assign access. The “Assign access” dialog appears.
  6. Select a project role to add to the team.
  7. Click Assign access.

Remove a role from a team

To remove a role from a team:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Teams.
  3. Click on the name of the team. The team’s Members tab appears.
  4. Click on the team’s Access tab.
  5. Find the role you want to remove in the list of roles.
  6. Click the three-dot overflow menu next to that role.
  7. Click Remove access. A confirmation dialog appears.
  8. Click Remove access in the dialog to confirm.