Update concurrency-limits.md

Updates to include information about team-level CCY management and adding the end of support date for Queueing.

- updated that org admins can view and adjust team ccy
-removed the information about usage as we are launching the new Usage Analytics under Insights
- added steps that describe how to set team limits
- added a Caution element to inform users about the end of support for Queuing
- minor grammatical mistake corrections

docs/basics/acct-team-mgmt/concurrency-limits.md

@@ -1,24 +1,22 @@
 ---
 id: concurrency-limits
 title: Concurrency Limits and Team Accounts
-sidebar_label: Concurrency Limits and Team Accounts
+sidebar_label: Concurrency Limits and Allocations for Teams
 ---
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
 <p><span className="sauceGreen">Enterprise Plans only</span></p>
 
-If your organization has multiple teams sharing a Sauce Labs account, it's important to monitor your concurrency limits--the number of virtual machines that you can run tests on simultaneously. You'll need to ensure that your organization's concurrency is distributed among your accounts.
+If your organization has multiple teams sharing a Sauce Labs account, you can use Team Limits to ensure that your organization's concurrency is distributed among different teams.
 
-If you are an org admin, you can view your organization's concurrency limits:
+If you are an org admin, you can view and control your organization's concurrency limits:
 
 1. In Sauce Labs, click **ACCOUNT** and then click **Team Management**.
 
 <img src={useBaseUrl('img/team-mgmt/team-mgmt-nav.png')} alt="Team management navigation" width="300"/>
 
-2. On the **Organization Management** page, under the ORGANIZATION NAME box, concurrency limits will be displayed for the selected data center. You can also view the **PEAK VM CONCURRENCY** and **VM TESTS BY DAY** for the organization.
-
-<img src={useBaseUrl('img/team-mgmt/ccy-limits-org-mgmt.png')} alt="Org management concurrency limits" width="600"/>
+2. On the **Organization Management** page, under the ORGANIZATION NAME box, concurrency limits will be displayed for the selected data center. 
 
 3. To view the limits for another data center, in the upper-right corner of the window, click the **DATA CENTER** dropdown and select the relevant data center.
 
@@ -28,11 +26,16 @@ If you are an org admin, you can view your organization's concurrency limits:
 
 <img src={useBaseUrl('img/team-mgmt/ccy-limits-teams.png')} alt="Team concurrency limits" width="600"/>
 
-For more information about usage, see [Viewing and Exporting Usage Data](/basics/acct-team-mgmt/viewing-exporting-usage-data/).
+For more usage information, see [Viewing and Exporting Usage Data](/basics/acct-team-mgmt/viewing-exporting-usage-data/).
+
+5. To allocate concurrency to teams, click on the team name to open the Teams tab.
+
+6. Under the Teams tab, Enter **Team VM Concurrency** and click on Update.
 
-## How Concurrency Limits Work
 
-Through Sauce Labs, organization admins set the total concurrency of their organization's account. When setting the concurrency limit for a team, be mindful that team members share the concurrency limit of the team. If a team exceeds its concurrency limit, any additional tests will be queued (see [Queueing Tests](#queueing-tests) for more information).
+## How Concurrency Allocation Works
+
+Through Sauce Labs, organization admins set the total concurrency of their organization's account. When setting the concurrency limit for a team, be mindful that team members share the concurrency limit of the team. If a team exceeds its concurrency limit, any additional tests will be queued. Be informed that queuing will be disabled from March 1st, 2024. 
 
 #### Example - Org Limits
 
@@ -42,15 +45,7 @@ When Team A is using all 250 concurrency slots, that only leaves 250 of the orga
 
 #### Example - Team Limits
 
-An org admin allocates 100 VMs to Team A, which has five members. Since the members of a team share the team's VM limit, the number of concurrent tests being run by the five team members cannot exceed 100. However, concurrency limits cannot be set at the user level, so User A could be running 20 tests, while user B is running 50 tests, and users C, D, and E are running 10 tests each. Or User A could be running 100 tests while Users B, C, D, and E are not running any tests.
-
-## Queueing Tests
-
-As tests complete, queued tests are allocated to concurrency slots in the order they were queued.
-
-If you run more tests at once than your concurrency allows (e.g., you have a concurrency of 100 but send 200 tests at once), the extra tests will be queued and run as the first tests finish. A test is only allowed to remain in the queue for 10 minutes. If it has not been moved out of the queue before 10 minutes elapse, or if too many tests are already queued, the test is removed from the queue and not run at all.
-
-Queuing is intended to deal with small mistakes in concurrency management. Sauce Labs does not recommend queuing tests intentionally.
+An organization admin allocates 100 VMs to Team A, which has five members. Since the members of a team share the team's VM limit, the number of concurrent tests being run by the five team members cannot exceed 100. However, concurrency limits cannot be set at the user level, so User A could be running 20 tests, while user B is running 50 tests, and users C, D, and E are running 10 tests each. Or User A could be running 100 tests while Users B, C, D, and E are not running any tests.
 
 ## Checking Concurrency
 
@@ -61,3 +56,17 @@ curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
 --request GET 'https://api.us-west-1.saucelabs.com/rest/v1.2/users/<username>/concurrency' \
 --header 'Content-Type: application/json' \ | json_pp
 ```
+
+:::caution
+
+Queuing will be disabled on March 1st, 2024. To better manage your usage, check the [Usage Analytics](https://docs.saucelabs.com/dev/api/usage/) that Sauce Labs provides for you 
+
+:::
+
+## Queueing Tests
+
+As tests are complete, queued tests are allocated to concurrency slots in the order they were queued.
+
+If you run more tests at once than your concurrency allows (e.g., you have a concurrency of 100 but send 200 tests at once), the extra tests will be queued and run as the first tests finish. A test is only allowed to remain in the queue for 10 minutes. If it has not been moved out of the queue before 10 minutes elapse, or if too many tests are already queued, the test is removed from the queue and not run at all.
+
+Queuing is intended to deal with small mistakes in concurrency management. Sauce Labs does not recommend queuing tests intentionally.