You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Structure/Consistency — Line 230: The job path is written as 7.Certificate Authority > Collection > AD_CACollection, but every comparable collection job in this document uses a numbered Collection node — for example 5.Domains > 0.Collection > AD_DomainControllers (line 169) and 6.Activity > 0.Collection > AD_ActivityCollection (line 221). If the UI node is actually 0.Collection, this path is missing the 0. prefix and will not match what the reader sees in the product. Suggested fix: confirm the exact node name and align it with the established pattern, e.g. 7.Certificate Authority > 0.Collection > AD_CACollection.
Completeness — Lines 240–241: The info admonition tells the reader to "escalate incrementally (Read, then Enroll, then Officer, then Manage CA)," but these Certification Authority permission levels are introduced here without explanation. The requirements list above only mentions a single "Read permission," so a newer user has no reference point for what Enroll, Officer, or Manage CA grant or where to set them. Suggested fix: briefly note that these are the standard Certification Authority security roles assigned on the same Certification Authority console Security tab referenced in the requirements list, so the reader knows where to apply each level.
Completeness — Lines 240–243: The escalation guidance triggers on the job failing to collect "Certification Authority security, registry, or enrollment agent data," but the reader is not told which escalation step corresponds to which data type. This leaves the reader guessing how far up the ladder to go for a given failure. Suggested fix: if the mapping is known, indicate which permission level unlocks each data category (for example, which level enables enrollment agent data), or state that the reader should stop at the lowest level that resolves their specific failure.
Summary
3 editorial suggestions across 1 file. 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.
| docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md:24 — Dale: passive-voice | 'domain controllers to be scanned' — making it active would change who performs the scan; meaning ambiguous. |
| docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md:64 — Dale: passive-voice | 'The following firewall ports are needed:' — an active rewrite ('Open the following ports') would alter the meaning of a requirements intro. |
| docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md:190 — Dale: wordiness | 'just requiring access added to the winreg key' is awkward, but the intended relationship between the Lsa and winreg keys is ambiguous; a rewrite risks changing meaning. |
| docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md:203 — Dale: wordiness | 'just requiring access added to the winreg key' is awkward, but the intended meaning is ambiguous; a rewrite risks changing meaning. |
| docs/accessanalyzer/12.0/requirements/activedirectory/target/access.md:114 — Dale: passive-voice | 'which must be configured at the Domain level' has no natural active subject without adding assumptions. |
Ask @claude on this PR if you'd like an explanation of any fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
access-analyzerThis change or issue involves Access Analyzer.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.