Skip to content

docs(privilegesecure): add the 26.07 documentation - #1843

Merged
TylerReese merged 289 commits into
devfrom
docs/privilegesecure-26.07
Nov 9, 2026
Merged

TylerReese merged 289 commits into
devfrom
docs/privilegesecure-26.07

Conversation

@TylerReese

@TylerReese TylerReese commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Adds the cumulative 26.07 documentation for Netwrix Privilege Secure for Access Management and makes it the latest version. One section covers 25.12.0, 26.03.x, and 26.07.0 through 26.07.3, in the Section Guide layout.

  • 26.07 docs: getting started, requirements, install, configuration, administration, resources, Remote Access Gateway, user guide, integrations, and troubleshooting. The API reference is generated from the product OpenAPI spec.
  • Reference additions: proxy settings, SSH client settings, and device actions, written from lab tests.
  • Diagrams: the access policy and architecture diagrams are redrawn with labeled arrows, the real connection directions, and the message bus, WSL, and guacd placement for the Remote Access Gateway.
  • Search and retrieval: 52 page descriptions, three titles, and seven alt texts were rewritten. The 4.2 redirects and five KB articles now point to 26.07.
  • KB: all 75 Privilege Secure KB articles were restyled to the KB standard. Every fact, command, path, number, UI label, and link target is kept.
  • 26.03: adds the Linux and BSD sudoers pages and the related edits to 26.03 pages.
  • Registration: src/config/products.js, docusaurus.config.js, and package.json add the 26.07 version and the API reference plugin. The OpenAPI spec and its preparation script are included.

Follow-ups after merge

  • Confirm with an SME whether SSH recordings mask keystrokes typed at a password prompt. The 26.07 pages no longer claim they do.
  • Check on a lab whether the Settings and Command Plans tabs on Platforms need a feature flag. The text still says "when the custom platform connector feature is enabled".
  • Confirm the browser extension build number (25.8.26).
  • Confirm the 45 open items on the open-questions page (23 from the review feedback, 22 from the first research pass). The page-by-page list is in the open-questions page linked in the PR conversation. They cover Completed With Errors and Completed Not Run statuses, regex checking in command restrictions, activity group deletion, %fqdn% versus %dnshostname%, RADIUS empty username format, the two InsecureSkipVerify settings, key tools in the Proxy Service installer, the first-install SQL Server sequence, ServiceNow Keep In Progress, Setup-WslTask.ps1, the Remote Access Gateway upgrade order and sign-in landing page, user-count licensing, PAN-OS group membership, removing resources, Allow Connection events, session file encryption, and a sample HashiCorp Vault policy.
  • Replace the 31 screenshot and verify placeholders. They are comments and don't render.
  • Decide the short product name in the KB: "Privilege Secure" or "Privilege Secure for Access Management".
  • Confirm 33 suspected typos in KB articles.
  • Review proposed KB merges and splits, and outdated version gates (3.5 to 4.2, Postgres 12 versus 16, PowerShell 7.1 pins).
  • Site-wide SEO changes for a separate PR: a product-aware title template, a working social image, a banner and canonical links for older versions, sitemap lastmod, and optional JSON-LD.
  • Seven ports.md items that depend on open questions: SMTP and SIEM rows, the runtime 6500 wording, and the license service port on high availability pairs.
  • The DaleLocal.ExclamatorySentences fixture test fails the same way on dev. The branch doesn't touch it.

Verification

  • Container build passes. Broken-link warnings are cross-product only, because it is a single-product build.
  • Vale passes on the changed 26.07 pages. The anchor check passes.
  • 929 pages return 200 on a preview deployment. The deployment is noindex.

Restyled-With: /doc-restyle

Generated with AI

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

https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm

Closes #1844

TylerReese and others added 30 commits October 25, 2026 13:29
…ers in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…viceNow in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…g-based troubleshooting in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…enial log message in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…and change requests in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…s for ServiceNow users in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
… and port, and RAG package name from the lab server in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…mbers, and report defaults in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
… 5.1 certificate error from lab tests in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
…eleases in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
* Add Linux target requirements for file system scanning to Access Analyzer 12.0 and 11.6

New Linux Target Requirements and Linux Server Configuration pages covering SMB/CIFS and NFSv3 scanning, permissions, ports, SELinux, and that Activity Auditing is not supported. Linked from the supported platforms topic. Vale clean. Pre-commit hook skipped because its style check needs packages that are not installed locally.

Generated with AI

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

* fix(vale): auto-fix style issues (Vale + Dale)

* Add Linux target requirements for file system scanning to Access Analyzer 12.0 and 11.6

New Linux Target Requirements and Linux Server Configuration pages covering SMB/CIFS and NFSv3 scanning, permissions, ports, SELinux, and that Activity Auditing is not supported. Linked from the supported platforms topic. Vale clean. Pre-commit hook skipped because its style check needs packages that are not installed locally.

Generated with AI

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

* fix(vale): auto-fix style issues (Vale + Dale)

---------

Co-authored-by: Claude Code <ai@netwrix.com>
Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com>
* Update fast-cloud-proxy-settings.md

An update to this article is required.

Changes were made to the application which make the original settings redundant.

* docs(kb): apply review fixes to FAST Cloud proxy settings article

- Vale: replace contraction
- Dale: fix three passive-voice sentences
- Derek: gerund title, two-sentence description, goal-first Overview,
  single Instructions section with version subsections, bold/backtick
  consistency, callout indentation, removal step as NOTE, trim product
  name repetition
- Remove stacked callouts: move the browser-proxy note to
  Troubleshooting and fold step 3 placeholder guidance into the lead-in

Generated with AI

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

---------

