diff --git a/docs/images/appdynamics_1.png b/docs/images/appdynamics_1.png
new file mode 100644
index 000000000..ab13ca82c
Binary files /dev/null and b/docs/images/appdynamics_1.png differ
diff --git a/docs/images/appdynamics_10.png b/docs/images/appdynamics_10.png
new file mode 100644
index 000000000..40c51be10
Binary files /dev/null and b/docs/images/appdynamics_10.png differ
diff --git a/docs/images/appdynamics_2.png b/docs/images/appdynamics_2.png
new file mode 100644
index 000000000..fbb1c9f9c
Binary files /dev/null and b/docs/images/appdynamics_2.png differ
diff --git a/docs/images/appdynamics_3.png b/docs/images/appdynamics_3.png
new file mode 100644
index 000000000..5ee96bdd4
Binary files /dev/null and b/docs/images/appdynamics_3.png differ
diff --git a/docs/images/appdynamics_4.png b/docs/images/appdynamics_4.png
new file mode 100644
index 000000000..5acd5be83
Binary files /dev/null and b/docs/images/appdynamics_4.png differ
diff --git a/docs/images/appdynamics_5.png b/docs/images/appdynamics_5.png
new file mode 100644
index 000000000..04aeb2449
Binary files /dev/null and b/docs/images/appdynamics_5.png differ
diff --git a/docs/images/appdynamics_6.png b/docs/images/appdynamics_6.png
new file mode 100644
index 000000000..3b5a67ed6
Binary files /dev/null and b/docs/images/appdynamics_6.png differ
diff --git a/docs/images/appdynamics_7.png b/docs/images/appdynamics_7.png
new file mode 100644
index 000000000..3bc5cfb6b
Binary files /dev/null and b/docs/images/appdynamics_7.png differ
diff --git a/docs/images/appdynamics_8.png b/docs/images/appdynamics_8.png
new file mode 100644
index 000000000..be94a6b88
Binary files /dev/null and b/docs/images/appdynamics_8.png differ
diff --git a/docs/images/appdynamics_9.png b/docs/images/appdynamics_9.png
new file mode 100644
index 000000000..ed91c73fe
Binary files /dev/null and b/docs/images/appdynamics_9.png differ
diff --git a/docs/providers/documentation/appdynamics-provider.mdx b/docs/providers/documentation/appdynamics-provider.mdx
index 8948964be..7af267d7a 100644
--- a/docs/providers/documentation/appdynamics-provider.mdx
+++ b/docs/providers/documentation/appdynamics-provider.mdx
@@ -17,16 +17,98 @@ The AppDynamics provider requires the following authentication parameter:
## Connecting with the Provider
1. Ensure you have a AppDynamics account with the necessary [permissions](https://docs.appdynamics.com/accounts/en/cisco-appdynamics-on-premises-user-management/roles-and-permissions). The basic permissions required are `Account Owner` or `Administrator`. Alternatively you can create an account (instructions)[https://docs.appdynamics.com/accounts/en/global-account-administration/access-management/manage-user-accounts]
-### Basic Auth authentication
+## Provider configuration
-Obtain AppDynamics Username and Password:
1. Find your account name [here](https://accounts.appdynamics.com/overview).
+2. Get the appId of the Appdynamics instance in which you wish to install the webhook into.
+3. Determine the Host [here](https://accounts.appdynamics.com/overview).
-OR create Access Token:
-1. Follow instructions [here](https://docs.appdynamics.com/appd/23.x/latest/en/extend-appdynamics/appdynamics-apis/api-clients)
+### Basic Auth authentication
-1. Determine the Host [here](https://accounts.appdynamics.com/overview).
-2. Get the appId of the Appdynamics instance in which you wish to install the webhook into.
+1. Obtain AppDynamics **Username** and **Password**
+2. Go to **Basic Auth** tab under **Authentication** section
+3. Enter **Username** and **Password**
+
+
+
+
+
+### Access Token authentication
+
+1. Log in to the **Controller UI** as an **Account Owner** or other roles with the **Administer users**, **groups**, **roles** permission.
+2. Go to **Administration**
+
+
+
+
+
+3. Go to **API Client** tab
+
+
+
+
+
+4. Click **+ Create**
+
+
+
+
+
+5. Fill Client **Name** and **Description**
+6. Click **Generate Secret**
+
+
+
+
+
+
+ This API Client secret is not an authentication token yet
+
+
+7. Add **Account Owner** and/or **Administrator** roles
+
+
+
+
+
+8. Click **Save**
+
+
+
+
+
+9. Click **Generate Temporary Token**
+
+
+
+
+
+
+ This token is not persistent, but since Keep uses it just once to install Webhook, we will use it without oAuth
+
+
+10. Click **Save** one again
+
+ This is important. Otherwise generated token will not be saved and authentication will fail
+
+11. Copy generated token
+
+
+
+
+
+12. Go to **Access Token** tab under **Authentication** section
+
+
+
+
+
+13. Enter Access Token
+
+## Connecting provider
+
+1. Ensure **Install webhook** is checked
+2. Click **Connect**
## Webhook Integration Modifications