Using actions
This topic is a complete reference of all actions that are available to use in role policies. It includes tables with all supported actions and details about them. These actions are scoped by resource type.
Actions represent changes you can make to resources, such as createFlag
, deleteFlag
, updateName
, and more.
To learn more about how actions work within role policies, read Member role concepts.
When new features are added to LaunchDarkly, there may be new associated actions. We recommend reviewing these actions periodically to determine if you want to add them to any of your roles. If you are using preset roles provided by LaunchDarkly, you can choose when to update your preset roles to the latest versions. To learn how, read Update organization roles and Update project roles.
This table describes new actions that have been added to LaunchDarkly recently:
These are all the actions you can take, sorted by each resource type.
When you create a policy using the policy builder, actions relevant to the resource scope you’ve selected automatically appear in the policy builder:
When you create a policy using the advanced editor, you can specify actions individually, or in bulk using glob syntax and wildcards. For example, you can describe all modifications to feature flags with the action specifier update*
.
Expand Account actions
acct
is a top-level resource. A code sample is below:
This table explains available account actions:
This table explains available account ownership actions:
Expand AI Config actions
aiconfig
is a child of both a project and an environment. The code example below grants permission to update targeting rules for all AI Configs across all projects and environments.
This table explains available AI Config actions related to settings and targeting changes:
This table explains AI Config actions related to collaboration:
Expand AI tool actions
ai-tool
is a child resource of a project. A code sample is below:
This table explains available AI tool actions:
Expand AI model config actions
ai-model-config
is a child resource of both a project and an environment. A code sample is below:
This table explains available AI model config actions:
Expand Application actions
application
is a top-level resource. A code sample is below:
This table explains available application actions:
Expand Application version actions
application version
is a child resource of applications. A code sample is below:
This table explains available application version actions:
Expand Code reference actions
code-reference-repository
is a top-level resource. A code sample is below:
To learn more, read Code references.
This table explains available code reference actions:
Expand Context kind actions
context-kind
is a child of a project. A code sample is below:
To learn more, read Context kinds.
This table explains available context kind actions:
Expand Destination actions
destination
is a child of both a project and an environment. A code sample is below:
To learn more, read Data Export.
This table explains available Data Export destinations actions:
Expand Domain verification actions
domain-verification
is a top-level resource. A code sample is below:
To learn more, read Domain verification.
This table explains available domain verification kind actions:
Expand Environment actions
env
is a child of a project. A code sample is below:
To learn more, read Environments.
This table explains available environment actions:
More information about viewSdkKey
The deny
effect in the viewSdkKey
action hides the server-side SDK key you specify from the member. However, the allow
effect for the same resource and action pairing doesn’t do anything. Your LaunchDarkly member does not need explicit permission to view the keys, because all custom roles can view all environments in a LaunchDarkly instance by default.
Expand Experiment actions
experiment
is a child of both a project and an environment. A code sample is below:
To learn more, read Experimentation.
This table explains available experiment actions:
Expand Feature flag actions
flag
is a child of both a project and an environment. A code sample is below:
To learn more, read Creating new flags.
Some feature flag actions affect only the current environment. Other feature flag actions affect all environments in a project.
This table explains feature flag actions related to targeting changes. Unless otherwise specified, these actions affect only the current environment:
This table explains feature flag actions related to flag settings. Each of these actions affects all environments in a project:
This table explains feature flag actions related to environment-specific settings:
This table explains feature flag actions related to collaboration:
This table explains feature flag actions related to other flag changes:
Expand Holdout actions
holdout
is a child of both a project and an environment. A code sample is below:
To learn more, read Holdouts.
This table explains available holdout actions:
Expand Integration actions
Most third-party integrations use a shared set of custom role actions.
integration
is a top-level resource. A code sample is below:
To learn more, read Integrations.
This table explains available integration actions:
Expand Layer actions
layer
is a child of a project. A code sample is below:
To learn more, read Mutually exclusive experiments.
This table explains available layer actions:
Expand Member actions
member
is a top-level resource. A code sample is below:
To learn more, read Members.
This table explains available member actions:
Expand Metric actions
metric
is a child of a project. A code sample is below:
To learn more, read Metrics.
This table explains available metric actions:
Expand Metric group actions
metric-group
is a child of a project. Guardrail metrics groups are a type of metric group, but have their own actions.
A code sample is below:
To learn more, read Metric groups.
This table explains available metric group actions:
This table explains available guardrail metrics group actions:
Expand Pending request actions
pending-request
is a top-level resource. A code sample is below:
To learn more, read Accept pending requests.
This table explains available personal access token actions:
Expand Personal access token actions
token
is a child of a member. A code sample is below:
To learn more, read API access tokens.
This table explains available personal access token actions:
Expand Product analytics dashboard actions
productAnalyticsDashboard
is a child of both a project and an environment. A code sample is below:
To learn more, read Product analytics.
This table explains available product analytics dashboard actions:
Expand Project actions
proj
is a top-level resource. A code sample is below:
To learn more, read Projects.
This table explains available project actions:
More information about viewProject
Starting in October 2024, all new roles start with no access. This means the roles cannot take any actions on any resources. Make sure to add explicit permission to view projects to any roles that you create.
Older custom roles may have read-only access to all resources by default. This is because roles created prior to October 2024 had the option to use the Reader base role as their starting point, rather than starting with no access.
To learn more, read Project roles and Create private projects with custom roles.
Expand Relay Proxy configuration actions
relay-proxy-config
is a top-level resource for which you can allow or deny certain actions.
Here is an example:
To learn more, read Automatic configuration.
This table explains available Relay Proxy automatic configuration actions:
Expand Release pipeline actions
release-pipeline
is a child of a project. A code sample is below:
This table explains available release pipeline actions:
Expand release policies actions
release-policy
is a child of a project.
To learn more, read Release policies.
This table explains available release policies actions:
Expand Role actions
role
is a top-level resource. A code sample is below:
To learn more, read Roles.
This table explains available role actions:
Expand Segment actions
segment
is a child of both a project and an environment. A code sample is below:
To learn more, read Segments.
This table explains available segments actions:
Expand Service access token actions
service-token
is a top-level resource. A code sample is below:
To learn more, read API access tokens.
This table explains available service access token actions:
Expand Team actions
team
is a top-level resource. A code sample is below:
To learn more, read Teams.
This table explains available team actions:
More information about the viewTeam action
The deny
effect for your resource
in the viewTeam
action hides the teams you specify from the member. The allow
effect for the same resource and action pairing doesn’t do anything because your account member can already view the team.
To learn more, read Create private teams.
Expand Template actions
template
is a top-level resource. A code sample is below:
To learn more, read Workflow templates.
This table explains available workflow template actions:
Expand View actions
view
is a child of a project. A code sample is below:
To learn more, review Views.
This table explains available view actions:
Expand Webhook actions
webhook
is a top-level resource. A code sample is below:
To learn more, read Webhooks.
This table explains available webhooks actions: