Merge pull request #2527 from surishubham/testmuCom

Testmu com

Author: surishubham

docs/analytics-dashboard-settings.md

@@ -44,18 +44,21 @@ The Analytics Dashboard Settings page provides a comprehensive set of controls t
 
 ---
 
-### Email Notification Settings
+### Email Notifications
 
 Keep your team informed about dashboard activity and test results by configuring email notifications.
 
 - **Enable/Disable Notifications:** Use the toggle to activate or deactivate email notifications for the dashboard. When disabled, no email updates will be sent.
-- **Notification Frequency:** Choose how often you want to receive email updates. Options typically include Daily, Weekly, or Custom intervals, allowing you to match your team's workflow.
-- **Date Range:** Select the default date range or specify a custom number of days to include in each notification. For example, setting a custom range to 7 will include data from the last 7 days in each email.
-- **Add Recipients:** Enter one or more email addresses to receive notifications. Click **Add** after each address to include multiple recipients. This is useful for keeping stakeholders, QA leads, or team members in the loop.
-- **Update & Save Preferences:** After configuring your preferences, click **Update** to save changes. Your notification settings will take effect immediately.
+- **Frequency:** Choose how often you want to receive email updates from the dropdown. Options include **Daily**, **Weekly**, or **Monthly**.
+- **Time & Period:** Set a specific delivery time for your scheduled reports. Select the hour from the **Time** dropdown (e.g., `9:00`) and choose **AM** or **PM** from the **Period** dropdown.
+- **Date Range:** Select **Default** to use the platform's default date range, or select **Custom** and specify a number of days. For example, setting a custom range to `7` includes data from the last 7 days in each email.
+- **Emails:** Enter one or more email addresses to receive notifications. Click **+ Add** after each address to include multiple recipients. This is useful for keeping stakeholders, QA leads, or team members in the loop.
+- **Update:** After configuring your preferences, click **Update** to save changes. Your notification settings will take effect immediately.
 
 > **Tip:** Use custom date ranges and recipient lists to tailor notifications for different teams or reporting needs.
 
+For a detailed guide on scheduling reports with custom delivery times, see [Report Scheduling](/docs/analytics-report-scheduling/).
+
 ---
 
 ### Slack Notification Settings

docs/analytics-report-scheduling.md

@@ -0,0 +1,157 @@
+---
+id: analytics-report-scheduling
+title: Schedule Analytics Widget Reports
+sidebar_label: Report Scheduling
+description: Customize the delivery time for your analytics widget reports. Schedule reports at your preferred time for timely business insights.
+keywords:
+  - analytics
+  - report scheduling
+  - widget reports
+  - scheduled reports
+  - analytics notifications
+url: https://www.testmuai.com/support/docs/analytics-report-scheduling/
+site_name: LambdaTest
+slug: analytics-report-scheduling/
+canonical: https://www.testmuai.com/support/docs/analytics-report-scheduling/
+---
+
+import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": BRAND_URL
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": `${BRAND_URL}/support/docs/`
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Report Scheduling",
+          "item": `${BRAND_URL}/support/docs/analytics-report-scheduling/`
+        }]
+      })
+    }}
+></script>
+
+Analytics report scheduling allows you to customize the delivery time for your dashboard widget reports. Instead of receiving reports at a fixed default time, you can choose a specific time that aligns with your team's workflow.
+
+## Overview
+
+With the customizable scheduling feature, you can:
+
+- Set a preferred delivery time for each dashboard's email reports.
+- Configure notification frequency (Daily, Weekly, or Monthly).
+- Choose the data range included in each report.
+- Manage email recipients for scheduled reports.
+
+## Prerequisites
+
+- You must be logged in to your <BrandName /> account.
+- You must have at least one [analytics dashboard](/docs/analytics-create-dashboard/) created.
+- You must be the dashboard creator or an admin user to modify scheduling settings.
+
+## Schedule a Report
+
+### Step 1: Open Dashboard Settings
+
+1. Navigate to your analytics dashboard.
+2. Click the **Settings** icon in the dashboard toolbar to open the **Dashboard Settings** panel.
+
+### Step 2: Enable Email Notifications
+
+In the **Dashboard Settings** panel, expand the **Email Notifications** section and toggle the switch to enable notifications for the dashboard.
+
+### Step 3: Set the Delivery Schedule
+
+1. Under **Frequency**, select your preferred schedule from the dropdown:
+   - **Daily** — Receive reports every day at your chosen time.
+   - **Weekly** — Receive reports once a week.
+   - **Monthly** — Receive reports once a month.
+
+2. Under **Time**, select the hour from the dropdown (e.g., `9:00`).
+
+3. Under **Period**, select **AM** or **PM** from the dropdown.
+
+### Step 4: Configure the Date Range
+
+Select the date range for the data included in each report:
+
+- **Default** — Uses the platform's default date range.
+- **Custom** — Specify a custom number of days. For example, setting this to `7` includes data from the last 7 days in each report.
+
+### Step 5: Add Recipients
+
+1. Under **Emails**, enter the email address in the **Enter Email address** field.
+2. Click **+ Add** to include the recipient.
+3. Repeat to add multiple recipients.
+
+### Step 6: Save Your Settings
+
+Click **Update** to save your scheduling preferences. The changes take effect immediately.
+
+:::tip
+Each dashboard has its own independent scheduling settings. You can configure different delivery times and recipients for different dashboards to match each team's needs.
+:::
+
+## Update an Existing Schedule
+
+1. Navigate to the dashboard whose schedule you want to modify.
+2. Open the **Dashboard Settings** panel.
+3. Adjust the frequency, time, period, date range, or recipients as needed.
+4. Click **Update** to save your changes.
+
+:::note
+When you update the delivery time for a dashboard, the new schedule applies only to that dashboard. Other dashboards retain their existing schedules.
+:::
+
+## Disable Scheduled Reports
+
+To stop receiving scheduled reports for a dashboard:
+
+1. Open the **Dashboard Settings** panel.
+2. Toggle the **Email Notifications** switch to the off position.
+3. Click **Update** to confirm.
+
+The notification preferences (time, recipients) are preserved so you can re-enable them later without reconfiguring.
+
+## Common Issues
+
+| Issue | Solution |
+|---|---|
+| Email notification toggle appears disabled | Ensure you have saved the dashboard after creation. Try refreshing the page and toggling again. |
+| Delivery time reverts after clicking Update | Verify you selected the time and period before clicking Update. If the issue persists, refresh the page and try again. |
+| Email toggle is not clickable when Custom date range is selected | This is a known issue. Switch to Default, enable the toggle, then switch back to Custom. |
+
+## Related Docs
+
+- [Create Your Custom Dashboard](/docs/analytics-create-dashboard/)
+- [Dashboard Settings](/docs/analytics-dashboard-settings/)
+- [Dashboard Features](/docs/analytics-dashboard-features/)
+
+<nav aria-label="breadcrumbs">
+  <ul className="breadcrumbs">
+    <li className="breadcrumbs__item">
+      <a className="breadcrumbs__link" target="_self" href={BRAND_URL}>
+        Home
+      </a>
+    </li>
+    <li className="breadcrumbs__item">
+      <a className="breadcrumbs__link" target="_self" href={`${BRAND_URL}/support/docs/`}>
+        Support
+      </a>
+    </li>
+    <li className="breadcrumbs__item breadcrumbs__item--active">
+      <span className="breadcrumbs__link">
+      Report Scheduling
+      </span>
+    </li>
+  </ul>
+</nav>

