Merge branch 'main' into patch-1

docs/dev/api/storage.md

@@ -1194,15 +1194,15 @@ values={[
 
 ```jsx title="Sample Request"
 curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
---request GET 'https://api.us-west-1.saucelabs.com/v1/icons/<icon_hash>' --output icon.png
+--request GET 'https://api.us-west-1.saucelabs.com/v1/storage/icons/<icon_hash>' --output icon.png
 ```
 
 </TabItem>
 <TabItem value="eu">
 
 ```jsx title="Sample Request"
 curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
---request GET 'https://api.eu-central-1.saucelabs.com/v1/icons/<icon_hash>' --output icon.png
+--request GET 'https://api.eu-central-1.saucelabs.com/v1/storage/icons/<icon_hash>' --output icon.png
 ```
 
 </TabItem>
@@ -1264,15 +1264,15 @@ values={[
 
 ```jsx title="Sample Request"
 curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
---request GET 'https://api.us-west-1.saucelabs.com/v1/tags'
+--request GET 'https://api.us-west-1.saucelabs.com/v1/storage/tags'
 ```
 
 </TabItem>
 <TabItem value="eu">
 
 ```jsx title="Sample Request"
 curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
---request GET 'https://api.eu-central-1.saucelabs.com/v1/tags'
+--request GET 'https://api.eu-central-1.saucelabs.com/v1/storage/tags'
 ```
 
 </TabItem>
@@ -1351,15 +1351,15 @@ values={[
 
 ```jsx title="Sample Request"
 curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
---request GET 'https://api.us-west-1.saucelabs.com/v1/projects'
+--request GET 'https://api.us-west-1.saucelabs.com/v1/storage/projects'
 ```
 
 </TabItem>
 <TabItem value="eu">
 
 ```jsx title="Sample Request"
 curl -u "$SAUCE_USERNAME:$SAUCE_ACCESS_KEY" --location \
---request GET 'https://api.eu-central-1.saucelabs.com/v1/projects'
+--request GET 'https://api.eu-central-1.saucelabs.com/v1/storage/projects'
 ```
 
 </TabItem>

docs/dev/cli/virtual-usb/start-session.md

@@ -109,10 +109,15 @@ Specify a proxy password to be set on the device.
 <div className="cli-desc">
 <p><small>| OPTIONAL | STRING |</small></p>
 
-The name of an active [Sauce Connect](/secure-connections/sauce-connect/) tunnel to use for secure connectivity to the Sauce Labs platform.
+Specifies the name of an active [Sauce Connect](/secure-connections/sauce-connect/) tunnel to use for secure connectivity to the Sauce Labs platform.   
+Use the `--tunnelIdentifier` option with the tunnel identifier in the format:
+```java title="tunnel identifier format"
+--tunnelIdentifier tunnel-identifier:<tunnel-name>,<tunnel-owner>
+```    
 
 :::note Identifying a Tunnel
-The value expected here is the value shown under the **Tunnel Name** column on the Sauce Labs Tunnels page, not the Tunnel ID numerical value.
+- `tunnel-name`: The value expected here is the value shown under the **Tunnel Name** column on the Sauce Labs Tunnels page, not the Tunnel ID numerical value.
+- `tunnel-owner`: The name of the tunnel owner. This is the value shown under the **Owner** column on the Sauce Labs Tunnels page.   
 :::
 
 </div>
@@ -141,5 +146,5 @@ java -jar virtual-usb-client.jar startSession \
     --deviceName iPhone_XS \
     --serverHost http://127.0.0.1 \
     --serverPort 8080 \
-    --tunnelIdentifier my-tunnel
+    --tunnelIdentifier tunnel-identifier:my-tunnel,my-owner
 ```

docs/dev/test-configuration-options.md

@@ -718,7 +718,7 @@ If set to `true` it prevents the device from resetting before the session startu
 
 **For Real Devices:**
 
-Set `noReset` to `true` to keep a device allocated to you during the device cleaning process, as described under [`cacheId`](#`cacheId`), allowing you to continue testing on the same device. Default value is `false`. To use `noReset`, you must pair it with `cacheId`.
+Set `noReset` to `true` to keep a device allocated to you during the device cleaning process, as described under [`cacheId`](#cacheid), allowing you to continue testing on the same device. Default value is `false`. To use `noReset`, you must pair it with `cacheId`.
 
 **For Virtual Devices:**
 
@@ -1378,7 +1378,7 @@ If [`noReset`](#noreset) is also set to `true`, the app under test and its data
 Changing [`noReset`](#noreset) has no impact here. The app will not be removed, will stay on the phone/tablet and will keep it's state. This is caused by the re-signing process of the app.
 :::
 
-If you are running multiple test suites in parallel, the values for `cacheId` should be unique for each suite (to avoid mixing up the devices), and the value for `cacheId` must be the same for all test methods that you want to run on the cached device. In addition, the app and project ID used for the tests must remain the same, along with the values for these capabilities:
+If you are running multiple test suites in parallel, the values for `cacheId` should be unique for each suite (to avoid mixing up the devices), and the value for `cacheId` must be the same for all test methods that you want to run on the cached device. The value itself can be any (random) string. In addition, the app and project ID used for the tests must remain the same, along with the values for these capabilities:
 
 - `platformName`
 - `appium:deviceName`

docs/insights/coverage.md

@@ -7,21 +7,18 @@ description: See a breakdown of the browser and device variations covered by you
 
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-The Coverage report allows Org Admins to view and download the breakdown of browsers and mobile devices the tests across their organization have run against. Having insight into your coverage data helps companies:
+The Coverage report allows you to view and download the breakdown of browsers and mobile devices the tests across their organization have run against. Having insight into your coverage data helps companies:
 
 - See at a glance whether their testing is in sync with the environments in which it is most often accessed
 - Evaluate how evenly tests are being distributing across browsers and devices
 - Design their test strategy to keep up with newly released browser and device versions
 - Utilize their concurrency to spread testing across test environments for greater efficiency and comprehensiveness
 
-:::note Org Admins Only
-You must have [Org Admin](/basics/acct-team-mgmt/managing-user-info/#user-roles) privileges for your organization in order to view and download coverage data.
-:::
 
 ## Accessing the Coverage Reports
 
 1. Click the **Insights** tab to expand its submenu.
-1. Click **Coverage** (only visible to Org Admin users).
+1. Click **Coverage**.
 1. Specify the type of coverage you wish to view by selecting the **Devices**, **Browsers** or **OS** tab.
 1. If you choose **Devices** or **OS**, specify wheter you wish to see coverage data for:
    - **Virtual Cloud** tests: desktop web-apps, mobile emulators and simulators.