Co-authored-by: hilram7 <212961752+hilram7@users.noreply.github.com>
Co-authored-by: Claude Code <ai@netwrix.com>
… and code-settled TODOs in 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
…run (#1780)

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* Add doc-restyle skill and content-integrity check

Rewrites existing pages into doc-draft's style without changing their content.
checkContent compares code blocks, inline code, link targets, bold labels,
numbers, admonitions, and frontmatter between the original and the rewrite.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Restyle two Password Policy Enforcer 10.2 pages with doc-restyle (trial)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Shorten restyle trial descriptions and add a description length target

doc-draft and doc-restyle now aim for about 120 characters, with 160 as the ceiling.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Ignore code-block indentation in the restyle integrity check

Indenting a fenced block under a numbered step is a layout change, not a content change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Remove the doc-restyle trial page changes

Restores the two Password Policy Enforcer 10.2 pages to their dev versions.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Harden the restyle integrity check after code review

- Fail when a file is identical to its base, and reject a bad --base ref or a missing flag value
- Resolve paths from the repo root, and tell a new file from a git error
- Run as a script from paths with spaces or on Windows
- Apply --allow-change to prose only, and reject an empty old text
- Make SKILL.md say what the check does and does not flag

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Check whole frontmatter values, fence rules, and line endings in the restyle integrity check

- Compare each frontmatter key as a whole, so keywords lists count, and flag keys that are added or removed
- Close a code fence only on the same character and a length at least as long as the opener
- Treat CRLF and LF files the same, and strip indent from an unterminated block too
- Pin exact violation messages in the tests, fix the 'added' wording, and split the frontmatter test by case

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Let a merge pass the restyle integrity check and reject paths outside the repo

- Skip the frontmatter comparison for a file the merge deleted
- Exit 2 with a clear message for a path outside the repository
- Say in SKILL.md that --allow-change applies to prose only

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Fix the insecure temp file in a test and two integrity CLI path bugs

- Create the outside-the-repo test file in a private mkdtemp folder, not a fixed name in the shared temp directory (CodeQL js/insecure-temporary-file)
- Exit 2 when a path exists neither at the base nor on disk, instead of reporting PASS
- Compare real paths, so a symlinked checkout or macOS /var maps into the repository

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Scope --allow-change to plain whole words and harden the CLI tests

- Apply an allowed change to plain prose only, match whole words, and fail if the old text is not found
- Reject a --base value that starts with a dash
- Skip YAML comment lines when comparing frontmatter values
- Make the fixture repo commit unsigned and assert that it succeeded
- Tell the skill to pass the full surrounding phrase

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* Add --allow-link for renamed anchors and pair frontmatter numbers by page

- --allow-link rewrites link and image targets only, so a retitled heading or a moved page can pass the check
- Count frontmatter numbers only for a page that exists before and after, so a split or merge does not read as a number change
- Update SKILL.md to send prose fixes to --allow-change and link updates to --allow-link

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

* docs(doc-restyle): report progress for each page and batch

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
… move the latest-installer step to the top

An install on a release earlier than 1.2.0 has no in-cluster media
upgrade Job, so the Settings page, automatic updates, and dspmctl can't
move it to 1.2.0. Add a warning at the top of the upgrade page and an
"Upgrade to 1.2.0" section with the dspm-installer command for each
install type, and point the Settings page and automatic-update sections
at it.

The "download the latest dspm-installer" warning lived only in the
air-gapped tab. Move it, with the download commands, into a top-level
"Download the Latest Installer" section that applies to every install
type, and have the air-gapped download step link to it.
…ge-deployment-size

# Conflicts:
#	docs/accessanalyzer/26.1/install/roll-back-to-a-previous-version.md
…ab for 26.07

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.8 to 3.1.9.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](fastify/fast-uri@v3.1.8...v3.1.9)

---
updated-dependencies:
- dependency-name: fast-uri
  dependency-version: 3.1.9
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 0 skipped across 169 files

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

26.07 is now the latest version, so unversioned addresses follow its layout.
Adds 233 redirects from the old 26.03 addresses to the 26.07 pages that cover
the same topics, uses the 26_07 route in the API reference baseUrl, and makes
the spec preparation script reject a non-numeric depth argument.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 0 skipped across 169 files

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

Moves the 26.07 API reference notes into docs/privilegesecure/CLAUDE.md,
adds the api folder to its directory table, and drops pointers to files
that are not in the repository.

Generated with AI

Co-Authored-By: Claude Code <ai@netwrix.com>
Claude-Session: https://claude.ai/code/session_01D98ga2ymVWQpDP6SRfNxhm
@TylerReese

Copy link
Copy Markdown
Contributor Author

Documentation PR Review

Editorial Review

docs/privilegesecure/26.03/admin/activities/addaction/activityactiontypes.md

  • Completeness — Line 26: The row says Run As, Commands, and Prompt for Password appear but 26.03 doesn't apply them. It doesn't tell the reader what to do with those fields, so a reader may fill them in and assume they limit the session user. Suggested fix: "Say to leave those fields at their defaults because they have no effect in 26.03, and that the session user always gets full sudo. The least-privilege policy limits only the service account."

docs/privilegesecure/26.03/admin/configuration/serviceaccounts/linuxbsdsudoers.md

  • Structure — Line 38: 'Create the policy file' gives chown and chmod commands for a file that no step creates. The policy content comes in the next section, so the reader sets ownership on a file that doesn't exist yet. Suggested fix: "Add a step that creates the file, for example visudo -f /etc/sudoers.d/svc_sbpam, or move the ownership and mode commands after 'Add the policy'."

docs/privilegesecure/26.03/admin/configuration/serviceaccounts/serviceaccount.md

  • Structure — Line 31: The rule that a Linux or BSD account name must match the sudoers file comes after step 4 (Save). A reader saves the account before seeing a rule that affects what they enter in step 3, and the rule splits Save from its result. Suggested fix: "Move the sentence into step 3 as a sub-bullet, and keep 'The new service account is added to the Service Accounts list.' directly after step 4."

docs/privilegesecure/26.03/admin/configuration/serviceaccounts/serviceaccounts.md

No issues found.

docs/privilegesecure/26.03/admin/configuration/serviceaccounts/sudoerspatterns.md

  • Clarity — Line 65: 'despite a common claim that it does' refers to a claim with no source and adds nothing to the rule the sentence already states. Suggested fix: "Delete the clause: 'A command-path wildcard doesn't cross directory boundaries.'"

