docs(1secure): 1Secure free trial launch docs updates

[james-s-anderson]

Summary

• Added new Free Trial page (docs/1secure/freetrial.md) at sidebar position 10, above Requirements, based on the customer-facing self-serve free trial FAQ
• Updated Organization Statistics page to reflect the new dashboard UI: renamed to Organization Dashboard, updated all sections to match the current UI (Risk Assessment card, Recent Alerts, Reports card, Activity Summary, Most Logon Activity), and replaced the screenshot
• Updated all cross-references to "Organization Statistics" → "Organization Dashboard" across overview.md, alertstimeline.md, and riskassessmentdashboard.md

Test plan

• Verify Free Trial page appears in left nav above Requirements
• Verify Organization Dashboard page renders correctly with new screenshot
• Verify cross-reference links resolve correctly
• Confirm build passes

Generated with AI

Co-Authored-By: Claude Code ai@netwrix.com

[github-actions]

Documentation PR Review

Editorial Review

docs/1secure/admin/dashboard/organizationstatistics.md

• Clarity — Lines 13–14: The new navigation instruction says to click Dashboard in the left navigation pane to open the "MSP dashboard," but the other dashboard topics in this PR (overview.md, alertstimeline.md, riskassessmentdashboard.md) tell readers to click Home at the top to reach the "1Secure Dashboard." The two access paths and the two names ("MSP dashboard" vs. "1Secure Dashboard") now conflict, which will confuse a reader cross-referencing topics. Suggested fix: use one consistent entry point and name — e.g., "To view the Organization Dashboard, open the 1Secure dashboard, then click an organization name to open its Organization Dashboard." Confirm whether access is via Home or Dashboard.
• Clarity — Line 78: The heading "Most Logon Activity" reads as incomplete on its own; the body explains it shows "accounts with the highest number of logon attempts." If the UI label permits, "Accounts with Most Logon Activity" is clearer as a scannable heading. Suggested fix: align the heading with the card's actual UI label.

docs/1secure/admin/dashboard/alertstimeline.md

• Completeness — Lines 20–21: The step instructs the reader to navigate to the Organization Dashboard and "then click the Alerts Timeline chart." Per the redesigned Organization Dashboard in this same PR (organizationstatistics.md), that page no longer has an "Alerts Timeline" chart — it now has a Recent Alerts card with a View all alerts link. A reader following this step won't find the element named. Suggested fix: "...navigate to the Organization Dashboard, then click View all alerts on the Recent Alerts card."

docs/1secure/admin/dashboard/overview.md

• No issues found. (Both changes are clean renames of "Organization Statistics" to "Organization Dashboard.")

docs/1secure/admin/riskprofiles/riskassessmentdashboard.md

• No issues found. (The renamed step references the Risk Assessment card, which the redesigned Organization Dashboard still provides.)

docs/1secure/freetrial.md

• Clarity — Line 10: The intro states the trial gives access to "1Secure Complete," but the "After the Trial" section (lines 105–110) names the packages "1Secure Pro Identity," "1Secure Pro Data," and "1Secure Pro Complete." The reader can't tell whether "1Secure Complete" is the same thing as "1Secure Pro Complete." Suggested fix: use the exact package name consistently — "the capabilities included in the 1Secure Pro Complete package."
• Completeness — Lines 62–64 vs. lines 70–72: The "View Results" section says risk assessment results are available "as soon as the initial scans complete, depending on the size of your environment," while the "Risk Assessment" section says results are "typically available within 20 minutes of deployment." These two timing statements appear to conflict. Suggested fix: reconcile them — e.g., state the typical 20-minute figure once and note it varies with environment size.
• Clarity — Line 82: "MFA support" uses an acronym that isn't spelled out on first use. Suggested fix: "multi-factor authentication (MFA) support."
• Completeness — Line 99: "your data and configurations transition seamlessly to production" uses marketing phrasing ("seamlessly") that Netwrix standards discourage, and it leaves "transition to production" undefined for a trial reader. Suggested fix: "If you purchase a subscription, your data and configurations carry over to your production environment."
• Clarity — Lines 105–110: The package descriptions lean on marketing verbs ("uncover," "Unify," "enable secure AI adoption," "near real-time") rather than neutral, informative phrasing. Suggested fix: rephrase to describe what each package monitors and reports in plain, factual terms.

Summary

8 editorial suggestions across 3 files (2 files clean). Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

18 issues fixed, 9 skipped across 5 files

Category	Fixes
Contractions	1
Removed filler	1
BoilerplateCrossRef (rewrite)	1
Dale: passive-voice	15

Skipped (needs manual review)	Reason
docs/1secure/freetrial.md:83 — Netwrix.FirstPerson	False positive. The flagged 'I' is part of the certification name 'SOC 2 Type I', not a first-person pronoun. Rewriting would corrupt the product/standard name.
docs/1secure/freetrial.md:94 — Netwrix.FirstPersonPlural	The flagged 'Us' is the literal link/button label 'Contact Us' on the Netwrix website. Changing it would misrepresent the actual UI element the reader clicks.
docs/1secure/freetrial.md:109 — Netwrix.OxfordComma	False positive. 'discover and classify' is a compound verb within a single list item ('discover and classify sensitive data'), not a three-item series. The list's Oxford comma is already correctly placed before 'and enable secure AI adoption'.
docs/1secure/admin/dashboard/alertstimeline.md:16 — Dale: passive-voice	'the organization represented by the selected bar' is a reduced relative clause that reads naturally; rewriting is awkward
docs/1secure/admin/dashboard/alertstimeline.md:56 — Dale: passive-voice	'when the alert is triggered' describes an event state; active rewrite would require inventing an actor and change nuance
docs/1secure/admin/dashboard/overview.md:9 — Dale: idioms	'single-pane-of-glass' is an established security-industry term; rewriting risks changing meaning
docs/1secure/admin/dashboard/overview.md:11 — Dale: minimizing-difficulty	'quickly identify and prioritize' is ambiguous marketing phrasing describing product capability; removing it could change intent
docs/1secure/freetrial.md:70 — Dale: passive-voice	'The risk assessment is powered by PingCastle and runs...' — active rewrite would shift the subject of the trailing clause and risk meaning change
docs/1secure/freetrial.md:71 — Dale: passive-voice	'Each identified risk is prioritized... and mapped...' — actor (PingCastle vs 1Secure) is ambiguous, so active rewrite risks introducing inaccuracy

Ask @claude on this PR if you'd like an explanation of any fix.