+ })
+Create and Manage Orgs (Flex)
+Learn how to create and manage multiple Sumo Logic Orgs with Flex data.
+})
+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
+ 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. Click **Set Baseline**.
+ :::note
+ You need to set the baseline to allocate credits.
+ :::
+ })
+1. In the credits calculator, enter the following:
+ * **Average daily ingestion**. Enter the average daily ingestion of the Flex data.
+ * **Estimated Scans per GB of ingested data**. Adjust the toggle bar to specify how many times you expect the data to be scanned.. The default setting is 500X, which means the 1 GB of ingested data will be scanned 500 times. You can set this number based on your analytic usage profile.
+ - Set the value between 500-750 if your analytic usage profile is **Low**.
+ - Set the value between 750-1500 if your analytic usage profile is **Medium**.
+ - Set the value between 1500-2000 if your analytic usage profile is **High**.
+ * **Traces Ingest**. Enter estimated daily ingestion of traces.
+ * **Metrics**. Enter estimated daily metric data points per minute (DPM) ingestion.})
+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 contract, 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. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Organizations**. })
+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 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.})
+ })
+
+ **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. 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.
+
+## 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
+
+This section has information about how you can monitor credit allocations and consumption across all your orgs, and for each child org. You can view the usage by orgs and child orgs on the **Account Overview** page.
+
+* The **Credit Allocation** tile indicates the total number of credits allocated.
+* The **Total Credit Usage** tile shows amount of credits consumed out of the total allocated credits.
+* The **Usage Forecast** tile indicates the total consumption of the credits by the end of contract period according to the current consumption rate.
+
+### View overall credit usage by category
+
+You can view the aggreagte usage for all child orgs across usage category in the **Overall Usage** tab on the **Account Overview** page. Usage for the following categories is shown:
+
+* **Flex Ingest**. Credits used for logs ingested into the Flex.
+* **Flex Scan Upfront**. Credits used for Flex scan upfront.
+* **Tracing Ingest**. Credits used for traces ingested.
+* **Metrics Ingest**. Credits used for metrics ingested.
+* **Data Forwarding**. For more information, see [Data Forwarding](/docs/manage/data-forwarding/).
+* **Storage**. Credits used for log storage in the Continuous and Frequent Tiers.
+* **Promotional categories**. For more information, see [Promotional Credits](sumo-logic-credits-accounts.md#promotional-credits).
+
+By clicking the **Download Report** button, you can download the org usage data in csv format for further analysis and reporting. You can also download the detailed child org usage data in csv format by clicking **Download Detailed Credit Usages** from the kebab icon next to the Download Report button.
+
+})
+
+### View child credit usage by category
+
+You can view the usage of individual child orgs in the **Child Orgs** tab on the **Account Overview** page. Usage for the following categories is shown:
+
+* The **Allocated Credits** column indicates the total number of credits allocated to the selected child org.
+* The **Total Credits Used** column indicates the total amount of credits consumed for the selected child org.
+* The **Usage %** column indicates the percentage of overall subscription credits that was allocated to a child org has been consumed.
+* The **Forecast** column indicates the percentage of total consumption of the credits by the end of contract period according to the current consumption rate for a selected child org.
+* The **Usage % Change** column indicates the difference in credit usage by your child organisations over time. For example, if you choose the date from Jan 1 to Jan 7, it will show the usage difference between Dec 25 to Dec 31 and Jan 1 to Jan 7 for each child organisation.
+
+By clicking the **Download Report** button, you can download the child org usage data in csv format for further analysis and reporting.
+
+})
+
+By clicking any of the selected child orgs, a side panel opens up in which you can view the individual usage for the following categories:
+
+* **Flex Ingest**. Credits used for logs ingested into the Flex.
+* **Flex Scan Upfront**. Credits used for Flex scan upfront.
+* **Tracing Ingest**. Credits used for traces ingested.
+* **Metrics Ingest**. Credits used for metrics ingested.
+* **Data Forwarding**. For more information, see [Data Forwarding](/docs/manage/data-forwarding/).
+* **Storage**. Credits used for log storage in the Continuous and Frequent Tiers.
+
+By clicking the **Download Report** button, you can download the selected child org usage data in csv format for further analysis and reporting.
+
+})
+
+## Access a child org
+
+If a [custom subdomain](manage-org-settings.md#set-up-a-customsubdomain) has been configured for a child org, and you have an account in the org, you can access it from the **Organizations** UI.
+
+1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Organizations**. })
+
+## View child credits usage
+
+You can access the child credits usage for a selected organization from the **Organizations** UI.
+
+1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Organizations**. })
+
+## 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. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Organizations**.
+1. To view the baseline, click **View Baseline**.})
+
+## Audit logging for organizations
+
+This section has examples of the messages Sumo Logic writes to the Audit Event Index when you create or update an org.
+
+### OrganizationCreated
+
+```
+{"operator":{"email":"PF6gIXhGj33LzP8Ba7kzJkL9EAtz6RuSMYHHKnqbEICUz7PITMdceGFRdQESZ2JwpL7BSbGaOaUYmgADz3USgExa7egWZ8UY2wmm","id":"000000000AEE3701","interface":"INTERNAL","sessionId":"no_session","sourceIp":"54.177.241.252","type":"UserContext"},"organizationIdentity":{"email":"pjain+1ljjjjjlwasdk@sumologic.com","organizationName":"akjdhfjkhwqiue","firstName":"kajsdfh","lastName":"sakjdsh","orgId":"000000000AF45F28","deploymentId":"nite"},"subscriptionDetails":{"startDate":{"year":2020,"month":12,"day":16},"endDate":{"year":2021,"month":5,"day":11},"plan":"SUMO-ENT-SUI","credits":4388,"baselines":{"continuousIngest":1,"continuousStorage":30,"frequentIngest":1,"frequentStorage":30,"infrequentIngest":1,"infrequentStorage":30,"infrequentScan":0,"metrics":1,"cseIngest":0,"cseStorage":0}},"eventType":"Audit","severityLevel":"Info","accountId":"000000000AE07391","eventId":"67718e94-a8a3-4478-b778-975cd0e18e55","eventName":"OrganizationCreated","eventTime":"2020-12-17T04:59:05.584Z","eventFormatVersion":"1.0 beta","subsystem":"organizations"}
+```
+
+### OrganizationUpdated
+
+```
+{"operator":{"email":"rmVOQ8CwUBuxqDydSLIV2ZljEogPcR7fwZiIShCBldZ5jhEl1c4wLHJhL1j6xkzVPVuqVJFf1c5VUvOMESv4ieY0xrxuVET6JXTw","id":"000000000B0858AE","interface":"INTERNAL","sessionId":"no_session","sourceIp":"122.181.102.148","type":"UserContext"},"organizationIdentity":{"email":"fkonkpjg3z@mail.peaksum.com","organizationName":"QEV9Z3Z","firstName":"ne3ieXF","lastName":"85lZdXD","orgId":"000000000AF35705","deploymentId":"nite"},"from":{"continuousIngest":200,"continuousStorage":30,"frequentIngest":200,"frequentStorage":30,"infrequentIngest":200,"infrequentStorage":30,"infrequentScan":0,"metrics":200,"cseIngest":0,"cseStorage":0},"to":{"continuousIngest":201,"continuousStorage":30,"frequentIngest":200,"frequentStorage":30,"infrequentIngest":200,"infrequentStorage":30,"infrequentScan":0,"metrics":200,"cseIngest":0,"cseStorage":0},"eventType":"Audit","severityLevel":"Info","accountId":"000000000AE07391","eventId":"2f816b83-3f10-434f-b5b9-e73aa223fd5d","eventName":"OrganizationUpdated","eventTime":"2020-12-16T11:29:53.428Z","eventFormatVersion":"1.0 beta","subsystem":"organizations"}
+```
diff --git a/docs/manage/manage-subscription/index.md b/docs/manage/manage-subscription/index.md
index 1ec367ab06..0fc77c0a70 100644
--- a/docs/manage/manage-subscription/index.md
+++ b/docs/manage/manage-subscription/index.md
@@ -47,6 +47,12 @@ In this section, we'll introduce the following concepts:
Learn how to group, provision, centrally manage, and monitor credits usage of multiple orgs.
+Learn how to create and manage multiple Sumo Logic Orgs with Flex data.
+