docs/privilegesecure/26.03/requirements/target.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/access-certification.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/activity-log.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/audit-reporting.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/db-change-history.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/events.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/log-files.md

No issues found.

docs/privilegesecure/26.07/admin/audit-reporting/reports.md

  • Completeness — Line 105: The Subscribe steps start with 'Open a report you saved'. A reader who wants to subscribe to a predefined report isn't told that the Subscriptions tab stays disabled until they save a copy to My Reports. That is stated only under Create a report. Suggested fix: "Add a lead-in: 'To subscribe to a predefined report, first change a filter and select Save to create a copy in My Reports. The Subscriptions tab is disabled until the report is saved.'"

docs/privilegesecure/26.07/admin/credentials/credential-groups.md

No issues found.

docs/privilegesecure/26.07/admin/credentials/internal-service-accounts.md

No issues found.

docs/privilegesecure/26.07/admin/credentials/manage-credentials.md

No issues found.

docs/privilegesecure/26.07/admin/credentials/overview.md

No issues found.

docs/privilegesecure/26.07/admin/credentials/password-history.md

No issues found.

docs/privilegesecure/26.07/admin/credentials/policy-overrides.md

  • Structure — Line 60: The rule that only credentials with the method Automatic appear in the list comes after the steps that use the list. A reader who can't find an account won't know why. Suggested fix: "Move it above the numbered steps in 'Add credentials to an override' as a prerequisite, and link to Password rotation methods to explain Automatic."

docs/privilegesecure/26.07/admin/credentials/rotation-methods.md

  • Clarity — Line 39: This section says a Service account rotates from the Account Dependencies dialog. Line 23 and the table say Service Account Details. The reader can't tell whether these are one window or two. Suggested fix: "Use one name for the control in all places, or explain how Account Dependencies relates to Service Account Details."

docs/privilegesecure/26.07/admin/credentials/service-account-dependencies.md

  • Clarity — Line 73: The status names aren't consistent and aren't explained. The text lists Queued, Running, Complete, and Failed, then calls Completed With Errors and Completed Not Run red states. 'Complete' and 'Completed' look like different values, and neither red status is explained. Suggested fix: "Use the exact console labels, and add a short table that gives the meaning of each status, including Completed With Errors and Completed Not Run."

docs/privilegesecure/26.07/admin/overview.md

No issues found.

docs/privilegesecure/26.07/admin/roles/admin-view-read-only.md

No issues found.

docs/privilegesecure/26.07/admin/roles/assign-roles.md

No issues found.

docs/privilegesecure/26.07/admin/roles/custom-roles.md

No issues found.

docs/privilegesecure/26.07/admin/roles/roles.md

No issues found.

docs/privilegesecure/26.07/admin/service-nodes/scheduled-tasks.md

No issues found.

docs/privilegesecure/26.07/admin/service-nodes/service-nodes.md

  • Completeness — Line 45: Step 3 says to search for RemoteCertificate and refers to 'the inner exception' and 'the console port'. It never gives the exact string to look for or the port number, and the certificate fix comes only in the loose paragraphs after the steps. Suggested fix: "Name the exact error (for example RemoteCertificateNameMismatch) and port 6500 in step 3, and make the certificate fix a numbered step."

docs/privilegesecure/26.07/admin/sessions/active-sessions.md

No issues found.

docs/privilegesecure/26.07/admin/sessions/dashboard.md

No issues found.

docs/privilegesecure/26.07/admin/sessions/historical-sessions.md

  • Clarity — Line 36: 'Search and filters cover live and recorded sessions' is confusing on a tile that lists only sessions that have ended. Suggested fix: "Remove 'live', or rewrite: 'Search and filters cover sessions with and without recordings.'"

docs/privilegesecure/26.07/admin/sessions/live-session-viewer.md

No issues found.

docs/privilegesecure/26.07/admin/sessions/replay-viewer.md

  • Clarity — Line 32: The example says playback 'jumps to the first match' after you select the recording. Step 3 says you select a search match to start playback at that point. The two disagree on whether the reader must pick a match. Suggested fix: "Rewrite the example to match step 3: 'expand the row, select the match you want, and playback starts at that point.'"

docs/privilegesecure/26.07/admin/sessions/session-logs.md

No issues found.

docs/privilegesecure/26.07/admin/sessions/session-recording.md

No issues found.

docs/privilegesecure/26.07/admin/users-groups/add-users-groups.md

No issues found.

docs/privilegesecure/26.07/admin/users-groups/application-users.md

  • Structure — Line 9: The overview says an application user has the same capabilities as a standard user. What it can actually call depends on an access policy or role, which appears only in Next steps. A reader could create the user and find that it can do nothing. Suggested fix: "State in the overview that the user needs an access policy or role before the tool can call anything, and link to the Next steps."

docs/privilegesecure/26.07/admin/users-groups/collections.md

No issues found.

docs/privilegesecure/26.07/admin/users-groups/local-users.md

No issues found.

docs/privilegesecure/26.07/admin/users-groups/user-details.md

  • Clarity — Line 130: Lines 130 and 132 both say that from 26.07.3 a blocked or locked user can't sign in, so the statement appears twice. The failed-sign-in lockout section then says sign-in is refused with no version qualifier. A reader can't tell whether sign-in is refused before 26.07.3. Suggested fix: "Merge lines 130 and 132 into one statement, and say whether the failed-sign-in lockout applies to all versions or only from 26.07.3."
  • Completeness — Line 19: The header button table lists Lock Account, Reset MFA, and Reset Password, but not Unlock Account, which 'Unlock an account' uses later. Suggested fix: "Add an Unlock Account row (shown in place of Lock Account while the account is locked) that links to the Unlock an account section."

docs/privilegesecure/26.07/admin/users-groups/users-groups.md

No issues found.

docs/privilegesecure/26.07/api/authentication.md

No issues found.

docs/privilegesecure/26.07/api/overview.md

  • Clarity — Line 98: The paragraph repeats itself and is hard to follow. It says to connect with the host name in the certificate, says a localhost request returns HTTP 400, then repeats the host-name advice. It isn't clear which error applies to which client. Suggested fix: "Rewrite as two statements: Windows PowerShell 5.1 shows the trust error when the address doesn't match the certificate, and requests to localhost return HTTP 400. Using the certificate host name fixes both."

