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

# Using actions

> This topic is a complete reference of all actions that are available to use in role policies.

> For the complete documentation index, see [llms.txt](/llms.txt). For the full documentation snapshot, see [llms-full.txt](/llms-full.txt).

## Overview

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. Each action is scoped to a 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](/home/account/roles/role-concepts#actions).

## Recently added actions

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](/home/getting-started/vocabulary#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](/home/account/roles/organization-roles#update-organization-roles) and [Update project roles](/home/account/roles/project-roles#update-project-roles).

This table describes new actions that have been added to LaunchDarkly recently:

\| Resource

\| New actions

\| Learn more

| Date introduced |
| - |

\| ---

\| ---

\| --- |
\| <code>acct</code>

\| <code>createAIEvaluation</code> , <code>deleteAIEvaluation</code> , <code>updateAIEvaluation</code>

\| [AI evaluation actions](#ai-evaluation-actions)

\| April 2026 |
\| <code>acct</code>

\| <code>disableIdPManagingTeams</code> , <code>enableIdPManagingTeams</code>

\| [Account actions](#account-actions)

\| February 2026 |
\| <code> proj/*:env/*:notification-subscription/\* </code>

\| <code>createNotificationSubscription</code> , <code>deleteNotificationSubscription</code>

\| [Notification subscription actions](#notification-subscription-actions)

\| February 2026 |
\| <code> proj/*:agent-graph/* </code>

\| <code>createAgentGraph</code> , <code>updateAgentGraph</code> , <code>deleteAgentGraph</code>

\| [Agent graphs actions](#agent-graphs-actions)

\| January 2026 |
\| <code> proj/*:metric/* </code>

\| <code>updateAnalysisType</code>

\| [Metric actions](#metric-actions)

\| January 2026 |
\| <code>proj/\*</code>

\| <code> updateObservabilitySettings </code>

\| [Project actions](#project-actions)

\| December 2025 |
\| <code>proj/*:trace/*</code>

\| <code> viewTrace </code>

\| [Trace actions](#trace-actions)

\| December 2025 |
\| <code>proj/*:log/*</code>

\| <code> viewLog </code>

\| [Log actions](#log-actions)

\| December 2025 |
\| <code>proj/*:error/*</code>

\| <code>updateErrorStatus</code>, <code>viewError</code>

\| [Error actions](#error-actions)

\| December 2025 |
\| <code>proj/*:session/*</code>

\| <code> viewSession </code>

\| [Session actions](#session-actions)

\| December 2025 |
\| <code>proj/*:alert/*</code>

\| <code>createAlert</code>, <code>deleteAlert</code>, <code>updateAlertOn</code>, <code>updateAlertConfiguration</code>, <code>viewAlert</code>

\| [Alert actions](#alert-actions)

\| December 2025 |
\| <code>proj/*:observability-dashboard/*</code>

\| <code>addObservabilityGraphTo<br /> Dashboard</code>, <code>createObservability<br /> Dashboard</code>, <code>deleteObservability<br /> Dashboard</code>, <code>removeObservabilityGraphFrom<br /> Dashboard</code>, <code>updateObservability<br /> DashboardConfiguration</code>, <code>updateObservabilityGraph<br /> Configuration</code>, <code>updateObservabilitySettings</code>, <code>viewObservability<br /> Dashboard</code>

\| [Observability dashboard actions](#observability-dashboard-actions)

\| December 2025 |
\| <code>proj/*:env/*:metric-data-source/\*</code>

\| <code>createMetricDataSource</code>, <code>updateMetricDataSource</code>

\| [Metric data source actions](#metric-data-source-actions)

\| December 2025 |
\| <code> proj/\* </code>

\| <code>updateLifecycleSettings</code>

\| [Project actions](#project-actions)

\| November 2025 |
\| <code>proj/*:view/*</code>

\| <code>linkSegmentToView</code>, <code>unlinkSegmentFromView</code>

\| [View actions](#view-actions)

\| October 2025 |
\| <code> proj/*:metric/* </code>

\| <code>updateArchived</code>

\| [Metric actions](#metric-actions)

\| October 2025 |
\| <code> proj/*:release-policy/* </code>

\| <code>createReleasePolicy</code>, <code>deleteReleasePolicy</code>, <code>updateReleasePolicy</code>, <code>updateReleasePolicyRank</code>

\| [Release policy actions](#release-policy-actions)

\| September 2025 |
\| <code> proj/*:aiconfig/* </code>

\| <code>applyApprovalRequest</code>, <code>createApprovalRequest</code>, <code>deleteApprovalRequest</code>, <code>reviewApprovalRequest</code>, <code>updateApprovalRequest</code>

\| [AI Config actions](#ai-config-actions)

\| August 2025 |
\| <code> proj/*:ai-tool/* </code>

\| <code>createAITool</code>, <code>updateAITool</code>, <code>deleteAITool</code>

\| [AI tool actions](#ai-tool-actions)

\| August 2025 |
\| <code> proj/*:metric-group/* </code>

\| <code>createGuardrailMetricGroup</code>,<br /> <code>deleteGuardrailMetricGroup</code>,<br /> <code>updateGuardrailMetricGroup<br />Name</code>,<br /> <code>updateGuardrailMetricGroup<br />Description</code>,<br /> <code>updateGuardrailMetricGroup<br />Tags</code>,<br /> <code>updateGuardrailMetricGroup<br />Maintainer</code>,<br /> <code>updateGuardrailMetricGroup<br />Metrics</code><br /><br /> <b>Note:</b> Guardrail metric groups are no longer available. Configure release guardrails by adding individual metrics and metric groups to release policies.

\| [Release policies](/home/releases/release-policies)

\| July 2025 |
\| <code>proj/*:view/*</code>

\| <code>createView</code>, <code>deleteView</code>, <code>updateView</code>, <code>viewView</code>, <code>linkFlagToView</code>, <code>unlinkFlagFromView</code>

\| [View actions](#view-actions)

\| July 2025 |
\| <code> proj/*:metric/* </code>

\| <code>updateFilters</code>

\| [Metric actions](#metric-actions)

\| June 2025 |
\| <code> proj/*:env/*:aiconfig/\* </code>

\| <code>updateAIConfigTargeting</code>

\| [AI Config actions](#ai-config-actions)

\| June 2025 |
\| <code>proj/*:env/*:segment/\*</code>

\| <code> createSegmentExport </code>

\| [Segment actions](#segment-actions)

\| May 2025 |
\| <code>proj/*:ai-model-config/*</code>

\| <code>addAIRestrictedModel</code>, <code>deleteAIRestrictedModel</code>

\| [AI model config actions](#ai-model-config-actions)

\| April 2025 |
\| <code>acct</code>

\| <code> updatePresetBundleVersion </code>

\| [Account actions](#account-actions)

\| April 2025 |

## Actions reference

These are all the actions you can take, sorted by resource type.

When you create a policy using the [policy builder](/home/account/roles/role-create#create-policies-for-roles), actions relevant to the [resource scope](/home/account/roles/role-resources) you've selected automatically appear in the policy builder:

<Frame caption="The &#x22;Actions&#x22; and &#x22;Select actions&#x22; menus when defining a policy.">
  ![The "Actions" and "Select actions" menus when defining a policy.](https://files.buildwithfern.com/https://launchdarkly.docs.buildwithfern.com/docs/f8147aa70d20f7bb37d0ee3f5198b918d230c2e44cb7ae1fd7839d907c571e80/assets/images/auto/custom-roles-policy-builder-actions.auto.png)
</Frame>

When you create a policy using the [advanced editor](/home/account/roles/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*`.

## Account actions

<Accordion title="Expand Account actions">
  `acct` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Account resource" theme={null}
          acct
    ```
  </CodeGroup>

  This table explains the available account actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAnnouncement </code>

  \| Create an announcement for the account. |
  \| <code> createOAuthClient </code>

  \| Create a new OAuth client for the account. |
  \| <code> createSamlConfig </code>

  \| Create a new SAML configuration for the account. |
  \| <code> createSamlEncryptionCertificate </code>

  \| Create a new SAML encryption certificate for the account. |
  \| <code> createScimConfig </code>

  \| Create a new SCIM configuration for the account. |
  \| <code> deleteAccount </code>

  \| Delete the account. |
  \| <code> deleteAccountToken </code>

  \| Delete account tokens for the [LaunchDarkly REST API](/api#authentication). This is a legacy action and may have inconsistent performance. Instead, we recommend you use <code>deleteAccessToken</code>. |
  \| <code> deleteAnnouncement </code>

  \| Delete an announcement for the account. |
  \| <code> deleteOAuthClient </code>

  \| Delete an OAuth client for the account. |
  \| <code> deleteSamlConfig </code>

  \| Delete the SAML configuration for the account. |
  \| <code> deleteScimConfig </code>

  \| Delete the SCIM configuration for the account. |
  \| <code> deleteSubscription </code>

  \| Cancel the account plan. |
  \| <code> disableIdPManagingTeams </code>

  \| Disable team sync with SCIM. |
  \| <code> enableIdPManagingTeams </code>

  \| Enable team sync with SCIM. |
  \| <code> getPaymentCard </code>

  \| Get the credit card for the account. |
  \| <code> revokeSessions </code>

  \| Revoke sessions issued before a specified date. |
  \| <code> updateAccountToken </code>

  \| Reset account tokens for the [LaunchDarkly REST API](/api#authentication). |
  \| <code> updateAnnouncement </code>

  \| Update an announcement for the account. |
  \| <code> updateBillingContact </code>

  \| Update the billing contact for the account. |
  \| <code> updateEnableAccountImpersonation </code>

  \| Change whether LaunchDarkly support can impersonate the account as a read-only member. |
  \| <code> updateIsGeneralGenAiEnabled </code>

  \| Change whether LaunchDarkly can use generative AI for general product features on the account. |
  \| <code> updateIsSupportGenAiEnabled </code>

  \| Change whether support-driven automations can use generative AI for the account. |
  \| <code> updateOAuthClient </code>

  \| Update an OAuth client for the account. |
  \| <code> updateOrganization </code>

  \| Update the organization name. |
  \| <code> updatePaymentCard </code>

  \| Change the credit card for the account. |
  \| <code> updatePresetBundleVersion </code>

  \| Change the version of the predefined role bundle. This updates all [preset roles](/home/getting-started/vocabulary#preset-roles) to the specified version. |
  \| <code> updateRequireMfa </code>

  \| Change whether multi-factor authentication (MFA) is required for all members on the account. |
  \| <code> updateSamlDecryptionEnabled </code>

  \| Enable or disable decryption for incoming SAML assertions for the account. |
  \| <code> updateSamlDefaultRole </code>

  \| Update the default role given to members when SAML doesn't specify one. |
  \| <code> updateSamlEnabled </code>

  \| Enable or disable SAML SSO for the account. |
  \| <code> updateSamlLogoutUrl </code>

  \| Update the SAML logout URL for the account. |
  \| <code> updateSamlRequestSigningEnabled </code>

  \| Enable or disable signing outgoing SAML requests. |
  \| <code> updateSamlRequireSso </code>

  \| Change whether SSO must be used for authentication. |
  \| <code> updateSamlSsoUrl </code>

  \| Update the SAML SSO URL for the account. |
  \| <code> updateSamlX509Certificate </code>

  \| Update the SAML X509 certificate for the account. |
  \| <code> updateSamlX509KeystoreId </code>

  \| Update the SAML X509 identifier for the account. |
  \| <code> updateSessionDuration </code>

  \| Change the duration of sessions. |
  \| <code> updateSessionRefresh </code>

  \| Change whether sessions are refreshed automatically. |
  \| <code> updateSubscription </code>

  \| Change the pricing plan for the account. |

  ### Account ownership actions

  This table explains the available account ownership actions:

  \| <code> updateAccountOwner </code>

  | Update the account owner. |
  | - |

  \| --- |
</Accordion>

## Agent graphs actions

<Accordion title="Expand agent graphs actions">
  `agent-graph` is a child resource of a project. A code sample is below:

  <CodeGroup>
    ```text title="Agent graphs resource" theme={null}
          proj/*:agent-graph/*
    ```
  </CodeGroup>

  This table explains the available Agent graphs actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAgentGraph </code>

  \| Create a new agent graph. |
  \| <code> updateAgentGraph </code>

  \| Modify an agent graph. |
  \| <code> deleteAgentGraph </code>

  \| Delete an agent graph. |
</Accordion>

## AI Config actions

<Accordion title="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.

  <CodeGroup>
    ```text title="AI Config resource" theme={null}
          proj/*:env/*:aiconfig/*
    ```
  </CodeGroup>

  This table explains the available AI Config actions related to settings and targeting changes:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAIConfig </code>

  \| Create a new AI Config. |
  \| <code> deleteAIConfig </code>

  \| Delete an AI Config. |
  \| <code> deleteAIConfigVariation </code>

  \| Delete an AI Config variation. |
  \| <code> updateAIConfig </code>

  \| Update an AI Config. |
  \| <code> updateAIConfigTargeting </code>

  \| Update an AI Config's targeting rules in an environment. |
  \| <code> updateAIConfigVariation </code>

  \| Update an AI Config variation. |

  This table explains AI Config actions related to collaboration:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> applyApprovalRequest </code>

  \| Apply the requested changes after the request is approved. |
  \| <code> createApprovalRequest </code>

  \| Create an approval request. |
  \| <code> deleteApprovalRequest </code>

  \| Delete an approval request. |
  \| <code> reviewApprovalRequest </code>

  \| Review an approval request. |
  \| <code> updateApprovalRequest </code>

  \| Update an approval request. |
</Accordion>

## AI tool actions

<Accordion title="Expand AI tool actions">
  `ai-tool` is a child resource of a project. A code sample is below:

  <CodeGroup>
    ```text title="AI tool resource" theme={null}
          proj/*:ai-tool/*
    ```
  </CodeGroup>

  This table explains the available AI tool actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAITool </code>

  \| Create a new AI tool. |
  \| <code> updateAITool </code>

  \| Modify an existing AI tool. |
  \| <code> deleteAITool </code>

  \| Delete an AI tool. |
</Accordion>

## AI model config actions

<Accordion title="Expand AI model config actions">
  `ai-model-config` is a child resource of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="AI model config resource" theme={null}
          proj/*:ai-model-config/*
    ```
  </CodeGroup>

  This table explains the available AI model config actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> addAIRestrictedModel </code>

  \| Add an AI model to the restricted list. |
  \| <code> createAIModelConfig </code>

  \| Create a new AI model config. |
  \| <code> deleteAIModelConfig </code>

  \| Delete an AI model config. |
  \| <code> deleteAIRestrictedModel </code>

  \| Delete an AI model from the restricted list. |
</Accordion>

## AI evaluation actions

<Accordion title="Expand AI evaluation actions">
  `ai-evaluation` is a child resource of a project. A code sample is below:

  <CodeGroup>
    ```text title="AI evaluation resource" theme={null}
          proj/*:ai-evaluation/*
    ```
  </CodeGroup>

  This table explains the available AI evaluation actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAIEvaluation </code>

  \| Create a new AI evaluation or start a new evaluation run. |
  \| <code> deleteAIEvaluation </code>

  \| Delete an AI evaluation or evaluation run. |
  \| <code> updateAIEvaluation </code>

  \| Update an AI evaluation. |
</Accordion>

## Alert actions

<Accordion title="Expand Alert actions">
  `alert` is a child of a project. Alerts are related to the [observability feature](/home/observability).

  A code sample is below:

  <CodeGroup>
    ```text title="Alert resource" theme={null}
          proj/*:alert/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAlert </code>

  \| Create an alert. |
  \| <code> deleteAlert </code>

  \| Delete an alert. |
  \| <code> updateAlertConfiguration </code>

  \| Update an alert configuration. |
  \| <code> updateAlertOn </code>

  \| Turn an alert on or off. |
  \| <code> viewAlert </code>

  \| View an alert. |

  To learn more, read [Alerts](/home/observability/alerts).
</Accordion>

## Application actions

<Accordion title="Expand Application actions">
  `application` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Application resource" theme={null}
          application/*
    ```
  </CodeGroup>

  This table explains the available application actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createApplication </code>

  \| Create a new application. |
  \| <code> deleteApplication </code>

  \| Delete an application. |
  \| <code> updateApplicationDescription </code>

  \| Change an application's description. |
  \| <code> updateApplicationKind </code>

  \| Change an application's kind. |
  \| <code> updateApplicationMaintainer </code>

  \| Change an application's maintainer. |
  \| <code> updateApplicationName </code>

  \| Change an application's name. |
</Accordion>

## Application version actions

<Accordion title="Expand Application version actions">
  `version` is a child resource of applications. A code sample is below:

  <CodeGroup>
    ```text title="Application version resource" theme={null}
          application/*:version/*
    ```
  </CodeGroup>

  This table explains the available application version actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createApplicationVersion </code>

  \| Create a new application version. |
  \| <code> deleteApplicationVersion </code>

  \| Delete an application version. |
  \| <code> updateApplicationVersionName </code>

  \| Change the application version name. |
  \| <code> updateApplicationVersionSupport </code>

  \| Change whether an application version is supported or not. |
</Accordion>

## Code reference actions

<Accordion title="Expand Code reference actions">
  `code-reference-repository` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Code references resource" theme={null}
          code-reference-repository/*
    ```
  </CodeGroup>

  To learn more, read [Code references](/home/flags/code-references).

  This table explains the available code reference actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createCodeRefsRepository </code>

  \| Connect a Git repository. |
  \| <code> deleteCodeRefsRepository </code>

  \| Delete a Git repository connection. |
  \| <code> updateCodeRefsRepositoryBranches </code>

  \| Update the stored branch data for a Git repository connection. |
  \| <code> updateCodeRefsRepositoryConfiguration </code>

  \| Update a Git repository connection configuration. |
  \| <code> updateCodeRefsRepositoryName </code>

  \| Update a Git repository connection name. |
  \| <code> updateCodeRefsRepositoryOn </code>

  \| Flip the on/off status of a Git repository connection. |
</Accordion>

## Context kind actions

<Accordion title="Expand Context kind actions">
  `context-kind` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="Context resource" theme={null}
          proj/*:context-kind/*
    ```
  </CodeGroup>

  To learn more, read [Context kinds](/home/flags/context-kinds).

  This table explains the available context kind actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createContextKind </code>

  \| Create a context kind. |
  \| <code> updateContextKind </code>

  \| Update a context kind. |
  \| <code> updateAvailabilityForExperiments </code>

  \| Update whether a context kind is available for experiments and guarded rollouts, and whether that context kind is the project's default for experiments and guarded rollouts. |
</Accordion>

## Destination actions

<Accordion title="Expand Destination actions">
  `destination` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Destination resource" theme={null}
          proj/*:env/*:destination/*
    ```
  </CodeGroup>

  To learn more, read [Data Export](/integrations/data-export).

  This table explains the available Data Export destination actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createDestination </code>

  \| Create a new Data Export destination. |
  \| <code> deleteDestination </code>

  \| Delete a Data Export destination. |
  \| <code> updateConfiguration </code>

  \| Change a Data Export destination. |
  \| <code> updateName </code>

  \| Change the name of a Data Export destination. |
  \| <code> updateOn </code>

  \| Flip the on/off status of a Data Export destination. |
</Accordion>

## Domain verification actions

<Accordion title="Expand Domain verification actions">
  `domain-verification` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Domain verification resource" theme={null}
          domain-verification/*
    ```
  </CodeGroup>

  To learn more, read [Domain verification](/home/account/domain-verification).

  This table explains the available domain verification actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createDomainVerification </code>

  \| Create a new domain verification. |
  \| <code> deleteDomainVerification </code>

  \| Remove a domain verification. |
  \| <code> updateDomainVerification </code>

  \| Update a domain verification. |
</Accordion>

## Environment actions

<Accordion title="Expand Environment actions">
  `env` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="Environment resource" theme={null}
          proj/*:env/*
    ```
  </CodeGroup>

  To learn more, read [Environments](/home/account/environment).

  This table explains the available environment actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createEnvironment </code>

  \| Create a new environment. |
  \| <code> deleteEnvironment </code>

  \| Delete an existing environment. |
  \| <code> deleteContextInstance </code>

  \| Delete context instances. |
  \| <code> importEventData </code>

  \| Import event data using the API for [Importing metric events](/home/metrics/import-events). |
  \| <code> updateApiKey </code>

  \| Reset the SDK key for an environment. |
  \| <code> updateApprovalSettings </code>

  \| Configure the approval settings for an environment. |
  \| <code> updateColor </code>

  \| Change the color swatch for an environment. |
  \| <code> updateConfirmChanges </code>

  \| Require environment confirmation for changes to flags and segments. |
  \| <code> updateCritical </code>

  \| Change whether the environment is considered critical. |
  \| <code> updateDefaultTrackEvents </code>

  \| Turn on sending detailed information for new flags by default. |
  \| <code> updateMobileKey </code>

  \| Reset the mobile key for an environment. |
  \| <code> updateName </code>

  \| Change the name of an environment. |
  \| <code> updateRequireComments </code>

  \| Require comments for changes to flags and segments. |
  \| <code> updateSecureMode </code>

  \| Turn secure mode on or off for an environment. |
  \| <code> updateTags </code>

  \| Update tags associated with an environment. |
  \| <code> updateTtl </code>

  \| Change the TTL for an environment. |
  \| <code> viewSdkKey </code>

  \| View the server-side SDK key. All custom roles can take this action by default. If set to <code>deny</code>, anyone impacted by this policy can neither view nor reset SDK keys. |

  <Note title="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.
  </Note>
</Accordion>

## Error actions

<Accordion title="Expand Error actions">
  `error` is a child of a project. Errors are related to the [observability feature](/home/observability).

  A code sample is below:

  <CodeGroup>
    ```text title="Error resource" theme={null}
          proj/*:error/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> updateErrorStatus </code>

  \| Update an error's status. |
  \| <code> viewError </code>

  \| View an error. |

  To learn more, read [Error monitoring](/home/observability/errors).
</Accordion>

## Experiment actions

<Accordion title="Expand Experiment actions">
  `experiment` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Experiment resource" theme={null}
          proj/*:env/*:experiment/*
    ```
  </CodeGroup>

  To learn more, read [Experimentation](/home/experimentation).

  This table explains the available experiment actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createExperiment </code>

  \| Create an experiment or multi-armed bandit. |
  \| <code> updateExperiment </code>

  \| Start, stop, or edit an existing experiment or multi-armed bandit. |
  \| <code> updateExperimentArchived </code>

  \| Archive an experiment or multi-armed bandit. |
</Accordion>

## Feature flag actions

<Accordion title="Expand Feature flag actions">
  `flag` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Flag resource" theme={null}
          proj/*:env/*:flag/*
    ```
  </CodeGroup>

  To learn more, read [Creating new flags](/home/flags/new).

  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:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> stopMeasuredRolloutOnFlagFallthrough </code>

  \| Stop a guarded rollout on a flag's default rule. |
  \| <code> stopMeasuredRolloutOnFlagRule </code>

  \| Stop a guarded rollout on a flag's custom rule. |
  \| <code> updateExpiringTargets </code>

  \| Change a flag's expiring individual context targeting rules. |
  \| <code> updateFallthrough </code>

  \| Update the default rule, also called the "fallthrough" rule. |
  \| <code> updateFallthroughWithMeasuredRollout </code>

  \| Start a guarded rollout on a flag's default rule. |
  \| <code> updateFeatureWorkflows </code>

  \| Change a flag's release management workflows. |
  \| <code> updateMeasuredRolloutConfiguration </code>

  \| Attach metrics to a flag for use with guarded rollouts. |
  \| <code> updateOffVariation </code>

  \| Update the variation returned when flag is toggled off. |
  \| <code> updateOn </code>

  \| Toggle a flag's targeting on or off. |
  \| <code> updatePrerequisites </code>

  \| Update flag prerequisites. |
  \| <code> updateRules </code>

  \| Update custom targeting rules. |
  \| <code> updateRulesWithMeasuredRollout </code>

  \| Start a guarded rollout on a flag's custom rule. |
  \| <code> updateScheduledChanges </code>

  \| Create, edit, and delete the scheduled updates for a flag. |
  \| <code> updateTargets </code>

  \| Update individual context targeting rules. |

  This table explains feature flag actions related to flag settings. Each of these actions affects all environments in a project:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> addReleasePipeline </code>

  \| Add a flag to a release pipeline. |
  \| <code> createFlag </code>

  \| Create a flag. |
  \| <code> deleteFlag </code>

  \| Delete a flag. |
  \| <code> removeReleasePipeline </code>

  \| Remove a flag from a release pipeline. |
  \| <code> replaceReleasePipeline </code>

  \| Move a flag to a different release pipeline. |
  \| <code> updateClientSideFlagAvailability </code>

  \| Change whether the flag is available to client-side SDKs. |
  \| <code> updateDescription </code>

  \| Change the description of a flag. |
  \| <code> updateDeprecated </code>

  \| Change whether a flag is deprecated. |
  \| <code> updateFlagCodeReferences </code>

  \| Update code references associated with the flag. |
  \| <code> updateFlagConfigMigrationSettings </code>

  \| Update a feature flag's consistency check ratio. |
  \| <code> updateFlagCustomProperties </code>

  \| Update custom properties attached to a flag. |
  \| <code> updateFlagDefaultVariations </code>

  \| Change the default flag variations used by newly-created environments for a flag. |
  \| <code> updateFlagVariations </code>

  \| Change the flag's variations. |
  \| <code> updateGlobalArchived </code>

  \| Change whether a flag is archived. |
  \| <code> updateIncludeInSnippet </code>

  \| Change whether the flag is available to front-end code with the [JavaScript SDK](/sdk/client-side/javascript). |
  \| <code> updateName </code>

  \| Change the name of a flag. |
  \| <code> updateTags </code>

  \| Update tags associated with a flag. |
  \| <code> updateTemporary </code>

  \| Mark a flag temporary or permanent. |

  This table explains feature flag actions related to environment-specific settings:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createTriggers </code>

  \| Create a new trigger. |
  \| <code> deleteTriggers </code>

  \| Delete a trigger. |
  \| <code> updateFlagFallthroughTrackEvents </code>

  \| Change whether to send detailed event information when the fallthrough variation is selected. |
  \| <code> updateFlagSalt </code>

  \| Update a flag's salt. |
  \| <code> updateTrackEvents </code>

  \| Change whether to send detailed event information for a flag in a given environment. |
  \| <code> updateTriggers </code>

  \| Update an existing trigger. |

  This table explains feature flag actions related to collaboration:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> applyApprovalRequest </code>

  \| Apply the requested changes after the request is approved. |
  \| <code> bypassRequiredApproval </code>

  \| Bypass required approvals for flags in the environment. (You cannot bypass required approvals for segments.) |
  \| <code> createApprovalRequest </code>

  \| Create an approval request. |
  \| <code> createFlagLink </code>

  \| Create a flag link. |
  \| <code> deleteApprovalRequest </code>

  \| Delete an approval request. |
  \| <code> deleteFlagLink </code>

  \| Delete a flag link. This affects all environments in a project. |
  \| <code> manageFlagFollowers </code>

  \| Manage the list of members who receive flag change notifications. |
  \| <code> reviewApprovalRequest </code>

  \| Review an approval request. |
  \| <code> updateApprovalRequest </code>

  \| Update an approval request. |
  \| <code> updateMaintainer </code>

  \| Update the flag maintainer. This affects all environments in a project. |
  \| <code> updateFlagLink </code>

  \| Update a flag link. This affects all environments in a project. |

  This table explains feature flag actions related to other flag changes:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> cloneFlag </code>

  \| Create a new flag with settings based on an existing flag. To clone a flag, members need to have the <code>cloneFlag</code> permission on the source flag, as well as the <code>createFlag</code> permission for the new flag. This affects all environments in a project. |
  \| <code> copyFlagConfigFrom </code>

  \| Copy settings from a flag. |
  \| <code> copyFlagConfigTo </code>

  \| Copy settings to a flag. |
  \| <code> updateExpiringTargets </code>

  \| Change a flag's expiring individual context targeting rules. |
  \| <code> updateFlagRuleDescription </code>

  \| Change the description of a flag's custom targeting rules. |
  \| <code> updateReleasePhaseStatus </code>

  \| Update a release phase status. |
</Accordion>

## Holdout actions

<Accordion title="Expand Holdout actions">
  `holdout` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Holdout resource" theme={null}
          proj/*:env/*:holdout/*
    ```
  </CodeGroup>

  To learn more, read [Holdouts](/home/holdouts).

  This table explains the available holdout actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> addExperimentToHoldout </code>

  \| Add an experiment to a holdout. |
  \| <code> createHoldout </code>

  \| Create a holdout. |
  \| <code> removeExperimentFromHoldout </code>

  \| Remove an experiment from a holdout. |
  \| <code> updateHoldoutDescription </code>

  \| Update the description of a holdout. |
  \| <code> updateHoldoutMethodology </code>

  \| Update the statistical method for a holdout. |
  \| <code> updateHoldoutAmount </code>

  \| Update the holdout amount for a holdout. |
  \| <code> updateHoldoutName </code>

  \| Update the name of a holdout. |
  \| <code> updateHoldoutStatus </code>

  \| Update the status of a holdout. |
  \| <code> updateHoldoutRandomizationUnit </code>

  \| Update the randomization unit of a holdout. |
</Accordion>

## Integration actions

<Accordion title="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:

  <CodeGroup>
    ```text title="Integration resource" theme={null}
          integration/*
    ```
  </CodeGroup>

  To learn more, read [Integrations](/integrations).

  This table explains the available integration actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createIntegration </code>

  \| Create and configure new third-party integrations. |
  \| <code> deleteIntegration </code>

  \| Delete existing third-party integrations. |
  \| <code> updateConfiguration </code>

  \| Modify existing third-party integration configurations. |
  \| <code> updateName </code>

  \| Change the name of third-party integration configurations. |
  \| <code> updateOn </code>

  \| Enable and disable existing third-party integrations. |
  \| <code> validateConnection </code>

  \| Validate the third-party connection. |
</Accordion>

## Layer actions

<Accordion title="Expand Layer actions">
  `layer` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="Layer resource" theme={null}
          proj/*:layer/*
    ```
  </CodeGroup>

  To learn more, read [Mutually exclusive experiments](/home/experimentation/mutually-exclusive).

  This table explains the available layer actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createLayer </code>

  \| Create a layer. |
  \| <code> updateLayer </code>

  \| Update a layer's name or description. |
  \| <code> updateLayerConfiguration </code>

  \| Update a layer's audience allocation. |
</Accordion>

## Log actions

<Accordion title="Expand Log actions">
  `log` is a child of a project. Logs are related to the [observability feature](/home/observability).

  A code sample is below:

  <CodeGroup>
    ```text title="Log resource" theme={null}
          proj/*:log/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> viewLog </code>

  \| View a log. |

  To learn more, read [Logs](/home/observability/logs).
</Accordion>

## Member actions

<Accordion title="Expand Member actions">
  `member` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Member resource" theme={null}
          member/*
    ```
  </CodeGroup>

  To learn more, read [Members](/home/account/members).

  This table explains the available member actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> approveDomainMatchedMember </code>

  \| Approve a join request from a domain-matched member. To learn more, read [Enabling domain matching](/home/account/org-settings#enable-domain-matching) . |
  \| <code> createMember </code>

  \| Add a new account member to an account. |
  \| <code> deleteMember </code>

  \| Remove an account member from an account. |
  \| <code> sendMfaRecoveryCode </code>

  \| Send an account member their MFA recovery code. |
  \| <code> sendMfaRequest </code>

  \| Send an account member a request to enable MFA. |
  \| <code> updateCustomRole </code>

  \| Update an account member's custom roles. |
  \| <code> updateMemberRoleAttributes </code>

  \| Update a team member's role attributes. Role attributes are managed within LaunchDarkly and can be updated through the UI or REST API. They cannot be passed through SAML assertions for single sign-on. For SAML-based SSO, LaunchDarkly supports mapping only the <code>role</code> , <code>customRole</code> , and <code>teamKey</code> attributes. |
  \| <code> updateRole </code>

  \| Update an account member's role. |
</Accordion>

## Metric actions

<Accordion title="Expand Metric actions">
  `metric` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="Metric resource" theme={null}
          proj/*:metric/*
    ```
  </CodeGroup>

  To learn more, read [Metrics](/home/metrics).

  This table explains the available metric actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createMetric </code>

  \| Create a new metric. |
  \| <code> deleteMetric </code>

  \| Delete a metric that has been archived and is no longer in use. |
  \| <code> updateAnalysisType </code>

  \| Change a metric's analysis type. |
  \| <code> updateArchived </code>

  \| Archive a metric or restore an archived metric. |
  \| <code> updateDescription </code>

  \| Change the description of a metric. |
  \| <code> updateEventDefault </code>

  \| Change a metric's handling for units without events. |
  \| <code> updateEventKey </code>

  \| Change the event key for a custom metric. |
  \| <code> updateFilters </code>

  \| Update the filters for a custom metric. |
  \| <code> updateMaintainer </code>

  \| Change the metric's maintainer. |
  \| <code> updateName </code>

  \| Change the name of a metric. |
  \| <code> updateNumeric </code>

  \| Mark a custom metric as numeric or non-numeric. |
  \| <code> updateNumericSuccess </code>

  \| Update the success criteria for a numeric custom metric. |
  \| <code> updateNumericUnit </code>

  \| Update the unit displayed in results for a numeric custom metric. |
  \| <code> updateOn </code>

  \| Mark a metric as active or inactive. |
  \| <code> updateRandomizationUnits </code>

  \| Change the randomization units for a metric. |
  \| <code> updateSelector </code>

  \| Update the CSS selector for a click conversion metric. |
  \| <code> updateTags </code>

  \| Change the tags associated with a metric. |
  \| <code> updateUnitAggregationType </code>

  \| Change a metric's aggregation method. |
  \| <code> updateUrls </code>

  \| Update the URLs for a click conversion or page view conversion metric. |
</Accordion>

## Metric data source actions

<Accordion title="Expand Metric data source actions">
  `metric-data-source` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Metric data source resource" theme={null}
          proj/*:env/*:metric-data-source/*
    ```
  </CodeGroup>

  To learn more, read [Metric data sources](/home/warehouse-native/metric-data-sources).

  This table explains available metric data source actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createMetricDataSource </code>

  \| Create a metric data source. |
  \| <code> updateMetricDataSource </code>

  \| Update a metric data source. |
</Accordion>

## Metric group actions

<Accordion title="Expand Metric group actions">
  `metric-group` is a child of a project.

  A code sample is below:

  <CodeGroup>
    ```text title="Metric group resource" theme={null}
          proj/*:metric-group/*
    ```
  </CodeGroup>

  To learn more, read [Metric groups](/home/metrics/metric-groups).

  This table explains the available metric group actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createMetricGroup </code>

  \| Create a metric group. |
  \| <code> deleteMetricGroup </code>

  \| Delete a metric group. |
  \| <code> updateMetricGroupName </code>

  \| Change a metric group's name. |
  \| <code> updateMetricGroupDescription </code>

  \| Change a metric group's description. |
  \| <code> updateMetricGroupTags </code>

  \| Change the tags associated with a metric group. |
  \| <code> updateMetricGroupMaintainer </code>

  \| Change a metric group's maintainer. |
  \| <code> updateMetricGroupMetrics </code>

  \| Change the metrics in a metric group. |

  ### Guardrail metrics group actions

  <Note title="Guardrail metric groups are no longer available">
    Guardrail metric groups are no longer available. Configure release guardrails by adding individual metrics and metric groups to [release policies](/home/releases/release-policies).
  </Note>

  This table explains the available guardrail metrics group actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createGuardrailMetricGroup </code>

  \| Create a new guardrail metrics group. |
  \| <code> deleteGuardrailMetricGroup </code>

  \| Delete a guardrail metrics group. |
  \| <code> updateGuardrailMetricGroupName </code>

  \| Change a guardrail metrics group's name. |
  \| <code> updateGuardrailMetricGroupDescription </code>

  \| Change a guardrail metrics group's description. |
  \| <code> updateGuardrailMetricGroupTags </code>

  \| Change the tags associated with a guardrail metrics group. |
  \| <code> updateGuardrailMetricGroupMaintainer </code>

  \| Change a guardrail metrics group's maintainer. |
  \| <code> updateGuardrailMetricGroupMetrics </code>

  \| Change the metrics in a guardrail metrics group. |
</Accordion>

## Notification subscription actions

<Accordion title="Expand Notification subscription actions">
  `notification-subscription` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Notification subscription resource" theme={null}
          proj/*:env/*:notification-subscription/*
    ```
  </CodeGroup>

  To learn more, read [Update your notification settings](/home/account/profile#update-your-notification-settings).

  This table explains the available notification subscription actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createNotificationSubscription </code>

  \| Create a feedback notification subscription. |
  \| <code> deleteNotificationSubscription </code>

  \| Delete a feedback notification subscription. |
</Accordion>

## Observability dashboard actions

<Accordion title="Expand Observability dashboard actions">
  `observability-dashboard` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="Observability dashboard resource" theme={null}
          proj/*:observability-dashboard/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> addObservabilityGraphToDashboard </code>

  \| Add a graph to an observability dashboard. |
  \| <code> createObservabilityDashboard </code>

  \| Create an observability dashboard. |
  \| <code> deleteObservabilityDashboard </code>

  \| Delete an observability dashboard. |
  \| <code> removeObservabilityGraphFromDashboard </code>

  \| Remove a graph from an observability dashboard. |
  \| <code> updateObservabilityDashboardConfiguration </code>

  \| Update an observability dashboard's configuration. |
  \| <code> updateObservabilityGraphConfiguration </code>

  \| Update configuration for a graph on an observability dashboard. |
  \| <code> updateObservabilitySettings </code>

  \| Update an observability dashboard's settings. |
  \| <code> viewObservabilityDashboard </code>

  \| View an observability dashboard. |

  To learn more, read [Dashboards](/home/observability/dashboards).
</Accordion>

## Pending request actions

<Accordion title="Expand Pending request actions">
  `pending-request` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Pending requests resource" theme={null}
          pending-request/*
    ```
  </CodeGroup>

  To learn more, read [Accept pending requests](/home/account/members#accept-pending-requests).

  This table explains the available pending request actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> updatePendingRequest </code>

  \| Update a pending request. Accept or decline requests for new members to join your account. |
</Accordion>

## Personal access token actions

<Accordion title="Expand Personal access token actions">
  `token` is a child of a member. A code sample is below:

  <CodeGroup>
    ```text title="Token resource" theme={null}
          member/*:token/*
    ```
  </CodeGroup>

  To learn more, read [API access tokens](/home/account/api).

  This table explains the available personal access token actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAccessToken </code>

  \| Create a personal access token. All custom roles can take this action by default. |
  \| <code> deleteAccessToken </code>

  \| Delete a personal access token. |
  \| <code> resetAccessToken </code>

  \| Reset a personal access token's secret key. |
  \| <code> updateAccessTokenDescription </code>

  \| Change the description of a personal access token. |
  \| <code> updateAccessTokenName </code>

  \| Change the name of a personal access token. |
  \| <code> updateAccessTokenPolicy </code>

  \| Change the policy filter of a personal access token. |
</Accordion>

## Project actions

<Accordion title="Expand Project actions">
  `proj` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Project resource" theme={null}
          proj/*
    ```
  </CodeGroup>

  To learn more, read [Projects](/home/account/project).

  This table explains the available project actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createProject </code>

  \| Create a new project. |
  \| <code> deleteProject </code>

  \| Delete a project. |
  \| <code> updateDefaultClientSideAvailability </code>

  \| Change whether new flags are made available to client-side SDKs by default. Formerly <code>updateIncludeInSnippetByDefault</code> . |
  \| <code> updateDefaultReleasePipeline </code>

  \| Change the default release pipeline for a project. |
  \| <code> updateLifecycleSettings </code>

  \| Update the flag lifecycle settings for a project. |
  \| <code> updateObservabilitySettings </code>

  \| Update the observability settings for a project. |
  \| <code> updateProjectFlagDefaults </code>

  \| Update the default flag settings for a project. |
  \| <code> updateProjectName </code>

  \| Rename a project. |
  \| <code> updateTags </code>

  \| Update tags associated with a project. |
  \| <code> viewProject </code>

  \| View a project. For roles created after October 2024, and for roles with this action set to <code>deny</code>, anyone impacted by the policy can neither view nor modify a project. |

  <Note title="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](/home/account/roles/project-roles) and [Create private projects with custom roles](/home/account/private-projects).
  </Note>
</Accordion>

## Relay Proxy configuration actions

<Accordion title="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:

  <CodeGroup>
    ```text title="Relay Proxy configuration resource" theme={null}
          relay-proxy-config/*
    ```
  </CodeGroup>

  To learn more, read [Automatic configuration](/sdk/relay-proxy/automatic-configuration).

  This table explains the available Relay Proxy automatic configuration actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createRelayAutoConfiguration </code>

  \| Create a Relay Proxy with automatic configuration enabled. |
  \| <code> deleteRelayAutoConfiguration </code>

  \| Delete the Relay Proxy with automatic configuration enabled. |
  \| <code> resetRelayAutoConfiguration </code>

  \| Reset the configuration of the Relay Proxy with automatic configuration enabled. |
  \| <code> updateRelayAutoConfigurationName </code>

  \| Change the Relay Proxy with automatic configuration's name. |
  \| <code> updateRelayAutoConfigurationPolicy </code>

  \| Change the policies associated with the Relay Proxy with automatic configuration. |
</Accordion>

## Release pipeline actions

<Accordion title="Expand Release pipeline actions">
  `release-pipeline` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="Release pipeline resource" theme={null}
          proj/*:release-pipeline/*
    ```
  </CodeGroup>

  This table explains the available release pipeline actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createReleasePipeline </code>

  \| Create a new release pipeline. |
  \| <code> deleteReleasePipeline </code>

  \| Delete a release pipeline. |
  \| <code> updateReleasePipelineDescription </code>

  \| Change the description of a release pipeline. |
  \| <code> updateReleasePipelineName </code>

  \| Change the name of a release pipeline. |
  \| <code> updateReleasePipelinePhase </code>

  \| Update release pipeline phase and audience values. |
  \| <code> updateReleasePipelinePhaseName </code>

  \| Change the name of one phase in a release pipeline. |
  \| <code> updateReleasePipelineTags </code>

  \| Change the tags on a release pipeline. |
</Accordion>

## Release policy actions

<Accordion title="Expand release policy actions">
  `release-policy` is a child of a project.

  <CodeGroup>
    ```text title="Release policy resource" theme={null}
          proj/*:release-policy/*
    ```
  </CodeGroup>

  To learn more, read [Release policies](/home/releases/release-policies).

  This table explains the available release policy actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createReleasePolicy </code>

  \| Create a new release policy. |
  \| <code> deleteReleasePolicy </code>

  \| Delete a release policy. |
  \| <code> updateReleasePolicy </code>

  \| Update a release policy. |
  \| <code> updateReleasePolicyRank </code>

  \| Update a release policy's priority. |
</Accordion>

## Role actions

<Accordion title="Expand Role actions">
  `role` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Role resource" theme={null}
          role/*
    ```
  </CodeGroup>

  To learn more, read [Roles](/home/account/roles).

  This table explains the available role actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createRole </code>

  \| Create new custom roles. |
  \| <code> deleteRole </code>

  \| Delete a custom role. |
  \| <code> updateBasePermissions </code>

  \| Update a custom role's base permissions. This only applies to roles created before October

  2024. |
        \| <code> updateDescription </code>

  \| Update a custom role's description. |
  \| <code> updateMembers </code>

  \| Add or remove members from a custom role. Equivalent to <code>updateCustomRole</code> on account members. |
  \| <code> updateName </code>

  \| Update a custom role's name. |
  \| <code> updatePolicy </code>

  \| Update a custom role's policy. |
  \| <code> updateTokens </code>

  \| Change the policy filter of a personal access token. Equivalent to <code>updateAccessTokenPolicy</code> on personal access tokens. |
</Accordion>

## Segment actions

<Accordion title="Expand Segment actions">
  `segment` is a child of both a project and an environment. A code sample is below:

  <CodeGroup>
    ```text title="Segment resource" theme={null}
          proj/*:env/*:segment/*
    ```
  </CodeGroup>

  To learn more, read [Segments](/home/flags/segments).

  This table explains the available segments actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> applyApprovalRequest </code>

  \| Apply an approved approval request for a segment. |
  \| <code> bypassRequiredSegmentApproval </code>

  \| Bypass required approval for segment changes in the environment. |
  \| <code> createApprovalRequest </code>

  \| Request approval on changes for a segment. |
  \| <code> createSegment </code>

  \| Create new segments. |
  \| <code> createSegmentExport </code>

  \| Export a list-based segment. |
  \| <code> deleteApprovalRequest </code>

  \| Delete an approval request for a segment. |
  \| <code> deleteSegment </code>

  \| Delete segments. |
  \| <code> reviewApprovalRequest </code>

  \| Review changes on an approval request for a segment. |
  \| <code> updateApprovalRequest </code>

  \| Update an approval request for a segment. |
  \| <code> updateDescription </code>

  \| Update a segment's description. |
  \| <code> updateExcluded </code>

  \| Change a segment's excluded contexts. |
  \| <code> updateExpiringTargets </code>

  \| Change a segment's expiring individual context targeting rules. |
  \| <code> updateIncluded </code>

  \| Change a segment's included contexts. |
  \| <code> updateName </code>

  \| Change the name of a segment. |
  \| <code> updateRules </code>

  \| Change a segment's custom targeting rules. |
  \| <code> updateScheduledChanges </code>

  \| Change the scheduled updates on a segment. |
  \| <code> updateTags </code>

  \| Change the tags associated with a segment. |
</Accordion>

## Service access token actions

<Accordion title="Expand Service access token actions">
  `service-token` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Service token resource" theme={null}
          service-token/*
    ```
  </CodeGroup>

  To learn more, read [API access tokens](/home/account/api).

  This table explains the available service access token actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createAccessToken </code>

  \| Create a service access token. All custom roles can take this action by default. |
  \| <code> deleteAccessToken </code>

  \| Delete a service access token. |
  \| <code> resetAccessToken </code>

  \| Reset a service access token's secret key. |
  \| <code> updateAccessTokenDescription </code>

  \| Change the description of a service access token. |
  \| <code> updateAccessTokenName </code>

  \| Change the name of a service access token. |
</Accordion>

## Session actions

<Accordion title="Expand Session actions">
  `session` is a child of a project. Sessions are related to the [observability feature](/home/observability).

  A code sample is below:

  <CodeGroup>
    ```text title="Session resource" theme={null}
          proj/*:session/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> viewSession </code>

  \| View a session. |

  To learn more, read [Session replay](/home/observability/session-replay).
</Accordion>

## Team actions

<Accordion title="Expand Team actions">
  `team` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Team resource" theme={null}
          team/*
    ```
  </CodeGroup>

  To learn more, read [Teams](/home/account/teams).

  This table explains the available team actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createTeam </code>

  \| Create a new team. |
  \| <code> deleteTeam </code>

  \| Delete a team. |
  \| <code> updateTeamCustomRoles </code>

  \| Add or remove custom roles from a team. |
  \| <code> updateTeamDescription </code>

  \| Update the description of a team. |
  \| <code> updateTeamMembers </code>

  \| Add or remove members to or from a team. |
  \| <code> updateTeamName </code>

  \| Change the name of a team. |
  \| <code> updateTeamPermissionGrants </code>

  \| Update a team's permission grants. Permission grants can be added or removed using the [REST API](/api-reference/teams/update-team) . |
  \| <code> updateTeamRoleAttributes </code>

  \| Update a team's role attributes. |
  \| <code> viewTeam </code>

  \| If set to deny, anyone impacted by this policy can neither view nor modify a team. |

  <Note title="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](/guides/teams-roles/teams#create-private-teams).
  </Note>
</Accordion>

## Template actions

<Accordion title="Expand Template actions">
  `template` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Template resource" theme={null}
          template/*
    ```
  </CodeGroup>

  To learn more, read [Workflow templates](/home/releases/workflow-templates).

  This table explains the available workflow template actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createTemplate </code>

  \| Create a new template. |
  \| <code> deleteTemplate </code>

  \| Delete a template. |
  \| <code> viewTemplate </code>

  \| If set to deny, anyone impacted by this policy can neither view nor modify a template. |
</Accordion>

## Trace actions

<Accordion title="Expand Trace actions">
  `trace` is a child of a project. Traces are related to the [observability feature](/home/observability).

  A code sample is below:

  <CodeGroup>
    ```text title="Trace resource" theme={null}
          proj/*:trace/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> viewTrace </code>

  \| View a trace. |

  To learn more, read [Traces](/home/observability/traces).
</Accordion>

## Vega actions

<Accordion title="Expand Vega actions">
  `vega` is a child of a project. Vega is the [observability feature](/home/observability) AI agent.

  A code sample is below:

  <CodeGroup>
    ```text title="Vega resource" theme={null}
          proj/*:vega/*
    ```
  </CodeGroup>

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> talkToVega </code>

  \| Access the Vega AI agent. |

  To learn more, read [Vega](/home/getting-started/vega).
</Accordion>

## View actions

<Accordion title="Expand View actions">
  `view` is a child of a project. A code sample is below:

  <CodeGroup>
    ```text title="View resource" theme={null}
          proj/*:view/*
    ```
  </CodeGroup>

  To learn more, review [Views](/home/account/views).

  This table explains the available view actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createView </code>

  \| Create a new view. |
  \| <code> deleteView </code>

  \| Delete a view. |
  \| <code> linkFlagToView </code>

  \| Link a flag to a view. |
  \| <code> linkSegmentToView </code>

  \| Link a segment to a view. |
  \| <code> linkMetricToView </code>

  \| Link a metric to a view. |
  \| <code> unlinkFlagFromView </code>

  \| Unlink a flag from a view. |
  \| <code> unlinkSegmentFromView </code>

  \| Unlink a segment from a view. |
  \| <code> updateView </code>

  \| Update a view. |
  \| <code> viewView </code>

  \| View a view. |
</Accordion>

## Webhook actions

<Accordion title="Expand Webhook actions">
  `webhook` is a top-level resource. A code sample is below:

  <CodeGroup>
    ```text title="Webhook resource" theme={null}
          webhook/*
    ```
  </CodeGroup>

  To learn more, read [Webhooks](/home/infrastructure/webhooks).

  This table explains the available webhooks actions:

  \| Action

  | Description |
  | - |

  \| --- |
  \| <code> createWebhook </code>

  \| Create new webhooks. |
  \| <code> deleteWebhook </code>

  \| Delete existing webhooks. |
  \| <code> updateName </code>

  \| Change the name of webhook configurations. |
  \| <code> updateOn </code>

  \| Enable and disable existing webhooks. |
  \| <code> updateQuery </code>

  \| Modify a webhook query. |
  \| <code> updateSecret </code>

  \| Update an existing webhook's signing secret. |
  \| <code> updateStatements </code>

  \| Update webhook policy statements. |
  \| <code> updateTags </code>

  \| Update webhook tags. |
  \| <code> updateUrl </code>

  \| Change the URL for a webhook. |
</Accordion>
