Updates

Author: rajlearner17

docs/guides/github/decommission/guardrails-console-login.png

@@ -3,49 +3,62 @@ title: Decommission GitHub Organization
 sidebar_label: Decommission GitHub Organization
 ---
 
-CHANGES TODO
-
 # Decommission GitHub Organization
 
 In this guide, you will:
 
 - Learn how to decommission a GitHub organization from a Guardrails workspace while managing associated resources effectively.
 
-Guardrails allows administrators to remove a GitHub organization from a workspace. The delete action removes all associated policies and references from the Guardrails database, but **does not delete any resources** from the target GitHub organization. Careful consideration should be made when managing resources such as webhooks, as once removed, these changes cannot be undone.
-
-Before starting the process, administrators should determine whether Guardrails-managed resources (e.g., webhooks) should remain in the organization. The following policies can be configured in Guardrails to facilitate cleanup. Ensure that these changes are applied **only to the target GitHub organization**.
+Guardrails allows administrators to remove a [GitHub Organization](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations) from a workspace. The delete action removes all associated policies and references from the Guardrails database, but `does not delete any resources` from the target GitHub organization.
 
-1. `GitHub > Organization > Event Handlers` set to `Enforce: Disabled`. This removes Guardrails-configured webhooks.
+<!-- Careful consideration should be made when managing resources such as webhooks, as once removed, these changes cannot be undone. -->
 
-Once these policies have been applied and the associated controls have completed their cleanup, the GitHub organization can be safely removed from the Guardrails workspace.
+> [!IMPORTANT]
+> Before starting the process, administrators should determine whether Guardrails-managed resources (e.g., webhooks) should remain in the organization. The following policies can be configured in Guardrails to facilitate cleanup. Ensure that these changes are applied **only to the target GitHub organization**.
 
 ## Prerequisites
 
 - **Turbot/Operator** permissions at the Turbot resource level.
 - Familiarity with the Guardrails console.
+- Familiarity with the GitHub.
+
+DISCUSS THE SEQUENCE, WEBHOOKS SETUP WITH SD
+
+## Disable Event Handlers
+
+Disable Event Handlers associated with `GitHub > Organization > Event Handlers` with value set to `Enforce: Disabled`. This removes Guardrails-configured webhooks. Once these policies have been applied and the associated controls have completed their cleanup, the GitHub organization can be safely removed from the Guardrails workspace.
 
-## Step 1: Remove Credentials Policies
+## Remove Credentials Policies
 
 Delete the policy `GitHub > Config > Personal Access Token` configured for the target GitHub organization. This ensures that Guardrails no longer has access to the organization.
 
-## Step 2: Log in to the Guardrails Console
+## Delete the Organization
 
-Log in to the Guardrails console.
+Login to the Guardrails console.
 
 ![Guardrails Console Login](/images/docs/guardrails/guides/github/decommission-github-organization/guardrails-console-login.png)
 
-## Step 3: Navigate to the Organization
+Navigate to the `Organization` that needs to be removed.
+
+Image
+
+Select the **Actions** button in the top-right corner and choose **Actions** button in the top-right corner.
+
+Image
+
+Select the **Remove from Turbot**.
+
+> [!NOTE]
+> If you don’t see this button, contact your Guardrails administrator for the required permissions.
 
-Using the Guardrails console, navigate to the GitHub organization that needs to be removed.
+In the popup window, copy the `Organization ID` and paste it into the text box. Select **Delete**.
 
-## Step 4: Delete the Organization
+Image
 
-1. Click the **Actions** button in the top-right corner.
-2. Click the **Remove from Turbot** button in the top-right corner. If you don’t see this button, contact your Guardrails administrator for the required permissions.
-3. In the popup window, copy the organization ID and paste it into the text box.
-4. Click **Delete**. While the deletion is reversible by re-importing the organization, it can be resource-intensive. Double-check all configurations before proceeding.
+> [!IMPORTANT]
+> While the deletion is reversible by re-importing the organization, it can be resource-intensive. Double-check all configurations before proceeding.
 
-## Step 5: Verify Deletion
+## Verify
 
 Guardrails will begin the deletion process. The time to complete the process depends on the number of policies and resources associated with the organization. Larger organizations may take longer.
 

docs/guides/github/decommission/index.md

@@ -23,9 +23,10 @@ Importing a [GitHub Organization](https://docs.github.com/en/organizations/colla
 ## Prerequisites
 
 - Access to the Guardrails console with *Turbot/Owner* or *Turbot/Admin* permissions at the Turbot resource level.
+- Familiarity with the GitHub.
 - GitHub mod should be installed in your Guardrails workspace.
-- Ensure access to [GitHub CLI](https://cli.github.com/) to fetch organization id.
-- Ensure GitHub organization has allowed access via personal access tokens. See [Setting a personal access token policy for your organization](https://docs.github.com/en/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization) for more information.
+- Ensure access to [GitHub CLI](https://cli.github.com/) to fetch organization ID.
+- Ensure GitHub organization has allowed access via personal access tokens. Refer [Setting a personal access token policy for your organization](https://docs.github.com/en/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization) for more information.
 
 <!-- ## Supported Authentication -->
 
@@ -51,20 +52,20 @@ To ensure full functionality of the GitHub integration, we recommend granting th
 
 ## Get GitHub Organization ID
 
-There are various ways to get the GitHub organization ID
+There are various ways to get the GitHub organization ID.
 
-Use [GitHub CLI](https://docs.github.com/en/github-cli/github-cli/quickstart) and run the following command to get the id of the organization you want to import.
+Use [GitHub CLI](https://docs.github.com/en/github-cli/github-cli/quickstart) and run the following command to get the ID of the organization you want to import.
 
 ```
 gh api orgs/<organization name> --jq '.id'
 ```
 
-Alternatively, you can use `curl` command to render the ID
+Alternatively, you can use `curl` command to get the organization ID.
 
 ```
 curl -H "Authorization: Bearer ghp_iio5FzBF4OLbbes3AKasdre5f4mps50s7YXE" https://api.github.com/orgs/<your-org-name>
 ```
-The result will be shown as below
+The result will be shown as below:
 
 ```json
 {
@@ -89,11 +90,11 @@ Choose the location where you want to import the organization. Typically this wo
 
 ![Choose Location](/images/docs/guardrails/guides/github/import-github-organization/choose-location.png)
 
-Provide `Organization Name`, `Organization ID`, `Personal Access Token` and choose **Connect**
+Provide `Organization Name`, `Organization ID`, `Personal Access Token` and choose **Connect**.
 
 ![Connect](/images/docs/guardrails/guides/github/import-github-organization/connect.png)
 
-Verify that the controls are executed by navigating to **Controls** tab and select GitHub
+Verify that the controls are executed by navigating to **Controls** tab and select GitHub.
 
 ![Verify Controls](/images/docs/guardrails/guides/github/import-github-organization/verify-github-controls.png)