diff --git a/blog-service/2024-07-03-manage.md b/blog-service/2024-07-03-manage.md
new file mode 100644
index 0000000000..c78cc3a78c
--- /dev/null
+++ b/blog-service/2024-07-03-manage.md
@@ -0,0 +1,19 @@
+---
+title: Sumo Orgs - New Credits Management Experience (Manage)
+image: https://help.sumologic.com/img/sumo-square.png
+keywords:
+ - credits-management
+ - manage
+hide_table_of_contents: true
+authors:
+ - url: https://help.sumologic.com/release-notes-service/rss.xml
+ image_url: /img/release-notes/rss-orange.png
+---
+
+We are excited to introduce a new and enhanced credits management experience for our Sumo Logic orgs customers. This update empowers Sumo Logic parent org admins to manage child org credits with greater ease and control. Here are the key improvements in this update:
+
+- **Flexible Allocation**. Parent org admins can now allocate and manage credits for child orgs more flexibly, with faster and fewer steps.
+- **Smart Recommendations**. Receive system-suggested credit allocations tailored to your needs.
+- **Effortless Top-Ups**. Seamlessly top-up credits for child orgs upon depletion without needing baseline adjustments.
+
+[Learn more](/docs/manage/manage-subscription/create-manage-orgs#create-a-new-child-organization).
diff --git a/docs/manage/manage-subscription/create-manage-orgs-service-providers.md b/docs/manage/manage-subscription/create-manage-orgs-service-providers.md
index 6735d2aad6..fb5e20d4f3 100644
--- a/docs/manage/manage-subscription/create-manage-orgs-service-providers.md
+++ b/docs/manage/manage-subscription/create-manage-orgs-service-providers.md
@@ -83,53 +83,107 @@ After you create a child org, you can’t delete it.
:::
1. In the main Sumo Logic menu, select **Administration > Organizations**.
-1. Click **+ Add Organization**.
-1. The **Create New Organization** pane appears.
+1. Click **+ Add Organization**.
})
+1. The **Create New Organization** pane appears.
})
+
+### Allocate Credits
+
+1. **Plan Type**. Select your organization's plan type. By default, “POV Trial (45 days)” is selected. Leave it selected.
+1. **Deployment**. Select a Sumo Logic deployment from the list.
+ :::note
+ Depending on your Sumo Logic subscription type, creating an org in a different deployment than the parent may incur additional deployment charges.
+ :::
+1. Click **View Baseline**.
+1. The **Baselines** popup appears and displays the POV Trial org ingest limits, which you cannot change.
})
+1. View the following:
+ * **Continuous Log Ingest**. Estimated daily ingestion to the Continuous Tier.
+ * **Frequent Log Ingest.** Estimated daily ingestion to the Frequent Tier.
+ * **Infrequent Log Ingest.** Estimated daily ingestion to the Infrequent Tier.
+ * **Metrics**. Estimated daily metric data points per minute (DPM) ingestion.
+ * **Tracing**. Estimated daily ingestion of traces.
+ * **CSE Log Ingest**. Estimated daily Cloud SIEM ingestion.
+1. Click **Done** to go back.
+
+### Basic Details
+
1. **Organization Name**. Enter a unique name for the org.
1. **Account Owner Email**. Enter the name of the account owner.
1. **Account Owner First Name**. Enter the account owner’s first name.
1. **Account Owner Last Name**. Enter the account owner’s last name.
-1. **Deployment**. Select a Sumo Logic deployment from the list.
-1. **Plan Type**. By default, “POV Trial” is selected. Leave it selected.
-1. Click **View Allocation**.
-1. The **Baselines** popup appears, and displays the ingest limits for a POV Trial org. You cannot change the limits.
})
-2. Click **Done**.
-3. Click **Save** to save the new org.
+1. Click **Save** to save the new org.
## Upgrade a POV Trial org
1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the trial org you want to upgrade.
})
1. The right pane appears with information about the org. Click **Edit**.
})
-1. In the edit pane, click **Plan Type**, and choose the Enterprise plan that appears as an option.
})
+1. In the edit pane, choose the **Enterprise plan** that appears as an option in the **Plan Type** dropdown.
1. A warning message is shown that says you won’t be able to downgrade the org once you upgrade it.
})
-1. Click **Allocate Credits**.
+1. Click **Set Baseline**.
1. The Credits Calculator appears.
})
-1. **Continuous Log Ingest**. Enter estimated daily ingestion to the Continuous Tier.
-1. **Frequent Log Ingest**. Enter estimated daily ingestion to the Frequent Tier.
-1. **Infrequent Log Ingest**. Enter estimated daily ingestion to the Infrequent Tier.
-1. **Metrics**. Enter estimated daily metric data points per minute (DPM) ingestion.
-1. **Tracing**. Enter estimated daily ingestion of traces.
-1. **Cloud SIEM**. Click the checkbox to enable Cloud SIEM.
- 1. If you enable Cloud SIEM, the Cloud SIEM Log Ingest field appears.
- 2. Enter a value in GB.
- :::note
- Provisioning Cloud SIEM can take up to 24 hours. See [Monitor Cloud SIEM Provisioning](#monitor-cse-provisioning), below.
- :::
-7. As you enter the ingestion estimates, the number of credits required for the ingestion levels is incremented.
})
-1. Click **Use This Allocation**.
+ * **Continuous Log Ingest**. Enter estimated daily ingestion to the Continuous Tier.
+ * **Frequent Log Ingest**. Enter estimated daily ingestion to the Frequent Tier.
+ * **Infrequent Log Ingest**. Enter estimated daily ingestion to the Infrequent Tier.
+ * **Metrics**. Enter estimated daily metric data points per minute (DPM) ingestion.
+ * **Tracing**. Enter estimated daily ingestion of traces.
+1. **Cloud SIEM Enterprise**. Click the checkbox to enable Cloud SIEM. When the **Cloud Log Ingest** field appears, enter a value in GB.
+ :::note
+ Provisioning Cloud SIEM can take up to 24 hours. See [Monitor Cloud SIEM Provisioning](#monitor-cloud-siem-provisioning), below.
+ :::
+1. As you enter the ingestion estimates, the number of credits required for the ingestion levels is incremented.
+1. The calculator now shows the recommended credit allocation, which provides you a suggestion on how many credits you would need for the child org. This is calculated based on the baseline added, the burndowns in your contact, and the days remaining in your contract.
+1. Click **Done** after adding the baseline.
+1. Click **Save** to save the changes.
+
+## Update a CF Credit - Free org
+
+If a POV trial org is not upgraded to Enterprise plan after 45 days, the org will be downgraded to the **CF Credit - Free** plan. If you need to upgrade this plan to Enterprise, follow the below steps:
+
+1. In the main Sumo Logic menu, select **Administration > Organizations**.
+1. Click the org with the **CF Credit - Free** plan that you want to upgrade to.
+1. The right pane appears with information about the org. Click **Upgrade**.
})
+1. Click **Set Baseline**.
})
+1. The credits calculator appears.
+ * **Continuous Log Ingest**. Enter estimated daily ingestion to the Continuous Tier.
+ * **Frequent Log Ingest**. Enter estimated daily ingestion to the Frequent Tier.
+ * **Infrequent Log Ingest**. Enter estimated daily ingestion to the Infrequent Tier.
+ * **Metrics**. Enter estimated daily metric data points per minute (DPM) ingestion.
+ * **Tracing**. Enter estimated daily ingestion of traces.
+1. **Cloud SIEM Enterprise**. Click the checkbox to enable Cloud SIEM. When the **Cloud Log Ingest** field appears, enter a value in GB.
+ :::note
+ Provisioning Cloud SIEM can take up to 24 hours. See [Monitor Cloud SIEM Provisioning](#monitor-cloud-siem-provisioning), below.
+ :::
+1. As you enter the ingestion estimates, the number of credits required for the specified ingestion levels will be incremented.
+1. The calculator now shows the recommended credit allocation, which provides you a suggestion on how many credits you would need for the child org. This is calculated based on the baseline added, the burndowns in your contact, and the days remaining in your contract.
+1. Click **Done** after adding the baseline.
+1. Click **Save** to save the changes.
## Update an org's credits allocation
-You can update an Enterprise org’s credits allocation, but not a Trial POV org.
+:::info
+If the org has already depleted its credits, you can see a red color warning icon in the **Usage %** column and a red-colored usage bar in the **Allocation & usage** section when you view the selected org.
+:::
-1. To change an org's credits allocation
-1. In the main Sumo Logic menu, select **Administration > Organizations**.
+To change an org's credits allocation:
+1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the org you want to edit.
-1. Click **Edit** in the right hand pane.
})
-1. Click **Modify Allocation**.
})
-1. The Credits Calculator appears.
-1. Follow steps in [Upgrade a POV Trial org](#upgrade-a-pov-trial-org) to finish.
+1. Click **Edit** in the right hand pane.
})
+1. Under **Modify Credit Allocation**, you can increase or decrease the credits based on your requirement.
+ :::note
+ Ensure your total new allocation is not less than the consumed credits.
+ :::
+ You can select **Credits to be Added** and enter either the recommended credit value or a value of your choice to top-up additional credits and avoid credit depletion. This recommendation is calculated based on the usage forecast and the average daily credit usage for the selected contract period.
+
+ **Example 1**: Consider that you are heading towards credit depletion and need to add more credits. The below image shows you have almost run out of the credits (1840/1841) allocated to the child org. To increase the credits to the child org, select **Credits to be Added**. An info icon will appear below with a suggestion on how many credits can be added to this child org based on the usage forecast. So, in this case, it is suggested that you add 135 credits.
})
+
Click **View Details** to view the detailed breakdown of the recommended value.
})
+
+ **Example 2**: Consider you need to increase credits to your child org. The below image shows that you have used 35 credits out of 31026 credits allocated to your child org. Now, if you wish to increase the credits to your child org, select **Credits to be Added** and add the additional credits required.
})
+1. If you want to modify the baseline, click **View Baseline**. The **Credits Calculator** appears.
+ 1. Click **Edit** and follow the steps in [Allocate Credits](#allocate-credits) to update the credits allocation.
})
+ 1. Depending on the new baseline values, the calculator now shows the recommended credit allocation, which provides a suggestion on how many credits you would need to add for the child org.
})
+ 1. Once you set the baseline, you can view the recommended value in the **Credits to be Added** section.
})
+ 1. (Optional) Click **View Details** to view the detailed breakdown of additional credits required value.
})
+1. Click **Save** once you finish editing the credit values.
## Deactivate a POV Trial org
@@ -216,16 +270,17 @@ You can access the child credits usage for a selected organization from the **Or
1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the org you want to access the credits usage.
-1. Scrow down to **Credits Usage**. You can see the total percentage of credits consumed out of the total number of credits allocated.
-1. Click **Open in Account Overview** for detailed child credit usage report for the selected organization.
})
+1. You can see the total percentage of credits consumed out of the total number of credits allocated in the **Allocation & usage** section.
+1. Click **Open in Account Overview** for a detailed child credit usage report for the selected organization.
## View baselines
Your estimates of ingest capacity required for each product variable are called as baselines. Sumo Logic’s throttling multipliers for logs and metrics are based on these estimates, you can access it from the **Organizations** UI.
-1. In the main Sumo Logic menu, select **Administration > Organizations**.
+1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the org you want to check the baselines.
-1. Click **View the organization baselines here** at the bottom of the right hand pane.
})
})
+1. Click **Edit** in the right hand pane.
+1. To view the baseline, click **View Baseline**.
})
## Audit logging for organizations
diff --git a/docs/manage/manage-subscription/create-manage-orgs.md b/docs/manage/manage-subscription/create-manage-orgs.md
index 413915f04e..335e9f9e3a 100644
--- a/docs/manage/manage-subscription/create-manage-orgs.md
+++ b/docs/manage/manage-subscription/create-manage-orgs.md
@@ -44,64 +44,86 @@ There are several role capabilities that are required to work with orgs:
* **Create Trial Organizations**. This capability is required to create and provision trial organizations.
* **Upgrade Trial Organizations**. This capability is required to upgrade trial organizations.
-## Create a child org
+## Create a new child organization
-This section has instructions for creating a child org.
+This section has instructions for creating a new org.
:::note
-After you create a child org, you can’t delete it.
+After you create a new org, you can’t delete it.
:::
1. In the main Sumo Logic menu, select **Administration > Organizations**.
-1. Click **+ Add Organization**.
- 
-1. The **Create New Organization** pane appears.
- 
- :::note
- The **Credits Usage** portion of the pane shows information you’ll want to know when you assign credits to the new org: **Total Credits Quota** is the total number of credits for your subscription; **Available Credits** is the number of credits that have not yet been allocated to child orgs.
- :::
- Enter the following:
- * **Organization Name**. Enter a unique name for the org.
- * **Account Owner Email**. Enter the name of the account owner.
- * **Account Owner First Name**. Enter the account owner’s first name.
- * **Account Owner Last Name**. Enter the account owner’s last name.
- * **Deployment**. Select a Sumo Logic deployment from the list.
- :::note
- Depending on your Sumo Logic subscription type, creating an org in a different deployment than the parent may result in a deployment charge being applied.
- :::
- * **Plan Type**. Select your organization's plan type.
-1. Click **Allocate Credits**. The **Credits Calculator** appears.
})
-1. Enter the following:
- * **Continuous Tier**. Enter estimated daily ingestion to the Continuous Tier.
- * **Frequent Tier.** Enter estimated daily ingestion to the Frequent Tier.
- * **Infrequent Tier.** Enter estimated daily ingestion to the Infrequent Tier.
- * **Metrics**. Enter estimated daily metric data points per minute (DPM) ingestion.
- * **Tracing**. Enter estimated daily ingestion of traces.
-1. **Cloud SIEM**. Click the checkbox to enable Cloud SIEM.
- 1. If you enable Cloud SIEM, the Cloud SIEM Log Ingest field appears.
- 1. Enter a value in GB.
+1. Click **+ Add Organization**.
})
+1. The **Create New Organization** pane appears.
})
+
+### Allocate Credits
+
+1. **Plan Type**. Select your organization's plan type.
+1. **Deployment**. Select a Sumo Logic deployment from the list.
:::note
- Provisioning Cloud SIEM can take up to 24 hours. See [Monitor Cloud SIEM Provisioning](#monitor-cse-provisioning), below.
+ Depending on your Sumo Logic subscription type, creating an org in a different deployment than the parent may result in a deployment charge being applied on the usage.
:::
-1. As you enter the ingestion estimates, the number of credits required for the ingestion levels is incremented.
})
-1. To see a breakdown of the required credits, click **View Breakdown**.
})
-1. The calculator now shows how many credits are associated with the ingestion volume and, as applicable, how many are due to the deployment factor—the upcharge based on the deployment where the org is located.
-1. Click **Use This Allocation**.
+1. Click **Set Baseline**.
+ :::note
+ You need to set the baseline to allocate credits.
+ :::
+ })
+1. In the credits calculator, enter the following:
+ * **Continuous Log Ingest**. Enter estimated daily ingestion to the Continuous Tier.
+ * **Frequent Log Ingest.** Enter estimated daily ingestion to the Frequent Tier.
+ * **Infrequent Log Ingest.** Enter estimated daily ingestion to the Infrequent Tier.
+ * **Metrics**. Enter estimated daily metric data points per minute (DPM) ingestion.
+ * **Tracing**. Enter estimated daily ingestion of traces.
+1. **Cloud SIEM Enterprise**. Click the checkbox to enable Cloud SIEM. When the **Cloud Log Ingest** field appears, enter a value in GB.
+ :::note
+ Provisioning Cloud SIEM can take up to 24 hours. See [Monitor Cloud SIEM Provisioning](#monitor-cloud-siem-provisioning), below.
+ :::
+1. As you enter the ingestion estimates, the number of credits required for the specified ingestion levels will be incremented.
+1. The calculator now shows the recommended credit allocation, which provides you a suggestion on how many credits you would need for the child org. This is calculated based on the baseline added, the burndowns in your contact, and the days remaining in your contract.
+1. Throttling limits displays the rate of ingestion. To learn more, refer to [Log Ingestion](/docs/manage/ingestion-volume/log-ingestion/).
+1. Once you're finished adding the baseline, click **Done**.
+1. **Credits to be allocated**. The recommended credits for this child org will be displayed once you set the baseline. You can add or reduce the credit based on your requirement.
+1. **Remaining Credits (Parent)**. Total balance credits available in the parent org after using the credits for child org.
+
+### Basic Details
+
+1. **Organization Name**. Enter a unique name for the org.
+1. **Account Owner Email**. Enter the name of the account owner.
+1. **Account Owner First Name**. Enter the account owner’s first name.
+1. **Account Owner Last Name**. Enter the account owner’s last name.
})
## Update an org's credits allocation
+:::info
+If the org has already depleted its credits, you can see a red color warning icon in the **Usage %** column and a red-colored usage bar in the **Allocation & usage** section when you view the selected org.
+:::
+
To change an org's credits allocation:
1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the org you want to edit.
1. Click **Edit** in the right hand pane.
-2. Click **Modify Allocation**.
-3. The **Credits Calculator** appears.
-4. Follow the steps in [Create a child org](#create-a-child-org) to update the credits allocation.
+1. Under **Modify Allocation**, you can increase or decrease the credits based on your requirement.
+ :::note
+ Ensure your total new allocation is not less than the consumed credits.
+ :::
+ You can select **Credits to be Added** and enter the recommended credit value or value of your choice to top-up additional credits to avoid credit depletion. This recommendation is calculated based on the usage forecast and average credit usage per day for the selected contract period.
+
+ **Example 1**: Consider that you are heading towards credit depletion and need to add more credits. The below image shows you have almost run out of the credits (1840/1841) allocated to the child org. To increase the credits to the child org, select **Credits to be Added**. An info icon will appear below with a suggestion on how many credits can be added to this child org based on the usage forecast. So, in this case, it is suggested that you add 135 credits.
+
Click **View Details** to view the detailed breakdown of the recommended value.
+
+ **Example 2**: Suppose you need to increase credits for your child org. The image below shows that you have used 35 out of 31,026 credits allocated to your child org. To add more credits, select **Credits to be Added** and enter the additional credits required.
+1. If you want to modify the baseline, click **View Baseline**. The credits calculator appears.
+ 1. Click **Edit** and follow the steps in [Allocate Credits](#allocate-credits) to update the credits allocation.
+ 1. Based on the new baseline values, the calculator now shows the recommended credit allocation, suggesting how many credits you should add for the child org.
+ 1. Once you set the baseline, you can view the recommended value in the **Credits to be Added** section.
+ 1. (Optional) Click **View Details** to view the detailed breakdown of additional credits required value.
+1. Click **Save** once you finish editing the credit values.
## Monitor Cloud SIEM provisioning
+
Provisioning Cloud SIEM can take up to 24 hours. You can determine provisioning status on the **Organizations** page. Until the provisioning is complete, you'll see a spinner and message that indicates the process is on-going.
-})
+
## Monitor credits allocation and usage
@@ -174,8 +196,8 @@ You can access the child credits usage for a selected organization from the **Or
1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the org you want to access the credits usage.
-1. Scrow down to **Credits Usage**. You can see the total percentage of credits consumed out of the total number of credits allocated.
-1. Click **Open in Account Overview** for detailed child credit usage report for the selected organization.
+1. You can see the total percentage of credits consumed out of the total number of credits allocated in the **Allocation & usage** section.
+1. Click **Open in Account Overview** for a detailed child credit usage report for the selected organization.
## View baselines
@@ -183,7 +205,8 @@ Your estimates of ingest capacity required for each product variable are called
1. In the main Sumo Logic menu, select **Administration > Organizations**.
1. Click the row for the org you want to check the baselines.
-1. Click **View the organization baselines here** at the bottom of the right hand pane.
+1. Click **Edit** in the right hand pane.
+1. To view the baseline, click **View Baseline**.
## Audit logging for organizations
diff --git a/static/img/subscriptions/access-org.png b/static/img/subscriptions/access-org.png
index 10d9ad7db2..39869eaa10 100644
Binary files a/static/img/subscriptions/access-org.png and b/static/img/subscriptions/access-org.png differ
diff --git a/static/img/subscriptions/allocate-credits-set-baseline.png b/static/img/subscriptions/allocate-credits-set-baseline.png
new file mode 100644
index 0000000000..d8115b63d5
Binary files /dev/null and b/static/img/subscriptions/allocate-credits-set-baseline.png differ
diff --git a/static/img/subscriptions/baseline-credits-to-add.png b/static/img/subscriptions/baseline-credits-to-add.png
new file mode 100644
index 0000000000..0db08cd9b8
Binary files /dev/null and b/static/img/subscriptions/baseline-credits-to-add.png differ
diff --git a/static/img/subscriptions/baseline-view-details.png b/static/img/subscriptions/baseline-view-details.png
new file mode 100644
index 0000000000..ac7732e16b
Binary files /dev/null and b/static/img/subscriptions/baseline-view-details.png differ
diff --git a/static/img/subscriptions/baselines-pov.png b/static/img/subscriptions/baselines-pov.png
new file mode 100644
index 0000000000..833fb248a0
Binary files /dev/null and b/static/img/subscriptions/baselines-pov.png differ
diff --git a/static/img/subscriptions/baselines_1.png b/static/img/subscriptions/baselines_1.png
index 0971218313..38d8eb447b 100644
Binary files a/static/img/subscriptions/baselines_1.png and b/static/img/subscriptions/baselines_1.png differ
diff --git a/static/img/subscriptions/baselines_2.png b/static/img/subscriptions/baselines_2.png
index 3031bc08a4..a66d334ad4 100644
Binary files a/static/img/subscriptions/baselines_2.png and b/static/img/subscriptions/baselines_2.png differ
diff --git a/static/img/subscriptions/baselines_3.png b/static/img/subscriptions/baselines_3.png
new file mode 100644
index 0000000000..403f5a3451
Binary files /dev/null and b/static/img/subscriptions/baselines_3.png differ
diff --git a/static/img/subscriptions/basic-details.png b/static/img/subscriptions/basic-details.png
new file mode 100644
index 0000000000..5f30ceed6d
Binary files /dev/null and b/static/img/subscriptions/basic-details.png differ
diff --git a/static/img/subscriptions/calculator.png b/static/img/subscriptions/calculator.png
index 4a65571d27..780ae8cee4 100644
Binary files a/static/img/subscriptions/calculator.png and b/static/img/subscriptions/calculator.png differ
diff --git a/static/img/subscriptions/child-credits-usage.png b/static/img/subscriptions/child-credits-usage.png
index 10417cc3ef..0e450ad780 100644
Binary files a/static/img/subscriptions/child-credits-usage.png and b/static/img/subscriptions/child-credits-usage.png differ
diff --git a/static/img/subscriptions/create-new-org.png b/static/img/subscriptions/create-new-org.png
index d96e8c7769..16f32a90c7 100644
Binary files a/static/img/subscriptions/create-new-org.png and b/static/img/subscriptions/create-new-org.png differ
diff --git a/static/img/subscriptions/credits-calculator.png b/static/img/subscriptions/credits-calculator.png
index 5d4ade113e..cc75d7857f 100644
Binary files a/static/img/subscriptions/credits-calculator.png and b/static/img/subscriptions/credits-calculator.png differ
diff --git a/static/img/subscriptions/edit-baseline-example.png b/static/img/subscriptions/edit-baseline-example.png
new file mode 100644
index 0000000000..624f388e28
Binary files /dev/null and b/static/img/subscriptions/edit-baseline-example.png differ
diff --git a/static/img/subscriptions/edit-baseline.png b/static/img/subscriptions/edit-baseline.png
new file mode 100644
index 0000000000..07cde88585
Binary files /dev/null and b/static/img/subscriptions/edit-baseline.png differ
diff --git a/static/img/subscriptions/edit-option.png b/static/img/subscriptions/edit-option.png
index 7c85563314..e116b97e98 100644
Binary files a/static/img/subscriptions/edit-option.png and b/static/img/subscriptions/edit-option.png differ
diff --git a/static/img/subscriptions/edit-org-3.png b/static/img/subscriptions/edit-org-3.png
index 3083e63810..10617b2453 100644
Binary files a/static/img/subscriptions/edit-org-3.png and b/static/img/subscriptions/edit-org-3.png differ
diff --git a/static/img/subscriptions/free-org-set-baseline.png b/static/img/subscriptions/free-org-set-baseline.png
new file mode 100644
index 0000000000..8a0c424d5c
Binary files /dev/null and b/static/img/subscriptions/free-org-set-baseline.png differ
diff --git a/static/img/subscriptions/modify-allocation-button.png b/static/img/subscriptions/modify-allocation-button.png
index 0bdf27b963..5948cd706e 100644
Binary files a/static/img/subscriptions/modify-allocation-button.png and b/static/img/subscriptions/modify-allocation-button.png differ
diff --git a/static/img/subscriptions/modify-allocation-recommendatio-example-2.png b/static/img/subscriptions/modify-allocation-recommendatio-example-2.png
new file mode 100644
index 0000000000..0554c5d11a
Binary files /dev/null and b/static/img/subscriptions/modify-allocation-recommendatio-example-2.png differ
diff --git a/static/img/subscriptions/modify-allocation-recommendation.png b/static/img/subscriptions/modify-allocation-recommendation.png
new file mode 100644
index 0000000000..f9229ffc71
Binary files /dev/null and b/static/img/subscriptions/modify-allocation-recommendation.png differ
diff --git a/static/img/subscriptions/modify-allocation-usage-forecast.png b/static/img/subscriptions/modify-allocation-usage-forecast.png
new file mode 100644
index 0000000000..6769c429e3
Binary files /dev/null and b/static/img/subscriptions/modify-allocation-usage-forecast.png differ
diff --git a/static/img/subscriptions/plan-selected.png b/static/img/subscriptions/plan-selected.png
index 2673274e25..6b8f20abfb 100644
Binary files a/static/img/subscriptions/plan-selected.png and b/static/img/subscriptions/plan-selected.png differ
diff --git a/static/img/subscriptions/pov-baselines.png b/static/img/subscriptions/pov-baselines.png
deleted file mode 100644
index 64d91be58f..0000000000
Binary files a/static/img/subscriptions/pov-baselines.png and /dev/null differ
diff --git a/static/img/subscriptions/sp-create-new-org.png b/static/img/subscriptions/sp-create-new-org.png
index f912cf5b46..ac51df6eba 100644
Binary files a/static/img/subscriptions/sp-create-new-org.png and b/static/img/subscriptions/sp-create-new-org.png differ
diff --git a/static/img/subscriptions/upgrade-plan.png b/static/img/subscriptions/upgrade-plan.png
index 9365c54a3f..66dba5993d 100644
Binary files a/static/img/subscriptions/upgrade-plan.png and b/static/img/subscriptions/upgrade-plan.png differ
diff --git a/static/img/subscriptions/upgrade.png b/static/img/subscriptions/upgrade.png
new file mode 100644
index 0000000000..c413f774bf
Binary files /dev/null and b/static/img/subscriptions/upgrade.png differ