Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions src/left-nav-title.json
Original file line number Diff line number Diff line change
Expand Up @@ -487,7 +487,7 @@
"/docs/configuration/api-keys/": "API Keys"
},
"security": {
"/docs/configuration/security/": "Security(SSO)"
"/docs/configuration/security/": "Security"
},
"api": {
"/docs/api/": "Testsigma REST APIs"
Expand Down Expand Up @@ -755,5 +755,9 @@
"jira": {"/docs/integrations/bug-reporting/jira/": "Jira" },
"jira": {"/docs/atto/generative-ai/integrations/jira/": "Jira"},
"xray": {"/docs/atto/generative-ai/integrations/xray/": "Xray"},
"qtest": {"/docs/atto/generative-ai/integrations/qtest/": "qTest"}
"qtest": {"/docs/atto/generative-ai/integrations/qtest/": "qTest"},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Duplicate key causes navigation mapping loss.

The key "qtest" is already defined at lines 700, 732, and 753. JSON does not allow duplicate keys at the root level—most parsers will only retain the last occurrence, causing earlier navigation entries to become unreachable.

Consolidate all qtest paths under a single key:

-  "qtest": {"/docs/integrations/test-management/qtest/": "qTest"},
+  "qtest": {
+    "/docs/integrations/test-management/qtest/": "qTest",
+    "/docs/atto/generative-ai/integrations/qtest/": "qTest"
+  }

Apply the same consolidation for lines 732 and 753, then remove the duplicate entry at line 758.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In src/left-nav-title.json around lines 700, 732, 753 and 758, the root key
"qtest" is duplicated which causes earlier mappings to be lost; consolidate all
mappings for "qtest" into a single "qtest" entry that contains every referenced
path->label pair from the entries at lines 700, 732, 753 and 758, then remove
the duplicate "qtest" entries so only one combined "qtest" key remains; ensure
the merged entry preserves all unique paths and labels exactly as they appeared.

"user-settings": {"/docs/configuration/user-settings/": "User Settings" },
"google-sso": {"/docs/configuration/security/google-sso/": "Setting Up Google SSO Login" },
"okta-sso": {"/docs/configuration/security/okta-sso/": "Setting Up Okta SSO Login (SAML)" },
"azure-sso": {"/docs/configuration/security/azure-sso/": "Setting Up Azure SSO Login (SAML)" }
}
4 changes: 2 additions & 2 deletions src/pages/docs/configuration/security/azure-sso.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@ title: "Setting up SAML-based SSO login for Testsigma in Azure"
page_title: "Setting up SAML-based Single Sign-On (SSO) for Testsigma with Azure AD"
metadesc: "Learn how to Set up SAML-based SSO login for Testsigma in Azure. With Azure Active Directory, users can automatically sign into their cloud-hosted/on-premise apps "
noindex: false
order: 19.24
page_id: "Set up SAML-based SSO login for Testsigma in Azure"
order: 19.27
page_id: "setting-up-azure-sso-with-saml-in-testsigma"
search_keyword: ""
warning: false
contextual_links:
Expand Down
4 changes: 2 additions & 2 deletions src/pages/docs/configuration/security/google-sso.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@ title: "Setting Up Google Single Sign-On(SSO) Login in Testsigma"
page_title: "Setting up Google Single Sign-On (SSO) login"
metadesc: "Learn how to set up Single Sign-On (SSO) with Google in Testsigma. With Google SSO, you are not required to store and manage passwords for the websites."
noindex: false
order: 19.22
page_id: "Setting up Google Single Sign-On(SSO) login in Testsigma Application."
order: 19.25
page_id: "google-sso"
search_keyword: ""
warning: false
contextual_links:
Expand Down
4 changes: 2 additions & 2 deletions src/pages/docs/configuration/security/okta-sso.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,8 @@ title: "Setting Up Okta Single Sign-On Integration with SAML Login in Testsigma"
page_title: "Configuring Okta SSO Integration with SAML in Testsigma"
metadesc: "Single Sign-On (SSO) provides faster, easier, and trusted access to applications. Learn how to set up Single Sign-On (SSO) with SAML login easily in Testsigma."
noindex: false
order: 19.23
page_id: "setting-up-okta-sso-with-saml--in-testsigma"
order: 19.26
page_id: "setting-up-okta-sso-with-saml-in-testsigma"
search_keyword: ""
warning: false
contextual_links:
Expand Down
63 changes: 63 additions & 0 deletions src/pages/docs/configuration/security/org-settings.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: "Configure Organization Settings"
metadesc: "Organization Settings allow administrators to manage authentication and security configurations for the organization | Learn how to configure organization settings in Testsigma"
noindex: false
order: 19.22
page_id: "organization-settings"
search_keyword: ""
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Password Policy"
url: "#password-policy"
- type: link
name: "Single Sign-On (SSO)"
url: "#single-sign-on-sso"
- type: link
name: "Supported SSO Providers"
url: "#supported-sso-providers"
---

