netwrix · shannon-kelley-netwrix · Jul 16, 2025 · Jul 13, 2025
diff --git a/docs/platgovsalesforce/changemanagement/_category_.json b/docs/platgovsalesforce/changemanagement/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Change Management Overview",
+  "label": "Change Enablement",
   "position": 80,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/cleanup/_category_.json b/docs/platgovsalesforce/cleanup/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Clean Up Overview",
+  "label": "Clean Up Salesforce",
   "position": 90,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/customizations/_category_.json b/docs/platgovsalesforce/customizations/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Customizations Overview",
+  "label": "Customizations",
   "position": 70,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/index.md b/docs/platgovsalesforce/index.md
@@ -1 +1,97 @@
-# Strongpoint for Sales Force
+---
+title: "Welcome"
+description: "Welcome"
+sidebar_label: Netwrix Platform Governance for Salesforce
+sidebar_position: 1
+---
+
+# Welcome
+
+Platform Governance for Salesforce is integrated into the Salesforce backend keeping all your data
+within your Salesforce account. Your documentation is automatically maintained so it is always up to
+date.
+
+By implementing Platform Governance for Salesforce you can:
+
+- Automatically catalog all custom fields, scripts, forms, searches, records and workflows.
+- Visually browse standard and custom fields, lists and records to find all related scripts,
+  searches, users and departments.
+- Capture and search script comments and identify poorly commented code.
+- Automatically track changes to your customizations using the change logs, so you can see what
+  customizations were changed, how they were changed, when they were changed and who changed them.
+
+## Installation and Initial Scan
+
+Once you install Platform Governance for Salesforce, you simply click the **Start Spider** button
+and your customizations are documented over the course of 4-5 days with minimal impact on system
+performance. Once completed, you have a searchable database of all your customizations.
+
+## Documentation and Optimization
+
+After installation, it takes 4-5 days to document your customizations and approximately 3 weeks to
+have your account both fully documented and optimized.
+
+### Clean Up
+
+Use the end to end documentation of custom objects and our Clean Up Tools to:
+
+- Identify unused fields, searches and other custom objects.
+- Quickly identify dependencies to reduce the risk of breaking things in your account (i.e. see if a
+  search is being used in a script or workflow).
+- Use Change Requests to keep your changes organized and capture approvals.
+
+### Script Management
+
+Critical Script Analysis enables you to determine how healthy your scripts are and what areas you
+can fix to improve your account. With the tools and the Critical Script Analysis methodology you
+can:
+
+- Identify high priority scripts based on usage.
+- Identify people and departments triggering scripts to focus on scripts that could be
+  inappropriately triggered.
+- Understand script execution times.
+
+## Intelligent Change Management
+
+Platform Governance for Salesforce is the only application for Salesforce that enables end to end
+change management and compliance. This process can be achieved effectively in only 5 weeks after
+install.
+
+By implementing Platform Governance for Salesforce you give your customers the ability to:
+
+- Track all changes to custom objects in Salesforce.
+- Automatically be alerted to non-compliant changes.
+- Set compliance requirements by risks based on System Complexity and Processes that are then
+  automatically tracked.
+- Manage changes right in Salesforce by using the Change Request.
+- Use automated impact analysis to identify the risks associated with changing custom objects.
+- Use test records to manage tests in a central repository linked to the customization records.
+
+## Enterprise Compliance
+
+Once Intelligent Change Management is complete, it only takes between 3 to 4 weeks to achieve
+Enterprise Compliance.
+
+### Environment Comparison
+
+The Environment Management Module enables Salesforce customers and consultants to quickly and
+accurately identify differences between any two Salesforce accounts that have Intelligent Change
+Management installed. Since both accounts have Platform Governance for Salesforce documentation in
+place, the tool can quickly and easily compare them. It is principally used in four scenarios:
+
+- Sandbox Refreshes
+- Migrating Customizations Between Developer and Sandbox Accounts
+- User Acceptance Testing (UAT) and Performance Testing Environment Validation
+- Deploying Changes to Production
+
+### Automated Audit
+
+Agent automates IT and financial controls and critical change practices to ensure configuration and
+master data are compliant. It can:
+
+- Check for process problems regularly without user event scripts.
+- Automatically generate and assign tasks and cases for each detected problem.
+- Automatically alert key stakeholders.
+- Log control violations for clearance.
+- Store relevant data as a CSV to create a snapshot for compliance or troubleshooting purposes.
+- Block unauthorized changes to critical records and fields (requires Advanced Change Management).
diff --git a/docs/platgovsalesforce/installingstrongpoint/_category_.json b/docs/platgovsalesforce/installingstrongpoint/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Install Platform Governance for Salesforce",
+  "label": "Installation",
   "position": 20,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/integrations/jiraintegration/_category_.json b/docs/platgovsalesforce/integrations/jiraintegration/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Set Up the Jira Integration",
+  "label": "Jira",
   "position": 10,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/integrations/jiraintegration/jira_troubleshooting.md b/docs/platgovsalesforce/integrations/jiraintegration/jira_troubleshooting.md
@@ -53,7 +53,7 @@ Error message:
 
 error=invalid_client_id&error_description=client%20identifier%20invalid
 
-Refer to [Access Data with API Integration](/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md#access-data-with-apiintegration) for
+Refer to [Access Data with API Integration](/docs/platgovsalesforce/integrations/jiraintegration/jira_integration#access-data-with-apiintegration) for
 more information on setting up the connected app.
 
 ## Error with Consumer Secret

diff --git a/docs/platgovsalesforce/integrations/jiraintegration/jira_walkthrough_example.md b/docs/platgovsalesforce/integrations/jiraintegration/jira_walkthrough_example.md
@@ -53,7 +53,7 @@ The walkthrough demonstrates these steps:
 ### Connected App
 
 Use the **Connected App** tab if you set up the connected app using the procedure:
-[Access Data with API Integration](/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md#access-data-with-apiintegration)
+[Access Data with API Integration](/docs/platgovsalesforce/integrations/jiraintegration/jira_integration#access-data-with-apiintegration)
 
 1. Open the **Connected App** tab.
 

diff --git a/...alesforce/welcome/navigate_strongpoint.md → ...platgovsalesforce/navigate_strongpoint.md b/...alesforce/welcome/navigate_strongpoint.md → ...platgovsalesforce/navigate_strongpoint.md
@@ -1,7 +1,7 @@
 ---
 title: "Launch Platform Governance for Salesforce"
 description: "Launch Platform Governance for Salesforce"
-sidebar_position: 30
+sidebar_position: 7
 ---
 
 # Launch Platform Governance for Salesforce

diff --git a/docs/platgovsalesforce/releasemanagement/_category_.json b/docs/platgovsalesforce/releasemanagement/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Release Management Overview",
+  "label": "Release Management",
   "position": 110,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/scanner/_category_.json b/docs/platgovsalesforce/scanner/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Scanner Overview",
+  "label": "Scanner",
   "position": 40,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/scanner/running_scanner.md b/docs/platgovsalesforce/scanner/running_scanner.md
@@ -0,0 +1,9 @@
+---
+title: Manual Scanners
+description: "Manual Scanners"
+sidebar_position: 20
+---
+
+import ManualScanners from '/docs/platgovsalesforce/installingstrongpoint/running_scanner.md';
+
+<ManualScanners />
diff --git a/docs/platgovsalesforce/settings/_category_.json b/docs/platgovsalesforce/settings/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Settings Overview",
+  "label": "Settings",
   "position": 30,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/tools/_category_.json b/docs/platgovsalesforce/tools/_category_.json
@@ -1,5 +1,5 @@
 {
-  "label": "Tools Overview",
+  "label": "Tools",
   "position": 50,
   "collapsed": true,
   "collapsible": true,

diff --git a/docs/platgovsalesforce/welcome/_category_.json b/docs/platgovsalesforce/welcome/_category_.json
diff --git a/docs/platgovsalesforce/welcome/welcome.md b/docs/platgovsalesforce/welcome/welcome.md
diff --git a/...welcome/what_does_strongpoint_document.md → ...esforce/what_does_strongpoint_document.md b/...welcome/what_does_strongpoint_document.md → ...esforce/what_does_strongpoint_document.md
@@ -1,7 +1,7 @@
 ---
 title: "What is Documented"
 description: "What is Documented"
-sidebar_position: 20
+sidebar_position: 5
 ---
 
 # What is Documented

diff --git a/docs/platgovsalesforce/welcome/whatsnew.md → docs/platgovsalesforce/whatsnew.md b/docs/platgovsalesforce/welcome/whatsnew.md → docs/platgovsalesforce/whatsnew.md
@@ -1,7 +1,7 @@
 ---
 title: "What's New"
 description: "What's New"
-sidebar_position: 10
+sidebar_position: 3
 ---
 
 # What's New