docs/privilegesecure/26.07/api/reference/index.md

No issues found.

docs/privilegesecure/26.07/configuration/access-policies/activity-token-complexity.md

No issues found.

docs/privilegesecure/26.07/configuration/access-policies/approval-workflows.md

  • Structure — Line 58: The warning that local users never receive approval requests appears only after the reader has already chosen approvers. The prerequisite (line 16) says approvers must be domain users that 'Privilege Secure manages', which is hard to parse. Suggested fix: "Move the warning into Prerequisites, and reword line 16: approvers must be domain users or groups of domain users that you onboarded in Privilege Secure."

docs/privilegesecure/26.07/configuration/access-policies/command-restrictions.md

  • Clarity — Line 9: The intro and the Actions table say 'the console' takes the action, but lines 39, 41, and 72 say the proxy tests the command. The reader can't tell which component enforces the rule. Suggested fix: "Say 'the proxy' for enforcement in the intro and the Actions table, and use 'the console' only for where you configure the restriction."
  • Completeness — Line 41: 'The proxy skips a rule whose expression isn't valid' doesn't tell the reader how they would know. The console may accept the rule while the restriction silently does nothing. Suggested fix: "Say whether the console checks the expression when you save, and where a skipped rule shows up (for example, a log). If nothing shows, say so and tell the reader to test each rule."

docs/privilegesecure/26.07/configuration/access-policies/connection-profiles.md

No issues found.

docs/privilegesecure/26.07/configuration/access-policies/credential-based-policy.md

No issues found.

docs/privilegesecure/26.07/configuration/access-policies/overview.md

No issues found.

docs/privilegesecure/26.07/configuration/access-policies/resource-based-policy.md

No issues found.

docs/privilegesecure/26.07/configuration/activities/action-types.md

  • Clarity — Line 159: The warning 'From 26.07.3, the rule limits the user to the Run As account' doesn't say what changed or what the reader must do. Suggested fix: "State the effect and the action, for example: 'From 26.07.3, the user can run the listed commands only as the Run As account. Set Run As to every account the user needs.'"

docs/privilegesecure/26.07/configuration/activities/actions.md

No issues found.

docs/privilegesecure/26.07/configuration/activities/activities.md

No issues found.

docs/privilegesecure/26.07/configuration/activities/activity-groups.md

  • Completeness — Line 23: The page shows a trash icon for deleting a group, and line 33 covers removing an activity, but neither says what happens to access policies that use the group. The upgrade warning on line 14 is about deleting a group, but there is no delete section for it to sit in. Suggested fix: "Add a 'Delete an activity group' section that says whether deleting a group removes it from policies, and move the line 14 upgrade warning there."

docs/privilegesecure/26.07/configuration/activities/create-activity.md

  • Clarity — Line 47: The token-name explanation mixes two rules. Without a policy, Privilege Secure keeps 15 characters and pads the name to 20. With a policy, it keeps Length minus 5 and pads to Length. The text doesn't say that the 5 added characters are random, or whether the rule applies on every platform. Suggested fix: "Split the explanation into two short statements, one for the default and one for a complexity policy, say that 5 random characters are added, and say whether the rule applies to every platform."

docs/privilegesecure/26.07/configuration/activities/group-role-activities.md

No issues found.

docs/privilegesecure/26.07/configuration/activities/login-account-templates.md

  • Clarity — Line 53: %fqdn% and %dnshostname% (line 52) have identical descriptions, so the reader can't choose between them. Suggested fix: "State the difference, or say that %fqdn% is the same as %dnshostname%."

docs/privilegesecure/26.07/configuration/authentication/openid-connect.md

No issues found.

docs/privilegesecure/26.07/configuration/authentication/overview.md

  • Completeness — Line 72: The page names the StrictExternalAuth setting 'in the web service configuration' and the next paragraph discusses changing it, but it gives neither the file path nor the edit. Suggested fix: "Give the configuration file and path, show the exact change, and say whether you must recycle the application pool."

docs/privilegesecure/26.07/configuration/authentication/radius.md

  • Clarity — Line 72: 'If the format produces an empty value, it sends that same value' is ambiguous. 'That same value' could mean the empty value or the Privilege Secure user name. Suggested fix: "Rewrite: 'If the format produces an empty value, Privilege Secure sends the Privilege Secure user name.' Confirm which one is correct."

docs/privilegesecure/26.07/configuration/authentication/saml.md

No issues found.

docs/privilegesecure/26.07/configuration/certificates.md

No issues found.

docs/privilegesecure/26.07/configuration/encryption-keys/aws-kms-rotation.md

  • Clarity — Line 55: Step 2 combines two paths: run Rotate Key with the ARN and Region, or 'to change only the stored access key, select Update Key instead'. Rotate Key also rotates the encryption key and re-encrypts every secret, so the choice matters, and the reader can't tell which one applies. Suggested fix: "Split the step into two paths: 'Update the stored access key only (Update Key)' and 'Update the key and rotate (Rotate Key)'. Recommend one."
  • Completeness — Line 60: The recovery warning gives SbPAM.RotateKey.exe refreshaws -k <keyId> -a <file> but doesn't say where the tool is, how to find the key ID, or which file <file> is. All of this is packed into one dense warning. Suggested fix: "Move the recovery into a numbered procedure. Define <keyId> and <file>, give the KeyTools folder and where key files are stored, and add an example."

docs/privilegesecure/26.07/configuration/encryption-keys/aws-kms.md

  • Structure — Line 70: 'Limit the policy to the key' is a separate section after the KMS key section. The IAM policy steps tell the reader to allow all keys for now, and Next step doesn't mention this section, so a reader can finish with an over-broad policy. Suggested fix: "Add a note in the IAM policy steps that links to 'Limit the policy to the key', or add the section to the checklist in Before you begin."

