Manage account member roles

Overview

This topic explains what built-in and custom roles are, which built-in roles LaunchDarkly offers for account members, and why you might use LaunchDarkly's custom roles feature to create roles with precise permissions and access to different aspects of LaunchDarkly.

The other topics in this category explain how to set up and manage roles for the people who use your LaunchDarkly account:

• Adding member roles
• Viewing member roles
• Changing member roles
• Removing member roles

Account members are people who work at your organization or have access rights to your organization's LaunchDarkly account for another reason, such as contractors or part-time employees. To learn more, read Account members.

LaunchDarkly role types

Account members are assigned member roles. LaunchDarkly has two types of member roles. They are:

• Built-in roles
• Custom roles

Each account member must have at least one role. Members can have both built-in roles and custom roles. If you manage your members with LaunchDarkly teams, a member's roles will aggregate with the custom roles that are applied to their teams. To learn more, read Teams.

Built-in roles

Every LaunchDarkly account has four built-in roles. They are:

• Reader
• Writer
• Admin
• Owner

Customers on an Enterprise plan also have a restricted No access role.

To learn more, read Built-in roles.

Custom roles

In addition to built-in roles, customers on an Enterprise plan can optionally configure custom roles. Custom roles are sets of permissions that give members or teams extremely precise access to different resources in LaunchDarkly, as well as the ability to perform only certain actions in your LaunchDarkly account. To learn more, read Custom roles.

How built-in roles interact with custom roles

You can give account members granular control to LaunchDarkly using custom roles. Custom roles let you define specific permissions for members or teams and apply them across your organization. Custom roles can increase the permissions given to a built-in role.

This is useful if you have members with multiple jobs, such as someone who needs access to flags controlled by an engineering team and the support team, or product managers who also code.