Added a new doc 'Configure User & Org Settings'

[bharathk08]

Added a new doc 'Configure User & Org Settings'

Summary by CodeRabbit

• Documentation
  • Added comprehensive guide on managing user and organization security settings, including profile management, password changes, two-factor authentication setup, password policies, and single sign-on configuration.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Added a new documentation page for managing user and organization settings in Testsigma, including a corresponding navigation entry in the left-nav configuration to direct users to the guide.

Changes

Cohort / File(s)	Summary
Navigation Configuration src/left-nav-title.json	Added new navigation entry "manage-user-and-organization-settings" mapping to the documentation path with display label "User & Organization Settings"; adjusted formatting on existing entry.
Documentation src/pages/docs/configuration/manage-user-and-organization-settings.md	Created new documentation page detailing user and organization security settings management, covering profile updates, password changes, two-factor authentication setup, password policies, and single sign-on configuration with step-by-step instructions and visual references.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Minimal scope: only two files affected with straightforward additions
• Changes are primarily documentation content and a simple config entry mapping
• No logic, no structural changes, no complex interactions to verify

Suggested reviewers

• Santhosh-testsigma
• Nandhini4501

Poem

🐰✨ New docs hop into view,
With settings neat and clean and true,
User profiles, two-factor light,
SSO configured just right!
Navigation guides the way,
Helping users every day.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Added a new doc 'Configure User & Org Settings'' directly and clearly summarizes the main change: adding new documentation about user and organization settings configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch DOC-686

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 760cf51 and 6208903.

📒 Files selected for processing (2)

• src/left-nav-title.json (1 hunks)
• src/pages/docs/configuration/manage-user-and-organization-settings.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

src/pages/docs/configuration/manage-user-and-organization-settings.md

[grammar] ~22-~22: Use a hyphen to join words.
Context: ...user settings and configure organization level security policies in Testsigma. Th...

(QB_NEW_EN_HYPHEN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: CI

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# First, let's check if the file is valid JSON and understand its structure
jq empty src/left-nav-title.json 2>&1 && echo "✅ Valid JSON" || echo "❌ Invalid JSON"

# Get basic stats about the file
echo "File size:"
wc -l src/left-nav-title.json

# Check the structure at a high level
echo -e "\nFirst few keys:"
jq 'keys[0:5]' src/left-nav-title.json

# Check around lines 760-761
echo -e "\nContent around lines 760-761:"
sed -n '758,763p' src/left-nav-title.json

# Look for the specific keys mentioned
echo -e "\nSearching for 'qtest' entries:"
grep -n '"qtest"' src/left-nav-title.json

echo -e "\nSearching for 'xray' entries:"
grep -n '"xray"' src/left-nav-title.json

echo -e "\nSearching for 'jira' entries:"
grep -n '"jira"' src/left-nav-title.json

echo -e "\nSearching for 'live-editor' entries:"
grep -n '"live-editor"' src/left-nav-title.json

Repository: testsigmahq/testsigma-docs

Length of output: 1922

---

🏁 Script executed:

# Let's understand the actual JSON structure - are these keys at root level or nested?
echo "JSON Structure Analysis:"
echo "========================"

# Get the top-level structure
echo "Top-level keys (sample):"
jq 'keys | length' src/left-nav-title.json
echo "Total root-level keys above"

# Check the type of values for these keys
echo -e "\nType of value for 'qtest' key:"
jq '.qtest | type' src/left-nav-title.json

# Check if qtest is a single object or array
echo -e "\nValue structure for 'qtest':"
jq '.qtest' src/left-nav-title.json

# Let's look at a few entries to understand structure
echo -e "\nSample entries around line 700-710:"
sed -n '698,712p' src/left-nav-title.json

echo -e "\nLet's verify: are 'qtest', 'xray', 'jira', 'live-editor' at ROOT level?"
jq 'has("qtest") and has("xray") and has("jira") and has("live-editor")' src/left-nav-title.json

# Count unique root keys
echo -e "\nTotal unique root-level keys:"
jq 'keys | unique | length' src/left-nav-title.json
echo "vs total root keys:"
jq 'keys | length' src/left-nav-title.json

Repository: testsigmahq/testsigma-docs

Length of output: 1853

---

Critical: Source file contains duplicate key definitions that cause silent data loss.

The JSON file is technically valid, but the source code contains multiple definitions of the same keys at the root level. In JSON, only the last occurrence of a duplicate key is retained in the parsed object; earlier definitions are silently discarded:

• "qtest": defined 4 times (lines 700, 732, 753, 760) — only line 760 is retained
• "xray": defined 5 times (lines 426, 699, 731, 752, 759) — only line 759 is retained
• "jira": defined 4 times (lines 423, 729, 757, 758) — only line 758 is retained
• "live-editor": defined 4 times (lines 704, 728, 755, 756) — only line 756 is retained

The navigation entries from the earlier definitions become inaccessible. Remove the duplicate key definitions and keep only the intended entries.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use hyphenated form for compound adjective.

Change "organization level" to "organization-level" to properly modify "security policies" as a compound adjective.

-You can now manage user settings and configure organization level security policies in Testsigma. This includes updating your profile, changing your password, enabling Two-Factor Authentication (2FA), and setting password security requirements for your team. This article discusses configuring User and Organization Settings in Testsigma.
+You can now manage user settings and configure organization-level security policies in Testsigma. This includes updating your profile, changing your password, enabling Two-Factor Authentication (2FA), and setting password security requirements for your team. This article discusses configuring User and Organization Settings in Testsigma.

[Based on static analysis feedback]

📝 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

	You can now manage user settings and configure organization level security policies in Testsigma. This includes updating your profile, changing your password, enabling Two-Factor Authentication (2FA), and setting password security requirements for your team. This article discusses configuring User and Organization Settings in Testsigma.
	You can now manage user settings and configure organization-level security policies in Testsigma. This includes updating your profile, changing your password, enabling Two-Factor Authentication (2FA), and setting password security requirements for your team. This article discusses configuring User and Organization Settings in Testsigma.

🧰 Tools

🪛 LanguageTool

[grammar] ~22-~22: Use a hyphen to join words.
Context: ...user settings and configure organization level security policies in Testsigma. Th...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

In src/pages/docs/configuration/manage-user-and-organization-settings.md around
line 22, the phrase "organization level security policies" uses the wrong form
for a compound adjective; change it to "organization-level security policies" so
the hyphenated compound adjective correctly modifies "security policies" (update
the sentence accordingly and run a quick spell/check to ensure consistency
across the file).

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Fix typo in image filename.

Line 85 references an image with a typo: "Contiune_After_QR_Code.png" should be "Continue_After_QR_Code.png". This will cause the image to fail to load.

-   ![Continue after QR Code](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Contiune_After_QR_Code.png)
+   ![Continue after QR Code](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/Updated_Doc_Images/Continue_After_QR_Code.png)

📝 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

	
	

🤖 Prompt for AI Agents

In src/pages/docs/configuration/manage-user-and-organization-settings.md around
line 85 the image filename contains a typo ("Contiune_After_QR_Code.png");
update the markdown to reference the correct filename
"Continue_After_QR_Code.png" so the image loads properly.