Example policies and templates

This example policy uses the * wildcard to allow members of the QA team to administer environments that have tags beginning with qa_, such as qa_test, qa_production, and so on. This policy also allows members to manage flags in environments that have tags beginning with qa_.

To manage flags in environments tagged qa_*, you must specify the flag-level resource you want to control. Limiting resources to "proj/*:env/*;qa_*" lets you manage the environment itself.

When you recreate this custom role, keep the By default, members can view all LaunchDarkly content box checked.

Copy this role and make any modifications to it to suit your needs:

Here are two example policies that use the {property:value} pattern to allow actions on environments based on whether or not they are critical environments. You can mark any environment as critical when you create or update it. Production environments default to being marked as critical.

To manage environments based on the critical property, you must specify the property-based selector as part of the modifiers for the environment resource. Limiting resources to "proj/*:env/*;{critical:true}" accomplishes this.

In the first example, the policy allows members of the DevOps team to administer environments that are marked as critical and tagged as fedramp-enabled. This policy also allows members to manage flags in environments that are marked as critical and tagged as fedramp-enabled.

Copy this role and make any modifications to it to suit your needs:

In the second example, the policy allows members of the Support Team to perform all actions on all environments not marked as critical with flags tagged with support.

Copy this role and make any modifications to it to suit your needs:

This example policy uses the {property:value} pattern to deny actions on environments based on whether or not they are critical environments. You can mark any environment as critical when you create or update it. Production environments default to being marked as critical.

To manage environments based on the critical property, you must specify the property-based selector as part of the modifiers for the environment resource. Limiting resources to "proj/*:env/*;{critical:true}" accomplishes this.

Copy this role and make any modifications to it to suit your needs:

One way to organize access to resources is by tagging individual resources, and then creating custom roles with access based on those tags. For example, you can create a dev tag for your environments and use it in a policy to allow access only to development environments. You can add tags to projects, environments, segments, flags, and metrics.

Copy this role and make any modifications to it to suit your needs:

Anyone with this custom role can edit resources that have a dev tag.

For more tag policy examples, read Tags in custom role policies.

This example policy allows members of the Ops team to toggle on or off any flags in the production environment. They may not change percentage rollouts or targeting rules, or manage any environments or projects.

Copy this role and make any modifications to it to suit your needs:

The policy below allows all actions to be done to a single specified flag, flag-1.

For a complete list of flag actions, read Feature flag actions.

Copy this role and make any modifications to it to suit your needs:

The policy below allows access only to a project a flag is in, and allows you to perform actions on that flag. In this example, the flag is called flag-1.

Copy this role and make any modifications to it to suit your needs:

This policy allows using only these actions in the production-1 environment:

• updateFlagVariations
• updateTags

This means you can take all other actions in any other non-production environment.

Copy this role and make any modifications to it to suit your needs:

The second statement in the code snippet above allows all actions in all environments and to all flags in the project named project-1. You must specifically allow access, or the roles default to the No access role.

In this example, we allow specific flag actions in one project, all segment actions in all projects, and all metric actions in all projects. When you restrict all actions this comprehensively, you must add each action for flags, segments, and metrics explicitly.

Copy this role and make any modifications to it to suit your needs:

In the next example, the environment key production represents the account's Production environment. This statement denies the member from modifying any feature flags in production:

You can also name an "inverse" set of resources by using notResources in a statement. notResources explicitly allows all actions to feature flags across all environments except an environment you specify.

In the example below, the combination of notResources and the allow effect gives access to all environments except the production environment.

Here's how:

Copy this Reader role and make any modifications to it to suit your needs:

Because permissions are set to deny by default, you must explicitly allow actions for the Writer role. The code snippet below is a replication of LaunchDarkly's built-in Writer role. You can copy it and make adjustments as needed.

Copy this Writer role and make any modifications to it to suit your needs:

Because permissions are set to deny by default, you must explicitly allow actions for the Admin role. The code snippet below is a replication of LaunchDarkly's built-in Admin role. You can copy it and make adjustments as needed.

Copy this Admin role and make any modifications to it to suit your needs:

Permissions are set to deny by default. In other words, by default, custom roles cannot take any actions on any resources. You must create a policy that provides the level of access you prefer. An empty policy is equivalent to the built-in No access role.