docs/privilegesecure/26.07/configuration/encryption-keys/encryption-keys.md

  • Structure — Line 98: The warning not to run rotate without the AWS options comes after the numbered steps. A reader whose key is protected by AWS KMS will already have run the command in step 3. Suggested fix: "Move the paragraph above step 3 as a :::warning callout."

docs/privilegesecure/26.07/configuration/overview.md

No issues found.

docs/privilegesecure/26.07/configuration/proxy-settings.md

  • Clarity — Line 25: The file table puts insecureskipverify for API calls in sbpam_api.json, but the SSH settings table (line 56) lists InsecureSkipVerify, 'Skips the certificate check when the proxy calls the Privilege Secure API', under sbpam_ssh.json. The reader can't tell which file applies. Suggested fix: "Say whether these are two separate settings and what each controls, or correct the file reference."

docs/privilegesecure/26.07/configuration/security-hardening.md

No issues found.

docs/privilegesecure/26.07/configuration/service-accounts/entra-id-app-registration.md

  • Clarity — Line 66: The note says to assign Global Administrator 'instead of' User Administrator, which conflicts with the instruction on line 57 to assign two roles. The role rules are repeated across lines 66, 69, and 72. Suggested fix: "Merge them into one statement of which roles are required for which accounts, and say whether Global Administrator replaces one role or both."

docs/privilegesecure/26.07/configuration/service-accounts/linux-bsd-sudoers.md

No issues found.

docs/privilegesecure/26.07/configuration/service-accounts/prepare-azure-linux.md

No issues found.

docs/privilegesecure/26.07/configuration/service-accounts/service-accounts.md

  • Clarity — Line 24: 'See the note on Windows logins that follows' points to a note after the table, but the first note that follows is about Cisco. The SQL Server note comes second. Suggested fix: "Place the SQL Server note directly after the table, or link to it by anchor."

docs/privilegesecure/26.07/configuration/service-accounts/sudoers-pattern-reference.md

No issues found.

docs/privilegesecure/26.07/configuration/service-accounts/sudoers-tags-reference.md

  • Clarity — Line 11: 'In the Commands field of the action, see [link]' is a fragment. It promises a separator rule for the Commands field but doesn't state it, so the reader doesn't know whether to use colons or commas there. Suggested fix: "Rewrite: 'In a sudoers file, join tags with colons. In the Commands field of the action, . See Sudoers tags in the Commands field.'"

docs/privilegesecure/26.07/configuration/ssh-algorithms.md

  • Structure — Line 65: Step 6 tells the reader to put lists inside an Algorithms object 'as the example shows'. The warning that explains why, that the installer's default layout is ignored, comes after the steps. Suggested fix: "Move the warning just before the step that edits sbpam_ssh.json."

docs/privilegesecure/26.07/configuration/ssh-client-settings.md

No issues found.

docs/privilegesecure/26.07/configuration/system-settings/data-retention.md

  • Structure — Line 32: The warning that deletion is permanent and can be large comes after the procedure that triggers it. A reader may click Save before seeing it. Suggested fix: "Move the warning above the numbered steps in 'Turn on data retention'."

docs/privilegesecure/26.07/configuration/system-settings/email.md

No issues found.

docs/privilegesecure/26.07/configuration/system-settings/rdp-files.md

No issues found.

docs/privilegesecure/26.07/configuration/system-settings/services-url.md

No issues found.

docs/privilegesecure/26.07/configuration/system-settings/system-settings.md

  • Structure — Line 73: The exemption rules for User Expiration come after the warning. The surprising rule, that users who get Administrator only through a group aren't exempt, is easy to miss, and a reader who stops at the warning could delete administrators. Suggested fix: "Put the exemptions before the warning or inside it, and call out the group-administrator case."

docs/privilegesecure/26.07/getting-started/architecture.md

  • Completeness — Line 30: Port 6522 (broker) appears only in this paragraph, not in the Service mesh row of the table, which lists 6520, 6523, and 6524. A reader who builds firewall rules from the table will miss it. Suggested fix: "Add 6522 to the Proxy service or Service mesh row of the table."

docs/privilegesecure/26.07/getting-started/glossary.md

  • Completeness — Line 28: Platform is a core concept across the Resources and Activities pages (Change Platform, the Platform field) but has no glossary entry, and other pages use it without a definition. Suggested fix: "Add an entry such as 'Platform: The resource type definition that tells Privilege Secure how to manage a resource, for example Windows, Linux, or Active Directory.'"

docs/privilegesecure/26.07/getting-started/key-concepts.md

No issues found.

docs/privilegesecure/26.07/getting-started/overview.md

No issues found.

docs/privilegesecure/26.07/getting-started/quick-start.md

  • Clarity — [idiom] Line 9: 'From the bottom up' is figurative and doesn't say what the bottom is. Suggested fix: "Rewrite as 'Set up Privilege Secure in this order: install, connect, and then define access.'"

docs/privilegesecure/26.07/index.md

No issues found.

docs/privilegesecure/26.07/install/activate-license.md

No issues found.

docs/privilegesecure/26.07/install/additional-services.md

  • Completeness — Line 70: This line says only the Action, Scheduler, and SIEM installers install the KeyTools folder, but the key import on the remote server needs KeyTools. A reader installing only the Host Scan Service has no way to import the keys. Suggested fix: "Say where KeyTools comes from for Host Scan, for example 'Install the Proxy Service first, or copy KeyTools from the application server.'"

docs/privilegesecure/26.07/install/components.md

No issues found.

docs/privilegesecure/26.07/install/first-launch.md

  • Structure — Line 58: Step 4 (recovery codes) reads as if it always appears, but step 3 says Setup Later skips MFA registration. A reader who skipped MFA reads a step that doesn't apply. Suggested fix: "Start step 4 with 'If you registered MFA,' and say to go on to step 5 otherwise."

docs/privilegesecure/26.07/install/high-availability.md

  • Structure — Line 78: The required iisreset on the new primary server is an unnumbered paragraph inside step 1 of the failover procedure, after a long description of what the HA manager does. A reader following the numbered steps can skip it, and failover doesn't complete without it. Suggested fix: "Make it a numbered step after step 1: 'On the new primary server, run iisreset so the SbPAM Web Service uses the new database settings.'"

