No results for ""
EXPAND ALL
  • Home
  • API docs

Using the advanced editor

Read time: 2 minutes
Last edited: Oct 21, 2024

Overview

The advanced editor is a tool for experienced LaunchDarkly members who want to create their own custom roles. You can use it to create custom roles and policies that are more complex and detailed than those supported by the policy builder.

You can copy example roles or templates that assign the same permissions as LaunchDarkly's built-in roles from the topic Example policies and templates. In the advanced editor, you can modify those templates to do exactly what you want.

The advanced editor is powerful

The advanced editor can cause large permissions changes to sensitive or confidential resources. If you use the advanced editor incorrectly, it is possible to disable your LaunchDarkly project, lock yourself out of your account, or cause other irrevocable changes.

It is critically important that you read all the documentation in the "Custom roles" section thoroughly before you use the advanced editor to create or modify any custom roles.

To learn more, read Custom role concepts.

Create custom role policies with the advanced editor

To access the advanced editor:

  1. Click the gear icon in the left sidenav to view Organization settings.
  2. Click Roles in the left sidenav.
  3. Click Create role. The New role page appears:
The New role page.
The New role page.
  1. In the "Create Policy" panel, click View JSON.
  2. (Optional) If you do not wish to use the advanced editor, click Policy builder to return to the graphical policy builder. Continue with the procedure Create policies for custom roles.
  3. Specify the effects, resources, and actions you wish. You can also specify inverse action and resource sets using notActions and notResources respectively.
  4. Click Create role.

When you create a policy with the advanced editor, you must use resource keys, not display names. If you use their names, the policies will not take effect. The resource keys are case-sensitive. For example, if the production environment of your default project has the key production, then referencing proj/default:env/Production in your policy will not work.

For advanced policy examples, read Example policies and templates.