This topic explains how to authorize or revoke access of an OAuth app.
It is critically important to only authorize applications you trust to use your LaunchDarkly account. Read the permissions required by the app carefully and use your own best judgment about whether you trust an app enough to use it.
You can connect your LaunchDarkly account to external applications, such as the LaunchDarkly Slack app, using the OAuth 2.0 protocol. When you authorize an OAuth application, you grant the application access to information and actions an account member might take. Some applications can act on your behalf, such as by turning feature flags on and off.
Your LaunchDarkly credentials and billing information will never be shared with any OAuth application you authorize.
If you are interested in developing your own OAuth application, read Registering a LaunchDarkly OAuth client.
On initial authorization, an OAuth app shows you a complete list of permissions it requires in order to work. While the app may have the capability to perform many actions in LaunchDarkly, the app’s ability to do anything is limited by the abilities of the account member who authorizes it.
Additionally, if your own permissions are reduced, applications you have previously authorized will have reduced permissions as will.
For example, if you are have a Writer base role and authorize an app, and then are downgraded to a Reader base role, your app will only have Reader-level permissions.
We care about the security of your information. You or an Administrator can revoke an app’s permission to use your account at any time.
If you are a LaunchDarkly administrator, you can revoke access of any app added to LaunchDarkly, regardless of which account member added it.
To disconnect an app:
The application’s access is revoked.