docs/privilegesecure/26.07/install/install-application-server.md

  • Completeness — Line 109: Step 4 says to install SQL Server, install Privilege Secure, and then point it at SQL Server. Line 111 says the Advanced checkbox and the switch apply only to an existing installation. The two don't agree, so the sequence for a first installation on SQL Server is unclear. Suggested fix: "Give the sequence for both cases, or state that a first installation uses PostgreSQL and then switches to SQL Server."

docs/privilegesecure/26.07/install/overview.md

No issues found.

docs/privilegesecure/26.07/install/rdp-monitor.md

No issues found.

docs/privilegesecure/26.07/install/remote-proxy.md

  • Structure — Line 45: The text says registration has three parts (get a hash, describe each server, register), but there are only two headings, Prepare the application server and Register the remote server. Suggested fix: "Say 'two parts' and list what each does, or add headings that match the three parts."

docs/privilegesecure/26.07/install/silent-install.md

No issues found.

docs/privilegesecure/26.07/install/troubleshoot-installation.md

No issues found.

docs/privilegesecure/26.07/install/upgrade.md

  • Structure — Line 58: Step 3 requires the PostgreSQL 12 to 16 migration first, but that section sits below the main procedure, so the reader meets it after steps 4 to 9. Suggested fix: "Move 'Upgrade PostgreSQL from 12 to 16' before 'Upgrade the application server', or make it a numbered step before the upgrade."

docs/privilegesecure/26.07/integrations/identity/okta-oidc.md

No issues found.

docs/privilegesecure/26.07/integrations/itsm/servicenow.md

  • Completeness — Line 114: The end-of-session prompt offers Keep In Progress, On Hold, and Resolved, but line 109 says change requests have no In Progress state. The page doesn't say what happens to a change request when the user picks Keep In Progress. Suggested fix: "State which options apply to incidents and which to change requests, and what Privilege Secure does when the state isn't valid for the ticket type."

docs/privilegesecure/26.07/integrations/overview.md

No issues found.

docs/privilegesecure/26.07/integrations/security/access-analyzer.md

  • Clarity — [idiom] Line 100: 'Delete any that you don't want in force' uses a figurative phrase. Suggested fix: "Write 'delete any policy that you don't want to apply'."

docs/privilegesecure/26.07/integrations/siem/siem-servers.md

No issues found.

docs/privilegesecure/26.07/integrations/siem/siem-templates.md

No issues found.

docs/privilegesecure/26.07/integrations/vaults/byov.md

No issues found.

docs/privilegesecure/26.07/integrations/vaults/cyberark.md

No issues found.

docs/privilegesecure/26.07/integrations/vaults/hashicorp.md

  • Completeness — Line 22: The token prerequisite says only that the token 'can check accounts out of, and in to, the library'. To create the token, the reader needs the Vault policy paths and capabilities. Suggested fix: "Give a sample Vault policy with the library check-out and check-in paths and the capabilities they need."

docs/privilegesecure/26.07/integrations/vaults/laps.md

  • Clarity — Line 60: The session signs in with 'the account name from the activity's login account setting', but the activity field this page uses is Login Account Template (line 52), so the name doesn't match the UI label. Suggested fix: "Replace it with 'the account name you entered in Login Account Template'."

docs/privilegesecure/26.07/integrations/vaults/password-secure.md

  • Clarity — Line 34: Step 5 says to copy the 'API token', while the prerequisites and the service account step call it the 'API key'. The reader may think these are two different items. Suggested fix: "Use one term, or write 'copy the API key (shown as the API token)'."

docs/privilegesecure/26.07/integrations/vaults/vault-connectors.md

No issues found.

docs/privilegesecure/26.07/release-notes/whats-new.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/configuration/authentication.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/configuration/certificates.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/configuration/gateway-settings.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/install/install-gateway.md

  • Completeness — Line 155: 'Start WSL automatically' tells the reader to run Setup-WslTask.ps1, then says the installer already registers two scheduled tasks that keep WSL and guacd running without a manual command. The reader can't tell whether the manual script is still needed. Suggested fix: "State what each one does, say whether Setup-WslTask.ps1 is required or only an alternative, and move the table of installer tasks before the manual steps."

docs/privilegesecure/26.07/remote-access-gateway/install/install-portal.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/install/upgrade.md

  • Completeness — Line 19: The page says to upgrade the gateway, the portal, and guacd together but gives no order, and the gateway section doesn't say to check guacd at the same time. Suggested fix: "State the order (for example gateway, then guacd, then portal), or say that the order doesn't matter, and add a short checklist at the top."

docs/privilegesecure/26.07/remote-access-gateway/overview.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/requirements.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/troubleshooting.md

  • Clarity — Line 167: 'or press the keys on a different combination' is garbled and gives no instruction the reader can use. Suggested fix: "Say what to try instead, for example 'or use the toolbar button for that combination if your browser captures the keys'. Confirm against the product."

docs/privilegesecure/26.07/remote-access-gateway/user-guide/browser-sessions.md

No issues found.

docs/privilegesecure/26.07/remote-access-gateway/user-guide/sign-in.md

  • Clarity — Line 40: After SSO, step 4 says the browser returns to the portal dashboard. After username and password, line 57 says the portal opens My Activities and the dashboard is reached through the Home icon. The two flows contradict each other. Suggested fix: "Use the same landing page in both places (My Activities, if that is correct) and describe it once."

docs/privilegesecure/26.07/requirements/application-server.md

No issues found.

docs/privilegesecure/26.07/requirements/client.md

No issues found.

docs/privilegesecure/26.07/requirements/database.md

  • Clarity — Line 41: This line suggests a customer-provided PostgreSQL database for active-active, but the table says Netwrix provides PostgreSQL, and line 39 calls it 'embedded' while the table says 'bundled'. 'Active-passive' and 'active-active' aren't defined either. Suggested fix: "Add customer-provided PostgreSQL to the table or remove it here, use 'bundled' throughout, and define both configurations in a phrase."

