diff --git a/src/components/navcards.jsx b/src/components/navcards.jsx index 1b96956f..ec562851 100644 --- a/src/components/navcards.jsx +++ b/src/components/navcards.jsx @@ -134,7 +134,7 @@ const data = [ id: 22, title: "Contributing", description: "Contribute to Testsigma community.", - path: "/docs/api/overview/", + path: "/docs/contributing/open-source-dev-environment-setup/macos-and-intellij-ce/", }, { id: 23, diff --git a/src/pages/docs/on-premise-setup/sla.md b/src/pages/docs/on-premise-setup/sla.md deleted file mode 100644 index cc169875..00000000 --- a/src/pages/docs/on-premise-setup/sla.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -title: "Service Level Agreement for customer" -order: 26.2 -page_id: "Service Level Agreement" -metadesc: "Service Level Agreement for customer by Testsigma | This effective Service Level Agreement is made by and between Testsigma company and client" -noindex: false -search_keyword: "" -warning: false ---- - - -
-
- -|**Document Owner**|**Testsigma Technologies Inc.**| -|---|---| - -## **1. Agreement Overview** -This Service-Level Agreement (this "Agreement" or this "Service-Level Agreement"), effective as of [Effective date], ("Effective Date") is made by and between [Client. Company], a company organized and existing in [Client. State], with offices located at [Client. Address] ("Customer") and ***Testsigma*** [Supplier. Company], a company organized and existing in [Supplier. State], with offices at **Testsigma Technologies Inc., 355 Bryant Street, Suite 403, San Francisco, CA 94107** [Supplier. Address] ("Supplier"). - -This Agreement remains valid until mutually endorsed by the stakeholders. - -## **2. Goals & Objectives** -This Agreement **aims** to obtain a mutual Agreement between the Service Provider(s) and Customer(s).
-The **objectives** of this Agreement are to
- -## **3. Stakeholders** -The following Service Provider(s) and Customer(s) will be used as the basis of the Agreement and represent the **primary stakeholders** associated with this SLA:
-**Service Provider(s): Testsigma Technologies Inc.**(“Provider”)
-**Customer(s):** (“Customer”) - -## **4. Periodic Review** -The terms stated in the Agreement shall be valid from the Effective Date. The revisions to this agreement shall be carried out every fiscal year. However, during the revision, the current Agreement shall be considered valid.
-**Business Relationship Manager: Amit Wadekar**
-**Review Period:** - -## **5. Service Agreement** -The following are the responsibility of the Service Provider in the ongoing support of this Agreement.
-### a. Service Scope -This Agreement covers the following Services;
- -[[info | **NOTE**:]] -|The support helpdesk does not cover the following: -|
  • Any enhancement requests by the customer -|
  • Network devices managed by the customer - -### b. Customer Requirements -Customer responsibilities and requirements in support of this Agreement include:
    - -### c. Service Provider Requirements -Service Provider responsibilities and/or requirements in support of this Agreement include:
    - -### d. Service Assumptions -Assumptions related to in-scope services and/or components include:
    - -### e. Security Assumptions -Zero dependability of data leakage: If any data leakage happens via application while accessing the API for 2FA functionality, Testsigma would own responsibility for the same. However, for any data leakage happening via the ("Customer") network or outside the product, Testsigma would not be responsible. - -## **6. Service Management** -For maintaining adequate customer-support levels, this Agreement lists the available scope of services the Service Provider provides. This list details availability, monitoring, and other relevant factors. - -### a. Service Availability -Coverage parameters specific to the service(s) covered in this Agreement are as follows: -
  • Email support: Monitored 24-hour support from Monday – Friday.
    -
  • Chat support: Monitored 24-hour support from Monday – Friday.
    - -### b. Service Requests -In support of services outlined in this Agreement, the Service Provider will respond to service-related incidents and/or requests submitted by the Customer within the following time frames: - -|**Support Request Classification**|**Description - Any service error comprising or causing any of the following events or effects**| -|---|---| -|Critical Service Error|Issue affecting the entire system or single critical production function. System down or operating in a materially degraded state or Widespread access interruptions.| -|High Service Error|Primary component failure that materially impairs its performance or Data entry or access is materially impaired on a limited basis.| -|Medium Service Error|Hosting Services operate with minor issues that can be addressed with a workaround.| -|Low Service Error|Request for assistance, information, routine services, or updates that are desired but do not impair system operation or functionality.| - -|**Support Request Classification**|**Response Time**|**Resolution Time (Provide workaround to unblock)**| -|---|---|---| -|Critical Service Error|60 minutes|~| -|High Service Error|2 hours|~| -|Medium Service Error|6 hours|~| -|Low Service Error|24 hours|~| - -[[info | **NOTE**:]] -| The SLA is subject to the availability of resources at the client site. Resolution time cannot be stated as it depends on access availability. - -## **6. Upgrades / New Release** -**a. Upgrades:** All new upgrades will be pushed quarterly. The version will not be in sync with the cloud version, and there will be a delay while the features are released for the on-prem setup.
    -**b. Hotfix / Patch:** If a blocker in the product halts the production environment for the customer, then a hotfix will be released and shared with the customer.
    -**c. Beta access:** On-premise setup will have access to a limited set of beta functionalities as any reported issue will not be prioritized and might also break the existing setup. - ---- \ No newline at end of file