docs/deep-dive-into-hyperexecute-yaml.md

@@ -952,14 +952,10 @@ alwaysRunPostSteps: true
 
 This flag is used to set the Name of your Projects which would later allow you to see all jobs of that Project at one place. To know more about Projects [click here](/support/docs/hyperexecute-projects).
 
-```yaml
-project:
-  name: 'demo-project' #project name
-```
-
 :::info note
-Once you have created a project, you can either pass in your `project ID` or `project name` to trigger your job on the same project.
-
+- Once you have created a project, you can pass in your project ID and project name to trigger your job on the same project.
+- If you are using   [**Project Level Secrets**](/support/docs/hyperexecute-how-to-manage-project-level-secrets/), you must include the id field in your project configuration.                                              
+:::
 ```yaml
 project:
   name: 'demo-project' #project name

docs/hyperexecute-how-to-manage-project-level-secrets.md

@@ -45,7 +45,7 @@ Secrets in <BrandName /> HyperExecute are encrypted environment variables used t
 Managing sensitive information like API tokens, credentials, and access keys is crucial when running tests in <BrandName /> HyperExecute. To address this, HyperExecute offers a Secrets Management system, and one of its powerful features is Project Level Secrets. This feature lets you define secrets scoped to a specific project, making secret handling more secure, easier, and collaborative for your teams.
 
 ## What Are Project Level Secrets?
-Project-level secrets are bound to a specific HyperExecute project instead of a user or account. When a job runs using that project (referenced by name or id in the YAML configuration, which is a sub-parameter of project parameter), the project-level secrets are automatically available to the test environment.
+Project-level secrets are bound to a specific HyperExecute project instead of a user or account. When a job runs using that project ( referenced by id or both id and name in the YAML configuration, which are sub-parameters of project parameter), the project-level secrets are automatically available to the test environment.
 
 ### Key Points
 - Define secrets once per project.
@@ -76,7 +76,9 @@ runson: linux
 autosplit: true
 concurrency: 2
 
-project: your-project-name
+project:
+  name: 'demo-project' 
+  id: '1abc2345-56de-7890-f1cg-h2ij34k56789' 
 
 # highlight-start
 env:

docs/support-access.md

@@ -46,7 +46,9 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
 ***
 The Support Access feature allows <BrandName /> to take access to your <BrandName /> account and log in on your behalf from the backend. By granting access to your account, our team can help you with debugging issues or do activities on your behalf. You can revoke this access anytime
 
-
+:::tip Quick Link
+You can directly navigate to the Support Access page by this [**link**](https://accounts.lambdatest.com/support).
+:::
 ## Granting Support Access
 ***
 

sidebars.js

@@ -3883,6 +3883,7 @@ module.exports = {
         "analytics-widget-filter-by-regex",
         "analytics-filter-by-custom-data",
         "analytics-dashboard-settings",
+        "analytics-report-scheduling",
       ],
     },
     {