docs/privilegesecure/26.07/requirements/licensing.md

  • Clarity — Line 15: Line 15 says that in all three conditions (count reached, trial expired, license service unreachable), existing users can still sign in but can't start sessions. Line 37 ties the no-sessions effect to an expired trial or no credits. The reader can't tell what happens when only the user count is reached. Suggested fix: "Describe each case separately: what happens at the count limit, when the trial expires, and when the license service is offline."

docs/privilegesecure/26.07/requirements/overview.md

No issues found.

docs/privilegesecure/26.07/requirements/ports.md

No issues found.

docs/privilegesecure/26.07/requirements/service-nodes.md

  • Clarity — Line 45: 'The Setup Launcher recommends that you disable antivirus software' conflicts with the paragraph before it, which says to exclude folders from scanning. The reader can't tell whether to disable antivirus or add exclusions. Suggested fix: "Say that the recommendation applies only during installation, and tell the reader to turn antivirus back on and add the exclusions afterward."

docs/privilegesecure/26.07/resources/ad-sync.md

No issues found.

docs/privilegesecure/26.07/resources/add-resources.md

No issues found.

docs/privilegesecure/26.07/resources/databases.md

No issues found.

docs/privilegesecure/26.07/resources/domains.md

  • Structure — Line 76: Delete removes the domain resource, the computer resources onboarded from it, its managed account credentials, and the sync job, but this appears in a plain paragraph after the tabs table. 'Resource groups still depend on the domain' isn't explained either. Suggested fix: "Put it in a :::warning under the buttons table, and say which resource groups block deletion and how to clear them."

docs/privilegesecure/26.07/resources/entra-id-tenants.md

No issues found.

docs/privilegesecure/26.07/resources/overview.md

No issues found.

docs/privilegesecure/26.07/resources/platforms/command-plans.md

No issues found.

docs/privilegesecure/26.07/resources/platforms/device-actions.md

  • Clarity — Line 54: The text says the PAN-OS plans 'also add and remove group membership', but the table (lines 22-23) lists Add to a group and Remove from a group as '(not supported)' for PAN-OS. Suggested fix: "Confirm the behavior, then remove the sentence or correct the table."

docs/privilegesecure/26.07/resources/platforms/password-complexity.md

No issues found.

docs/privilegesecure/26.07/resources/platforms/platforms.md

No issues found.

docs/privilegesecure/26.07/resources/platforms/schedule-policies.md

No issues found.

docs/privilegesecure/26.07/resources/protection-policies.md

No issues found.

docs/privilegesecure/26.07/resources/remove-resources.md

  • Completeness — Line 9: The page says removal deletes all records of the resource, but not what happens to active or scheduled sessions, access policies, managed credentials, or resource groups that reference it, or that the removal can't be undone. Suggested fix: "State the effect on each dependent item, whether active sessions block removal, and that removal can't be undone."

docs/privilegesecure/26.07/resources/resource-groups.md

  • Clarity — Line 51: Step 2 says selecting Map to OU or CN turns on Sync Now, but line 62 says Sync Now is unavailable until you save the group. The two statements conflict. Suggested fix: "Say that selecting Map to OU or CN shows Sync Now, and that it becomes available after you save."

docs/privilegesecure/26.07/resources/secret-vaults.md

No issues found.

docs/privilegesecure/26.07/resources/secure-winrm.md

No issues found.

docs/privilegesecure/26.07/resources/servers.md

  • Clarity — Line 58: The table says Allow Connection allows the connection and records a Warning event, the same as Log event and allow. Line 62 says Allow Connection doesn't compare the thumbprint at all, so it can't log a mismatch. Suggested fix: "Change the Allow Connection row to 'Allows the connection without comparing the thumbprint. No event is recorded.' Confirm against the product."

docs/privilegesecure/26.07/resources/websites.md

No issues found.

docs/privilegesecure/26.07/troubleshooting/ad-sync-and-scans.md

No issues found.

docs/privilegesecure/26.07/troubleshooting/enablement-toolkit.md

No issues found.

docs/privilegesecure/26.07/troubleshooting/overview.md

No issues found.

docs/privilegesecure/26.07/troubleshooting/services.md

  • Structure — Line 88: One paragraph holds a procedure (select Ignore HTTPS Certificate Errors, Save, Register Services), a file setting, and the security risk of skipping certificate validation. Suggested fix: "Turn the procedure into numbered steps, put the risk in a :::warning, and move the file detail into a note."

docs/privilegesecure/26.07/troubleshooting/sessions.md

  • Structure — Line 33: Line 9 says each entry has a symptom, cause, and fix, but this entry has no Cause, and the cause is buried in the Fix paragraph. The MFA entry at line 75 also has no Cause. Suggested fix: "Add a Cause: line (in earlier releases, cancelling a Running or Queued DisableUser action rescheduled in a loop) and keep the Fix to the upgrade. Do the same for the MFA entry."

docs/privilegesecure/26.07/user-guide/approve-requests.md

  • Clarity — Line 15: The email paragraph tells the approver about the Website URL setting, which only an administrator can change. An approver reading the user guide can't act on it. Suggested fix: "Rewrite for approvers: 'If the link opens the wrong address, ask your administrator to set the Website URL system setting.' Move the setting detail to the Email settings page."

docs/privilegesecure/26.07/user-guide/audit-sessions.md

  • Clarity — Line 59: The example says to enter a command name in Search. The filter table (line 42) says Search matches column values, and recorded keystrokes are searched with the Recording data filter (line 46), so the example may not find the command. Suggested fix: "Change the example to use Recording data, and state that Search doesn't search recording content."

docs/privilegesecure/26.07/user-guide/browser-extension/browser-extension.md

No issues found.

docs/privilegesecure/26.07/user-guide/browser-extension/use-browser-extension.md

No issues found.

docs/privilegesecure/26.07/user-guide/connect-own-client.md

No issues found.

