Skip to content

Conversation

@hilram7
Copy link
Collaborator

@hilram7 hilram7 commented Jan 15, 2026

Summary

Updates the .NET Dependencies KB for Netwrix Access Analyzer:

  • Relocates KB from staging to correct product directory
  • Updates requirements link to current Access Analyzer docs
  • Replaces Salesforce-hosted image with local copy
  • Removes cross-product KB links (will be restored in a follow-up PR after all 5 products merge)

Changes

File Relocation

  • Moved net_dependencies_for_netwrix_access_analyzer.md from docs-staging/needs-relocation/ to docs/kb/accessanalyzer/reference-and-technical-specifications/

Requirements Link

  • Updated link from generic placeholder to current docs: https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/overview

Image Replacement

  • Added local PowerShell example image to docs/kb/accessanalyzer/0-images/ka0Qk000000DG8bIAG.png
  • Replaced Salesforce URL with relative path ../0-images/ka0Qk000000DG8bIAG.png

Cross-Product Links

  • Removed cross-product KB links for broken link prevention
  • Links will be restored in a follow-up PR after all 5 product KBs merge

Testing

  • ✅ Dev server: KB page loads correctly at /docs/kb/accessanalyzer/reference-and-technical-specifications/net_dependencies_for_netwrix_access_analyzer
  • ✅ Image displays properly from local path
  • ✅ Requirements link navigates to correct Access Analyzer docs
  • ✅ KB accessible from sidebar navigation
  • ✅ Build passes without errors

Related

  • Related PRs: Activity Monitor, Threat Prevention, Recovery AD, Threat Manager
  • Follow-up: Will restore cross-product KB links after all 5 merge

Hilary Ramirez added 3 commits January 15, 2026 10:01
- Moved KB from docs-staging/needs-relocation/ to reference-and-technical-specifications/
- Updated question text to remove Activity Monitor reference
- Added correct requirements link (accessanalyzer/12_0/requirements/overview)
- Restored cross-product .NET dependency KB links with correct paths
- Hyperlinked 'Netwrix Access Analyzer Requirements' to requirements page
- Simplified sentence to match new docs site structure
- Removed cross-product .NET KB links (will be restored in Phase 1 final PR)
- Added PowerShell example image locally (ka0Qk000000DG8bIAG.png)
- Updated image reference from Salesforce URL to relative path
- Keeps only Access Analyzer requirements link for clean CI build
@github-actions

This comment was marked as resolved.

@hilram7 hilram7 marked this pull request as ready for review January 16, 2026 22:03
@hilram7 hilram7 requested a review from a team as a code owner January 16, 2026 22:03
Copy link
Contributor

@tay-caliguiri tay-caliguiri left a comment

Choose a reason for hiding this comment

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

Can we remove any mention of StealthAUDIT v11.5 here because it is no longer supported?

@github-actions

This comment was marked as resolved.

Removed references to StealthAUDIT 11.5 dependencies from the documentation as it's no longer supported.
@github-actions

This comment was marked as resolved.

@github-actions

This comment was marked as resolved.

Copy link
Collaborator Author

@hilram7 hilram7 left a comment

Choose a reason for hiding this comment

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

Made requested update - removed v11.5 references

@github-actions

This comment was marked as resolved.

@github-actions
Copy link
Contributor

Pull Request Review - Access Analyzer .NET Dependencies KB

Overall Assessment

This is a well-executed documentation maintenance PR. The changes are clean, purposeful, and properly tested. The migration from staging to the proper product directory is correctly implemented.


✅ Strengths

1. Proper File Organization

  • Correct relocation from docs-staging/needs-relocation/ to docs/kb/accessanalyzer/reference-and-technical-specifications/
  • Follows the established KB documentation structure

2. Image Management

  • Good decision to replace external Salesforce-hosted image with local copy
  • Proper placement in docs/kb/accessanalyzer/0-images/
  • Correct relative path usage: ../0-images/ka0Qk000000DG8bIAG.png
  • Image file verified to exist (53,624 bytes)

3. Content Updates

  • Requirements link properly updated to current Access Analyzer docs
  • URL follows correct pattern: https://docs.netwrix.com/docs/accessanalyzer/12_0/requirements/overview

4. Documentation Quality

  • Frontmatter metadata is complete and consistent with other KB articles
  • Proper use of knowledge_article_id: kA0Qk0000001hxNKAQ
  • Tags and product metadata correctly formatted

5. Testing

  • Comprehensive testing checklist provided
  • Build validation completed

📝 Minor Observations & Suggestions

1. Content Refinement - Question Section (Line 23)

-Which version of .NET is required for Netwrix Access Analyzer?
+Which version of .NET is required for Netwrix Access Analyzer and related products?

The original question referenced "Netwrix Activity Monitor" which has been removed. The current question is accurate but could acknowledge that this KB specifically covers Access Analyzer (which is fine as-is since cross-product links were intentionally removed).

2. Consistency with Legacy Products List
The new version removes StealthAUDIT legacy products from lines 40-46 of the original:

- StealthAUDIT 11.5
- StealthAUDIT Access Information Center version 11.5
- StealthAUDIT Sensitive Data Discovery Add-on version 11.5
- StealthAUDIT File System Scanning Proxy (FSAA Proxy) 11.5

Question for consideration: Should these legacy StealthAUDIT entries be retained for customers still running older versions? Or is the cleanup intentional to focus on current supported versions?

3. Frontmatter - Product ID Inconsistency
The frontmatter uses:

products:
  - accessanalyzer

However, I noticed other KB files in the same directory use access-analyzer (with hyphen). For consistency, verify which is the correct product ID format used across the repository. Example from access-analyzer-version-numbers.md:

products:
  - access-analyzer

4. Related Articles Section
The new Related Articles section (lines 55-57) now only includes the requirements link. Consider whether this section provides sufficient value with just one link, or if it could be:

  • Expanded when cross-product links are restored
  • Temporarily removed until more relevant links are available
  • Enhanced with internal Access Analyzer documentation links

🔒 Security & Performance

  • ✅ No security concerns
  • ✅ Local image hosting eliminates external dependency on Salesforce
  • ✅ No performance issues introduced
  • ✅ Markdown file is lightweight (57 lines)

🧪 Testing Recommendations

Verify the following in your build:

  1. Image rendering: Confirm ka0Qk000000DG8bIAG.png displays correctly with relative path
  2. Link validation: Test the requirements link resolves to the correct page
  3. Sidebar navigation: Ensure the KB appears in the correct category
  4. Search indexing: Verify keywords are picked up properly if using Algolia search
  5. Frontmatter product ID: Confirm accessanalyzer (no hyphen) is correct vs access-analyzer

📋 Follow-up Items

As noted in your PR description, these items are already tracked:

  • ✅ Restore cross-product KB links after all 5 product KBs merge
  • ✅ Coordinate with related PRs for Activity Monitor, Threat Prevention, Recovery AD, and Threat Manager

🎯 Recommendation

Approve with minor verification

This PR is ready to merge after confirming:

  1. The product ID format (accessanalyzer vs access-analyzer) is correct
  2. Intentional removal of StealthAUDIT legacy product versions is approved
  3. Build passes and image renders correctly

The changes are well-structured, properly tested, and align with the repository's documentation standards.


Great work on the thorough testing and clear PR description! 🎉

@hilram7 hilram7 merged commit b144c0f into dev Jan 20, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants