> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Using resources

**Developer**

**Federal docs**

**EU docs**

This topic explains how to specify different resources to use with roles, integrations access, and Relay Proxy access.

When you create or update a role, you specify **resources** that the role can or cannot access. Then, you grant access to a specific set of actions associated with that resource.

To learn more about how resources are structured within role policies, read [Member role concepts](https://launchdarkly.com/docs/home/account/roles/role-concepts).

## Specifying resources in the policy builder

When you create a [policy](https://launchdarkly.com/docs/home/getting-started/vocabulary.md#policy-custom-role) statement using the [policy builder](https://launchdarkly.com/docs/home/account/roles/role-create.md#create-policies-for-roles), you use the **Scope** menu to specify the resources that the policy affects:

![The "Scope" and "Select \[resources\]" menus when defining a policy scoped to a select set of applications.](https://mintcdn.com/launchdarkly/-b7nPh0oyigf6iW7/images/auto/custom-roles-policy-builder-scope.auto.png?fit=max\&auto=format\&n=-b7nPh0oyigf6iW7\&q=85\&s=d0154410307d64d127689a629c744072)

The "Scope" and "Select \[resources]" menus when defining a policy scoped to a select set of applications.

Some resources are "scoped" within specific parent resources and require additional context to be correctly identified. For example, feature flags are scoped within a project and environment. In the policy builder, if you initially select the "flag" resource type, the policy builder prompts you to specify projects and environments before you can continue.

You can define the resources explicitly in the policy statement for a role, as in the screenshot above. Alternatively, you can define them based on a parameter that you create.

This parameter is called a [role attribute](https://launchdarkly.com/docs/home/getting-started/vocabulary.md#role-attribute). You define the role attribute when you create the role, and then you set the value of the role attribute when you assign the role to a member, either directly or through a team. For example, you can define the role attribute `projectAttribute`, and set the value of the role attribute to "Project A" when you assign the role to member A. Then you can set the value of the role attribute to "Project B" when you assign the role to member B. Role attributes are available for all resource types.

## Specifying resources in the advanced editor

When you create a [policy](https://launchdarkly.com/docs/home/getting-started/vocabulary.md#policy-custom-role) statement using the [advanced editor](https://launchdarkly.com/docs/home/account/roles/advanced-editor.md), you specify resources in JSON. LaunchDarkly uses a resource specifier syntax to name resources or collections of resources. This is a precise, flexible taxonomy that lets you identify and control any resource in your LaunchDarkly account.

The syntax to specify a resource looks like this:

```text title="Resource specifier syntax" lines wrap theme={null}
resource-type/name;tag1,tag2,{property-based-selector:value}
```

The example above shows two tags separated by a comma, which means the resource must have both `tag1` AND `tag2`. Tags are optional.

The example also shows a property-based selector, which is a way to select resources whose properties match a particular value. To learn more, read [Property-based selectors](https://launchdarkly.com/docs/home/account/roles/role-concepts#property-based-selectors).

If you don't need to use any tags or selectors, you can omit the semicolon (`;`) and all content following.

Some resources are "scoped" within specific parent resources and require additional context to be correctly identified. For example, feature flags are scoped within a project and environment.

You can name scoped resources by using the resource syntax structure depicted below:

```text title="Scoped resources" lines wrap theme={null}
resource-type/name;tag1,tag2:resource-type/name;tag3,tag4,tag5
```

The following example names all feature flags across all environments:

```text title="All feature flags" lines wrap theme={null}
proj/*:env/*:flag/*
```

In the example above, `proj/*:`includes all named projects in the list of results. `env/*:` includes all environments in the list of results. `flag/*:` includes all flags in the list of results. This example will return very broad results because of how comprehensive its permissions are.

> [!NOTE]
>
> **Resource types do not share permissions**
>
> Member permissions are specific to each resource type, and different types do not share or inherit permissions. For example, if you set member permissions for a project with the ID `default` using `proj/default`, the member does not have the same permissions for the project's environments unless you also set member permissions for `proj/default:env/*`.

For a more refined example, you could name all feature flags whose keys start with `ops_`:

```text title="All feature flags with keys that begin with 'ops_'" lines wrap theme={null}
proj/*:env/*:flag/ops_*
```

Finally, you could name all feature flags in critical environments:

```text title="All feature flags in critical environments" lines wrap theme={null}
proj/*:env/*;{critical:true}:flag/*
```

### Additional examples of resource specifier syntax

Expand the section below to review additional examples of resource specifier syntax. You only need this information if you are creating your policy statements in JSON. You do not need to review this information if you use the [policy builder](https://launchdarkly.com/docs/home/account/roles/role-create.md#create-policies-for-roles).

> [accordion] Expand additional examples of resource specifier syntax
>
> The example below creates a resource that names all of the projects in an account:
>
> ```text title="Resource showing all projects" lines wrap theme={null}
> proj/*
> ```
>
> > [!NOTE]
> >
> > **Syntax supports wildcards**
> >
> > The resource syntax accepts globs and wildcards, so you can name collections of resources with `*`. You can also name a specific project by its key.
>
> The example below names a project by the `default` key.
>
> ```text title="Project key is 'default'" lines wrap theme={null}
> proj/default
> ```
>
> You can name sets of resources down to the tag level.
>
> The example below names all projects with the `mobile` tag.
>
> ```text title="All projects tagged 'mobile'" lines wrap theme={null}
> proj/*;mobile
> ```
>
> To learn more, read [Using the advanced editor](https://launchdarkly.com/docs/home/account/roles/advanced-editor.md).

## About resource types and scopes

To review which resources the LaunchDarkly preset roles have access to:

1. Click the **gear** icon in the left sidebar to view Organization settings.
2. Click **Roles** and find the role you wish to review. LaunchDarkly provides both project and organization preset roles. Select the **Project** or **Organization** tab as needed.
3. Click the role name. A summary of the role and its policy statements appears.
4. (Optional) Click **View JSON** to view the specific resources listed out by written expression.

To review which resources the LaunchDarkly base roles and preset roles have access to, expand the section below. It contains a reference list of all the supported resources in LaunchDarkly, their scopes, the role that has access to the resource, and the resource identifier, ordered by written expression.

You only need this information if you are creating your policy statements in JSON. You do not need to review this information if you use the [policy builder](https://launchdarkly.com/docs/home/account/roles/role-create.md#create-policies-for-roles). In the policy builder all of the supported resources are available directly in the user interface.

> [accordion] Expand reference list of supported resources in LaunchDarkly
>
> Here is a reference list of all the supported resources in LaunchDarkly, their scopes, the preset and base roles that have access to the resource, and the resource identifier, ordered by written expression:
>
> <table>
>   <thead>
>     <tr>
>       <th>Resource type</th>
>       <th>Resource scope</th>
>       <th>Preset roles with access</th>
>       <th>Resource identifier</th>
>     </tr>
>   </thead>
>
>   <tbody>
>     <tr>
>       <td>
>         `acct`
>       </td>
>
>       <td>
>         A unique resource specifier representing modifications to your account itself.
>       </td>
>
>       <td>
>         Billing admin, Organization admin
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `application`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `application/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Application key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `code-reference-repository`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `code-reference-repository/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Git repository name
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `domain-verification`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `domain-verification/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Domain ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `integration`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `integration/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Integration ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `member`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `member/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Member ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `token`
>       </td>
>
>       <td>
>         A child of a member, written as:\\
>
>         `member/*:token/*`
>       </td>
>
>       <td>
>         Organization admin, Architect, Member
>       </td>
>
>       <td>
>         Personal access token ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `pending-request`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `pending-request/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `proj`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `proj/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer
>       </td>
>
>       <td>
>         Project key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `agent-graph`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:agent-graph/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Agent graph key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `agent-optimization`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:agent-optimization/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Agent optimization key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `agent-skill`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:agent-skill/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Agent skill key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `ai-dataset`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:ai-dataset/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         AI dataset key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `ai-evaluation`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:ai-evaluation/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         AI evaluation key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `ai-tool`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:ai-tool/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         AI tool key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `ai-code-sync`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:ai-code-sync/*`
>       </td>
>
>       <td>
>         Project Admin, Maintainer, Developer, Writer
>       </td>
>
>       <td>
>         AI code sync key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `alert`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:alert/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `context-kind`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:context-kind/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Context kind key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `env`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:env/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Environment key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `error`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:error/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `log`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:log/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `observability-dashboard`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:observability-dashboard/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Dashboard ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `prompt-snippet`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:prompt-snippet/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Prompt snippet key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `session`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:session/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `sdk-key`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:sdk-key/*`
>       </td>
>
>       <td>
>         Project admin
>       </td>
>
>       <td>
>         SDK key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `trace`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:trace/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager
>       </td>
>
>       <td>
>         Not applicable
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `vega`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:vega/*`
>       </td>
>
>       <td>
>         Project admin, Project developer, View developer
>       </td>
>
>       <td>
>         Conversation ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `aiconfig`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:aiconfig/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager, Contributor, Reviewer
>       </td>
>
>       <td>
>         AgentControl config key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `ai-model-config`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:ai-model-config/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Release manager
>       </td>
>
>       <td>
>         Model name and model ID, concatenated with a hyphen (`-`)
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `assignment-data-source`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:assignment-data-source/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Release manager
>       </td>
>
>       <td>
>         Data source key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `attribute-data-source`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:attribute-data-source/*`
>       </td>
>
>       <td>
>         Project Admin, Owner, Developer
>       </td>
>
>       <td>
>         Data source key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `destination`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:destination/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer
>       </td>
>
>       <td>
>         Data Export destination ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `experiment`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:experiment/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Experiment key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `flag`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:flag/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Release manager, Contributor, Reviewer
>       </td>
>
>       <td>
>         Flag key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `holdout`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:holdout/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Holdout key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `metric-data-source`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:metric-data-source/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Data source key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `segment`
>       </td>
>
>       <td>
>         A child of a project and an environment, written as:\\
>
>         `proj/*:env/*:segment/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer, Reviewer
>       </td>
>
>       <td>
>         Segment key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `layer`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:layer/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Layer key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `metric`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:metric/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Metric key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `metric-group`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:metric-group/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         Metric group key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `release-pipeline`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:release-pipeline/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Release manager
>       </td>
>
>       <td>
>         Release pipeline key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `release-policy`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:release-policy/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Release manager
>       </td>
>
>       <td>
>         Release policy key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `flag-release`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:flag-release/*`
>       </td>
>
>       <td>
>         Project Admin, Maintainer, Owner, Admin
>       </td>
>
>       <td>
>         Flag release ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `flag-release-plan`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:flag-release-plan/*`
>       </td>
>
>       <td>
>         Project Admin, Maintainer, Owner, Admin
>       </td>
>
>       <td>
>         Flag release plan key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `view`
>       </td>
>
>       <td>
>         A child of a project, written as:\\
>
>         `proj/*:view/*`
>       </td>
>
>       <td>
>         Project admin, Maintainer, Project developer, View developer
>       </td>
>
>       <td>
>         View key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `relay-proxy-config`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `relay-proxy-config/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Relay Proxy configuration ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `role`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `role/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Role key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `service-token`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `service-token/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Service token ID
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `team`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `team/*`
>       </td>
>
>       <td>
>         Organization admin, Architect, Member
>       </td>
>
>       <td>
>         Team key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `template`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `template/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Workflow template key
>       </td>
>     </tr>
>
>     <tr>
>       <td>
>         `webhook`
>       </td>
>
>       <td>
>         A top-level resource, written as:\\
>
>         `webhook/*`
>       </td>
>
>       <td>
>         Organization admin, Architect
>       </td>
>
>       <td>
>         Webhook ID
>       </td>
>     </tr>
>   </tbody>
> </table>
>
> > [!NOTE]
> >
> > **The user resource is only relevant when working with older SDKs**
> >
> > If you are working with older SDKs, which do not yet support contexts, you can also reference the `user` resource. The `user` resource is scoped to a project and environment. It has one action, `deleteUser`. This action allows you to delete context instances, including users, which appear as context instances on the **Contexts** list. To learn more, read [Remove a context instance](https://launchdarkly.com/docs/home/flags/contexts-list#remove-a-context-instance).
> >
> > If you are working with [SDKs that have been updated for contexts](https://launchdarkly.com/docs/sdk.md), the equivalent action is `deleteContextInstance`, which is scoped to the environment resource. To learn more, read [Environment actions](https://launchdarkly.com/docs/home/account/roles/role-actions.md#environment-actions).
> >
> > We strongly encourage you to upgrade your SDKs to versions supporting contexts.

For a list of all actions available to each resource, read [Using actions](https://launchdarkly.com/docs/home/account/roles/role-actions.md). To learn more about how to create roles with access to these resources, read the [Creating roles](https://launchdarkly.com/docs/guides/teams-roles/custom-roles.md) guide.