docs/privilegesecure/26.07/user-guide/connect-session.md

  • Completeness — Line 28: For File sessions the console 'Downloads the encrypted file', but the page doesn't say how to decrypt or open it, so the reader has no next step. Suggested fix: "Add the decryption step or say where the key is, or link to the page that explains file access."

docs/privilegesecure/26.07/user-guide/my-activities.md

No issues found.

docs/privilegesecure/26.07/user-guide/my-sessions.md

  • Clarity — [idiom] Line 57: 'The provisioning stage hit an error' uses a figurative expression, and line 103 repeats it. Suggested fix: "Rewrite as 'An error occurred while Privilege Secure was preparing the session.' in both places."

docs/privilegesecure/26.07/user-guide/navigate-console.md

  • Clarity — Line 127: The alt text calls it the 'Product Walkthrough', but everywhere else the page calls it the 'Product Tour'. Suggested fix: "Use 'Product Tour' in the alt text."

docs/privilegesecure/26.07/user-guide/overview.md

No issues found.

docs/privilegesecure/26.07/user-guide/request-session.md

No issues found.

docs/privilegesecure/26.07/user-guide/review-access.md

  • Clarity — Line 27: Step 5 says Deny will 'remove' the access, but the note at line 48 says a denial doesn't remove the user from the access policy and only sets a deny flag. Suggested fix: "Change step 5 to 'or Deny to block it' and keep the note's explanation."

docs/privilegesecure/26.07/user-guide/servicenow-tickets.md

No issues found.

docs/privilegesecure/26.07/user-guide/sign-in.md

No issues found.

docs/privilegesecure/26.07/requirements/target-environments.md

  • Clarity — Line 37: The Linux row says the account is root or has delegated sudo permissions. Line 78 says to use a dedicated least-privilege account instead of root. The table doesn't say which one is recommended. Suggested fix: "Have the table row recommend the least-privilege account and say that root works but isn't recommended."

Summary

70 editorial suggestions across 67 files (169 files reviewed). Vale and Dale issues are auto-fixed separately.

Patterns across the set: Across the 26.07 set, the most common problems are statements that contradict each other within a page or between pages (Deny "removes" access vs. the note saying it doesn't; Allow Connection logs a Warning vs. never compares the thumbprint; PAN-OS group membership; RAG sign-in landing page), warnings and constraints placed after the steps they govern (encryption key rotate, data retention, SSH algorithms, policy overrides), and destructive actions (domain delete, resource remove) whose effects are given in plain prose instead of a warning.

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.

fixed 57 of these and added the others for human review.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

This run started because your comment quotes the Documentation PR Review, and the quoted "What to do next" section mentions @claude. Your own note ("fixed 57 of these and added the others for human review") reads as a status update, not a request, so I haven't changed any files.

If you want me to do something with the remaining suggestions, reply with a comment that starts with @claude and doesn't quote the review. For example:

  • @claude fix the remaining issues in docs/privilegesecure/26.07/install/upgrade.md: applies the suggestions for one file.
  • @claude check which review suggestions are still open: compares the review against the current branch and lists what's left, without editing.

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 0 skipped across 169 files

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

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Auto-Fix Summary

0 issues fixed, 0 skipped across 169 files

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

@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Code Review

I found no blocking issues in the config, script, or routing changes.

What I checked

  • products.js: 26.07 is now the latest and default version, and 26.03 is set to isLatest: false. The plugin ID privilegesecure26_07 matches docsPluginId in the new openapi-privilegesecure plugin. apiSidebarPath points to the gitignored sidebar.ts. loadApiSidebarItems returns [] until gen-api-docs has run, so loading the config doesn't fail before then. The info-doc filter (netwrix-privilege-secure-for-access-management-api) matches the slug of the spec's info.title.
  • Redirects: I checked all ~230 to targets in privilegesecure-26.03.js and privilegesecure-4.2.js against the 26.07 files on disk. Every target resolves, including the category-index routes with a trailing slash (admin/audit-reporting/, configuration/activities/, resources/platforms/, and others). None of the 26.07 _category_.json files use generated-index. As a result, no explicit from collides with an unversioned alias that createRedirects generates. The redirects are gated on activeProductIds.includes('privilegesecure'), so single-product builds of other products are unaffected.
  • package.json: The spec-prep and gen-api-docs steps are gated on DOCS_PRODUCT being unset or privilegesecure, the same pattern as changetracker and privilegesecurediscovery. They're added to prestart, prebuild, and preci. openapi:sync restores the tracked _category_.json afterwards.
  • scripts/prepare-privilegesecure-spec.mjs: The spec only uses #/components/schemas/* refs. It has no parameters, responses, or requestBodies components and no path-level parameters. Because of that, dropping components down to securitySchemes doesn't leave any dangling $ref. The allOf refs nested inside schemas are expanded by the recursive walk. Operation IDs are deduplicated. The script writes only to .generated/, which is gitignored, and doesn't use eval or the shell.
  • .gitignore: api/reference/* is ignored, with exceptions for _category_.json (which has customProps.isGeneratedApiSidebar) and index.md.

Minor, non-blocking

  • tidy() in the prep script deletes &lt;/&gt; entities and anything that looks like a tag. If any description contains a generic type (List&lt;Guid&gt; becomes ListGuid) or placeholder text such as <id>, that text is silently lost. Replacing the entities with ‹/›, or wrapping the text in backticks, would keep it.
  • The prep script handles only the $ref locations that appear in this spec. If a future spec adds path-level parameters or $refs to components/parameters or components/responses, those references will dangle after components is cut down. A guard that fails loudly on any unresolved $ref would catch that.
  • I didn't run a full build locally because it needs a 16 GB heap. CI's build will confirm that the MDX generated from the spec compiles.

🤖 Generated with Claude Code

@TylerReese
TylerReese merged commit fb7c051 into dev Nov 9, 2026
13 checks passed

This branch was previously deployed

1 inactive deployment
development — 0e84f445 Deployed Nov 9, 2026 by jth-nw via build-and-deploy #5083
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kb This change or issue involves Knowledge Base articles. privilege-secure This change or issue involves Privilege Secure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

KB review: docs(privilegesecure): add the 26.07 documentation (PR #1843)