---

Organization Settings allow administrators to manage authentication and security configurations for the organization. These settings define how users access Testsigma and help enforce consistent security standards across the organization.

This article discusses an overview of organization-level security settings, including Password Policy and Single Sign-On (SSO).

---

> <p id="prerequisites">Prerequisites</p>
> Before you begin, ensure that:
> - You have an active Testsigma account with administrator access.
> - You have access to the Single Sign-On (SSO) identity provider you plan to use.

---

## **Password Policy**

Password Policy allows organization administrators to configure password-related security controls for user accounts.

To learn how to configure password policies, see [Configure Password Policy](https://testsigma.com/docs/configuration/security/password-policy/).

---

## **Single Sign-On (SSO)**

Single Sign-On (SSO) allows users to authenticate using an external identity provider and enforces SSO-based access to the organization.

---

## **Supported SSO Providers**
Testsigma supports the following Single Sign-On (SSO) providers:
- [Google Single Sign-On](https://testsigma.com/docs/configuration/security/google-sso/)
- [SAML-based Single Sign-On (Okta)](https://testsigma.com/docs/configuration/security/okta-sso/)
- [SAML-based Single Sign-On (Azure)](https://testsigma.com/docs/configuration/security/azure-sso/)
- **SAML-based Single Sign-On (OneLogin)**
- **SAML-based Single Sign-On (Google Workspace)**

---
63 changes: 37 additions & 26 deletions src/pages/docs/configuration/security/overview.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: "Single Sign-on Options Available in Testsigma"
metadesc: "Setting up of all SSO types supported in Testsigma Application. With SSO, there's no need to store and manage passwords for the websites."
title: "Security Settings in Testsigma"
metadesc: "Security settings allow you to manage authentication, access control, and account security for the organization | Learn about security features available in Testsigma"
noindex: false
order: 19.21
page_id: "Single Sign-on options available in Testsigma"
page_id: "security-settings-in-testsigma"
search_keyword: ""
warning: false
contextual_links:
Expand All @@ -13,54 +13,65 @@ contextual_links:
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Single Sign-on Options Available"
url: "#single-sign-on-options-available"
name: "Organization Settings"
url: "#organization-settings"
- type: link
name: "Steps to Enable SSO in Testsigma"
url: "#steps-to-enable-sso-in-testsigma"
name: "Two-Factor Authentication (2FA)"
url: "#two-factor-authentication-2fa"
- type: link
name: "Password Policy"
url: "#password-policy"
- type: link
name: "Single Sign-On (SSO)"
url: "#single-sign-on-sso"
---

---

Single Sign-On (SSO) is an authentication process that allows you to access an application with a single login credentials. Testsigma allows SSO login to access the application. This article discusses SSO options available in Testsigma.
Security settings allow you to manage authentication, access control, and account security for the organization. These settings help ensure that only authorized users can access Testsigma and that access follows the organization’s security requirements. This article provides an overview of the security features available in Testsigma.

---


> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that you have an active Testsigma account.
> Before configuring security settings, ensure that:
> 1. You have an active Testsigma account with administrator access.
> 2. You have access to the identity provider required for the security feature you want to configure.

---

## **Single Sign-on Options Available**
## **Organization Settings**

Organization Settings allow administrators to manage organization-level authentication and security configurations, including Password Policy and Single Sign-On (SSO).

For details, see [Configure Organization Settings](https://testsigma.com/docs/configuration/security/org-settings/).

1. Google Single Sign On
![google cloud log](https://docs.testsigma.com/images/security/google-cloud-logo.png)
---

## **Two-Factor Authentication (2FA)**

2. SAML 2.0 based SSO - Okta, OneLogin, Azure AD e.t.c
![okta logo](https://docs.testsigma.com/images/security/okta-logo.png)
![onelogin logo](https://docs.testsigma.com/images/security/onelogin-logo.png)
![microsoft azure logo](https://docs.testsigma.com/images/security/microsoft-azure-logo.png)
Two-Factor Authentication provides an extra layer of security by requiring users to verify their identity using a second factor during sign-in.

## **Steps to Enable SSO in Testsigma**
For configuration steps, see [Two-Factor Authentication (2FA)](https://testsigma.com/docs/configuration/security/setup-two-factor-authentication/).

1. Navigate to your profile and click **Switch Account**.
---

2. Click **Settings** under the **Others** section on the home screen.
## **Password Policy**

3. In the **Settings** panel, scroll down to **Organization Settings** and click **Security (SSO)**.
Password Policy allows administrators to define password-related security controls for user accounts, such as session timeout, login attempt limits, and password change requirements.

4. In the **Single Sign-On (SSO)** settings, you can enable the SSO depending on your provider.
To learn how to configure password policies, see [Configure Password Policy](https://testsigma.com/docs/configuration/security/password-policy/).

![enable sso](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/sso/SAML_image.1.png)
---

Follow one of the links below to set up SSO depending on your provider:
## **Single Sign-On (SSO)**

**-** [Documentation on setting up Google Single Sign-On (SSO) login in Testsigma](https://testsigma.com/docs/configuration/security/google-sso/).
Single Sign-On (SSO) allows users to authenticate using an external identity provider and enforces SSO-based access to the organization.

**-** [Documentation on setting up SAML-based SSO login - Okta](https://testsigma.com/docs/configuration/security/okta-sso/).
For details, see:
- [Google Single Sign-On](https://testsigma.com/docs/configuration/security/google-sso/)
- [SAML-based Okta Single Sign-On](https://testsigma.com/docs/configuration/security/okta-sso/)
- [SAML-based Single Sign-On (Azure)](https://testsigma.com/docs/configuration/security/azure-sso/)

**-** [Documentation on setting up SAML-based SSO login - Azure](https://testsigma.com/docs/configuration/security/azure-sso/).
---
52 changes: 52 additions & 0 deletions src/pages/docs/configuration/security/password-policy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
title: "Configure Password Policy"
metadesc: "Password Policy allows organization administrators to configure password-related security controls for user accounts. | Learn how to configure password policy in Testsigma"
noindex: false
order: 19.24
page_id: "password-policy"
search_keyword: ""
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Configure Password Policy"
url: "#configure-password-policy"
---

---

Password Policy allows organization administrators to configure password-related security controls for user accounts. These settings manage session behavior, limit failed login attempts, and enforce periodic password changes across the organization. This article discusses configuring the password policy settings in Testsigma.

---

> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that you have an active Testsigma account.
Comment on lines +26 to +28
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Consider enhancing prerequisites to reflect administrator-only access.

The prerequisite currently only requires an active account. However, password policy configuration is an administrative function. The related overview.md file (line 39) specifies "administrator access" as a prerequisite. Align this documentation for consistency.

 > <p id="prerequisites">Prerequisites</p>
 > 
-> Before you begin, ensure that you have an active Testsigma account.
+> Before you begin, ensure that:
+> 1. You have an active Testsigma account with administrator access.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that you have an active Testsigma account.
> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that:
> 1. You have an active Testsigma account with administrator access.
🤖 Prompt for AI Agents
In src/pages/docs/configuration/security/password-policy.md around lines 26 to
28, the prerequisites text currently requires only an active Testsigma account
but this is an admin-only setting; update the prerequisite to require an active
Testsigma account with administrator access (or explicit administrator
privileges) to match overview.md and ensure wording is consistent with the
related docs.


---

## **Configure Password Policy**

1. Under **Organization Settings**, click **Password Policy**.
![Password Policy](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Org_Settings_Password_Policy.png)

2. Click **Configure**. This will open the **Configure Password Policy** dialog.
![Configure](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Configure_Password_Policy.png)

3. In the **Configure Password Policy** dialog, select each setting you want to enable.
![Configure Password Policy](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Options_for_Policy.png)

4. For each selected setting, enter the required value in the corresponding field:
- **Idle Session Timeout (minutes)**: Enter the number of minutes after which inactive users are automatically signed out.
- **Max Failed Login Attempts**: Enter the maximum number of consecutive failed login attempts allowed before the account is locked.
- **Password Change Frequency (days)**: Enter how often users must change their passwords.
![Options & Values](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Options_and_Values_for_Policy.png)

5. Click **Update** to save your changes.
![Update Policy Options](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Update_Policy_Options.png)

---
Original file line number Diff line number Diff line change
@@ -0,0 +1,59 @@
---
title: "Two-Factor Authentication (2FA)"
metadesc: "Two-Factor Authentication (2FA) is a security feature that requires two forms of verification to access your Testsigma account | Learn how to configure 2FA for Testsigma account"
noindex: false
order: 19.23
page_id: "two-factor-authentication"
search_keyword: ""
warning: false
contextual_links:
- type: section
name: "Contents"
- type: link
name: "Prerequisites"
url: "#prerequisites"
- type: link
name: "Single Sign-on Options Available"
url: "#single-sign-on-options-available"
- type: link
name: "Enable SSO in Testsigma"
url: "#enable-sso-in-testsigma"
---

---

Two-Factor Authentication (2FA) is a security feature that requires two forms of verification to access your Testsigma account. When 2FA is enabled, users must enter a one-time authentication code in addition to their username and password. This provides an added layer of protection for your account. This article discusses setting up Two-Factor Authentication for your Testsigma account.

---

> <p id="prerequisites">Prerequisites</p>
>
> Before you begin, ensure that you have an authenticator app for your organization.

---

## **Enable Two-Factor Authentication**

1. Click **2FA** under **User Settings**.
![2FA](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/2FA_Button.png)

2. Turn on the **Two-Factor Authentication** toggle. This will open the **Confirm Your Password** dialog.
![2FA Toggle](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/2FA_Toggle_Enable.png)

3. In the **Confirm Your Password** dialog, enter your password, and click **Continue**. This will open the **Set Up Authenticator App** dialog.
![Confirm Your Password](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Continue_with_2FA.png)

4. In the **Set Up Authenticator App** dialog, scan the QR code or enter the setup key in your authenticator app.
![QR Code](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/QR_Code_for_2FA.png)

5. Click **Continue**. This will open the **Verify Authenticator App** dialog.
![Continue after QR Code](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Contiune_After_QR_Code.png)

6. In the **Verify Authenticator App** dialog:
- Enter the 6-digit code from your authenticator app.
- Click **Continue**.
![Continue after entering Authenticator Code](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Continue_after_entering_Authenticator_Code.png)

7. You have now successfully enabled **Two-Factor Authentication** for your Testsigma account.

---
Loading