diff --git a/.github/workflows/claude-documentation-fixer.yml b/.github/workflows/claude-documentation-fixer.yml
index 3bd497fa53..5c642e63bf 100644
--- a/.github/workflows/claude-documentation-fixer.yml
+++ b/.github/workflows/claude-documentation-fixer.yml
@@ -119,11 +119,11 @@ jobs:
Follow these steps in order:
- 1. Use `gh pr diff ${{ steps.pr-info.outputs.number }}` to identify which lines are part of the PR diff.
+ 1. Use `gh pr diff ${{ steps.pr-info.outputs.number }}` to get the diff. In the diff output, lines starting with `+` are lines added or changed by this PR. Lines starting with `-` were removed. Lines starting with a space are unchanged context lines.
2. Use `gh pr view ${{ steps.pr-info.outputs.number }}` to get the list of changed files, then read the full content of each changed markdown file.
- 3. Run all three review passes on each file per your instructions, but report ONLY issues on lines that are NOT part of the PR diff.
+ 3. Run all three review passes on the full content of each file. Report ONLY issues on lines that do NOT start with `+` in the diff — that is, lines that were not added or changed by this PR. This includes unchanged context lines (space prefix in the diff) and lines not shown in the diff at all.
4. You MUST write your results ONLY to `/tmp/preexisting-issues.md` — always, even if there are no issues. Do not post a comment. Do not write anything else. Use this exact format:
@@ -151,6 +151,7 @@ jobs:
python3 << 'PYTHON_EOF'
import os
import json
+ import re
import subprocess
pr_number = os.environ['PR_NUMBER']
@@ -164,24 +165,67 @@ jobs:
"Note: Automated fixes are only available for branches in this repository, not forks."
)
+ def normalize_issues(body):
+ """Normalize issue lines to single bullet points, same as the reviewer."""
+ src = body.split('\n')
+ result = []
+ i = 0
+ while i < len(src):
+ line = src[i]
+ # Convert heading format: ### Line N: ... → - Line N: ...
+ m = re.match(r'^#{1,6}\s+(Line \d+:.+)$', line)
+ if m:
+ result.append(f'- {m.group(1)}')
+ i += 1
+ continue
+ # Convert bold format: **Line N: title** + sub-bullets → - Line N: single line
+ m = re.match(r'^\*\*(Line \d+:.*?)\*\*\s*$', line)
+ if m:
+ title = m.group(1).rstrip('.')
+ i += 1
+ parts = []
+ while i < len(src) and re.match(r'^\s*[-*]\s+', src[i]):
+ sub = re.sub(r'^\s*[-*]\s+', '', src[i])
+ sub = re.sub(r'^(Issue|Fix|Description|Suggested change):\s*', '', sub, flags=re.IGNORECASE)
+ if sub.strip():
+ parts.append(sub.strip().rstrip('.'))
+ i += 1
+ combined = f'- {title}. {". ".join(parts)}.' if parts else f'- {title}.'
+ result.append(combined)
+ continue
+ result.append(line)
+ i += 1
+ return '\n'.join(result)
+
def normalize_body(body):
- """Keep only the expected structured content from the preexisting issues output."""
+ """Extract the ## Preexisting issues section without fluff, normalized to match reviewer format."""
idx = body.find('## Preexisting issues')
if idx == -1:
return '## Preexisting issues\nNone.'
body = body[idx:]
- clean_lines = []
- for line in body.split('\n'):
+ # Strip any footer Claude may have appended after a --- divider
+ footer_idx = body.find('\n---')
+ if footer_idx != -1:
+ body = body[:footer_idx]
+ # Strip any prose intro between the header and first subheading/content
+ lines = body.split('\n')
+ result = []
+ past_intro = False
+ for line in lines:
s = line.strip()
- if (s == '## Preexisting issues' or
- s.startswith('### ') or
- s.startswith('- Line ') or
- s == 'None.' or
- s == ''):
- clean_lines.append(line)
- while clean_lines and not clean_lines[-1].strip():
- clean_lines.pop()
- return '\n'.join(clean_lines)
+ if s == '## Preexisting issues':
+ result.append(line)
+ elif not past_intro:
+ if s.startswith('### ') or s == 'None.' or s == '':
+ if s:
+ past_intro = True
+ result.append(line)
+ # else: prose intro line — skip it
+ else:
+ result.append(line)
+ while result and not result[-1].strip():
+ result.pop()
+ return normalize_issues('\n'.join(result))
summary_path = '/tmp/preexisting-issues.md'
if os.path.exists(summary_path):
diff --git a/docs/platgovsalesforce/changemanagement/approving_change_request.md b/docs/platgovsalesforce/changemanagement/approving_change_request.md
index fe854a5e23..90cd48e87c 100644
--- a/docs/platgovsalesforce/changemanagement/approving_change_request.md
+++ b/docs/platgovsalesforce/changemanagement/approving_change_request.md
@@ -9,23 +9,22 @@ sidebar_position: 50
Approvers are populated from the Change/Approval Policy for the Change Request. Approval
notifications are sent when the Change Request owner advances the status to **Pending Approval**.
-1. Approver receives an email with a link to the Change Request.
+1. Approvers receive an email with a link to the Change Request.
2. When the Change Request opens, **Approve** and **Reject** buttons are available at the top of the
form:
- - If all approvers approve the Change Request, the status is changed to **Approved**. Implement
- the changes specified by the Change Request.
- If an approver rejects the Change Request, the status is changed to **Rejected**. You can
- return the Change Request to **In Progress**, edit it, and reset it to **Pending Approval** if
+ return the Change Request to **In Progress**, edit it, and re-submit it for approval if
there are errors or omissions.
3. Change Request owner [Completes and Validates the Change Request](/docs/platgovsalesforce/changemanagement/completing_change_request.md).
-Once the Change Request is approved, you cannot change the customizations attached to the Change
-Request.
+Once the Change Request is approved, you cannot change the customizations associated with it or make any other modifications to the record.
-You can add the **Strongpoint CR Approval Override** Permission Set to specific users. Users with
-this Permission Set can approve a Change Request independent of the governing policy. The default
-approve permission is no longer included with the System Administrator role. If you have a System
-Administrator or other user you want to be able to approve, assign the **Strongpoint CR Approval
-Override** Permission Set.
+You can add the **Netwrix CR Approval Override** Permission Set to specific users. Users with
+this Permission Set can approve a Change Request independently of the governing policy.
+
+:::note
+The default approve permission is no longer included with the System Administrator role. If you have a System
+Administrator or other users you want to be able to approve, assign the **Netwrix CR Approval Override** Permission Set.
+:::
diff --git a/docs/platgovsalesforce/changemanagement/change_log_reportfolder_dashboardfolder.md b/docs/platgovsalesforce/changemanagement/change_log_reportfolder_dashboardfolder.md
new file mode 100644
index 0000000000..83b2b202a2
--- /dev/null
+++ b/docs/platgovsalesforce/changemanagement/change_log_reportfolder_dashboardfolder.md
@@ -0,0 +1,72 @@
+# Change Log for ReportFolder and DashboardFolder
+
+## Overview
+This document describes the Change Log structure for Salesforce types "ReportFolder" and "DashboardFolder", following the Netwrix Style Guide.
+
+## Change Log Layout
+
+The Change Log is organized into two main panels:
+
+### 1. "GENERAL & COMPLIANCE" Panel
+
+#### Fields and Meanings:
+
+| Field | Description |
+|-------|-------------|
+| Actual Change Date | Timestamp of the effective change |
+| Customization Created By / Modified By | Users who created/last modified the customization record |
+| Customization | Link to the specific folder customization record |
+| Metadata Type | Indicates "ReportFolder" or "DashboardFolder" |
+| Reason | Explanation for the change (e.g., "Manual Update on Package") |
+| Package | The package where the change was logged |
+| Related Change Request | Reference to the associated Change Request (if any) |
+| Compliant Indicator | Compliance status according to the active policy |
+| Active | Whether the customization is currently active |
+
+### 2. "CHANGE DETAILS" Panel
+
+#### Fields and Meanings:
+
+| Field | Description |
+|-------|-------------|
+| Change Type | Type of operation (Added, Removed, Access Changed) |
+| Old Access Level / New Access Level | Previous and new access levels (e.g., View, Edit, Manage) |
+| Folder Access User | Target user who was granted or revoked access |
+| Parent Group | Public Group through which access was granted (if applicable) |
+| Parent Role | Role through which access was granted (if applicable) |
+| Change Overview | Human-readable explanation of the change |
+
+## Access Permission Behaviors
+
+### Parent Group
+- Direct user permission or via Role: "Parent Group" is empty
+- Permission through a Public Group: Shows the Public Group that provided the access
+
+### Parent Role
+- Direct user permission or via public group: "Parent Role" is empty
+- Permission through a Role: Shows the Role that provided the access
+
+## Additional Notes
+
+- Access changes are tracked with specific indicators:
+ - "Change Type" shows the nature of the modification
+ - When access is revoked, "Change Type" displays "Removed"
+- The layout is consistent for both ReportFolder and DashboardFolder
+- Complies with Netwrix public documentation on Customizations and Change Logs
+
+## UI Examples
+
+- GENERAL & COMPLIANCE panel (ReportFolder example)
+
+
+
+- CHANGE DETAILS panel (access change details)
+
+
+
+- Full Change Log view
+
+
+
+## References
+- Additional Information: https://docs.netwrix.com/docs/platgovsalesforce/changemanagement/using_change_logs
diff --git a/docs/platgovsalesforce/changemanagement/completing_change_request.md b/docs/platgovsalesforce/changemanagement/completing_change_request.md
index 77d9ac438f..f03d308078 100644
--- a/docs/platgovsalesforce/changemanagement/completing_change_request.md
+++ b/docs/platgovsalesforce/changemanagement/completing_change_request.md
@@ -6,9 +6,7 @@ sidebar_position: 60
# Completing and Validating a Change Request
-To complete and validate the Change Request:
-
-Once the changes are complete, validate the Change Request and mark it **Complete CR**.
+Once the changes are complete, validate the Change Request and mark it as **Completed** on the path.
1. Open **Change Requests** to view the list of Change Requests. You may have to change the filter
from **Recently Viewed**.
@@ -18,5 +16,4 @@ Once the changes are complete, validate the Change Request and mark it **Complet
you expected. Refer to [Comparing Environments](/docs/platgovsalesforce/tools/environment_comparison.md) for details.
5. View the **Open Non-Compliant Changes** or **Compliant Changes** Change Management Reports
(**Netwrix Dashboard** > **Reports** > **Change Enablement**).
-6. When all changes are validated, click **Complete CR** on the Change Request status bar to mark it
- Completed.
+6. When all changes are validated, click **Complete** on the path.
diff --git a/docs/platgovsalesforce/changemanagement/creating_change_request.md b/docs/platgovsalesforce/changemanagement/creating_change_request.md
index fb316eecb9..40527af75e 100644
--- a/docs/platgovsalesforce/changemanagement/creating_change_request.md
+++ b/docs/platgovsalesforce/changemanagement/creating_change_request.md
@@ -19,7 +19,7 @@ Data Record Change Requests are only available with an Enterprise Compliance lic
:::
1. Open the **Change Requests** tab.
-2. Click **New**
+2. Click **New**.
@@ -34,65 +34,102 @@ Data Record Change Requests are only available with an Enterprise Compliance lic
- **Is Release**: check if this change request represents a release. The customizations from all
the child change requests are rolled into this release for deployment.
-4. **Save** the **Change Request**. A confirmation is displayed when the change request is saved.
+4. Optionally, on this screen you can enter **Existing Customizations**.
- 
+ - Click **Add** button in the Customizations panel to add **Existing Customizations** to the Change Request.
-5. Add or change information as needed:
+ 
- - **External Change Request Number** and **External Link** are used for reference if the change
- request is coming from an external system.
- - **Completion Status**: select a status from the list. This operation can also be performed
- after you save the change request and proceed to Impact Analysis.
- - **Stage**: the type of change project: **Change Request**, **Development Project**,
- **Deployment Record**, or **Rollback Record**. This is an informational field.
- - **Change Request Group**: search for groups to add to this change request.
- - **Assigned BA**: search for a user to add as the assigned Business Analyst.
- - **Release**: search for the parent change request if this change request is part of a release.
+ - To search for existing Customizations, you can use different filters such as **Salesforce Type**, **Package**, **Last Modified By**, or search directly by **Name**.
-6. Expand the **Customizations** section. **Customizations** is selected by default. Click
- **Customizations** to access the **Add/Remove** function.
+ 
- 
+ - User can search and select multiple customizations from the list.
+ - Once finished, click **Confirm Selection**.
- - Click **Add/Remove** to add existing Customizations to the change request.
- 
+5. You can also enter the **Proposed Customizations** at this point.
- - Enter filters to search for existing customizations. For this example, the **Metadata
- Type** is set to **CustomField**. The matching customizations are displayed.
+ - Click **Add** button in the Proposed panel to add **Proposed Customizations** to the change request.
+
+ 
- 
+ - Enter the **API Name** and **Salesforce Metadata Type**. Click **+** to add additional
+ proposed customizations. This can be used in conjunction with customizations that already exist.
+ All **Customizations** and **Proposed Customizations** are evaluated to determine the change
+ level. The highest change level is used for the change request.
+ - Once finished, click **Confirm Selection**.
- - Select one or more customizations. Use **Search**, **First**, **Previous**, **Next** and
- **Last** to navigate through the list if needed.
- - Click **Add** to add the customizations to the **Selected Customizations** list. Continue
- adding your existing customizations.
- - Click **Save**.
+ :::tip Troubleshooting: Incorrect API Name Format in Proposed Customizations
-7. Click **Proposed Customizations** to enable the **Add/Remove** option if you want to create new
- customizations.
+ **Issue**
- - Click **Add/Remove**.
+ When creating Proposed Customizations, the system may return a validation error due to an incorrect API Name format.
- 
+ **Cause**
- - Click **+** (Add).
+ The API Name format varies depending on the Salesforce Type. Each type follows a specific naming structure.
- 
+ Examples:
- - Enter the **API Name** and **Salesforce Metadata Type**. Click **+** to add additional
- proposed customizations. Can be used in conjunction with customizations that already exist.
- All **Customizations** and **Proposed Customizations** are evaluated to determine the change
- level. The highest change level is used for the change request.
- - Click **Save**.
+ - **CustomField**
+ `Object_Name__c.Custom_Field_Name__c`
+
+ - **ValidationRule**
+ `Object_Name__c.Validation_Rule_Name`
+
+ Validations are implemented for multiple Salesforce Types, so using an incorrect format will cause the request to fail.
+
+ **Workaround**
+
+ If you are unsure about the correct API Name format for a specific Salesforce Type:
+
+ - Navigate to the **Customizations** tab.
+
+ - Filter an existing List View or create a new one.
+
+ - Select the desired Salesforce Type.
+
+ - Add the **API Name** column to the view.
+
+ - Review existing customizations to identify the correct format.
+
+ This allows you to reference real examples from your account and ensure the API Name follows the correct structure.
-8. Click **Save** on the **Edit Change Request** form when you are finished. The **Deployment**
- section is only applicable after the change request is approved.
+ :::
-Your change request is created.
+6. **Save** the **Change Request**. A confirmation is displayed when the change request is saved and the user is redirected to the record view page.
+
+ 
+
+7. Add or change information as needed:
+
+ You can edit available fields by clicking the pencil icon. The following sections are available for editing, provided that the Change Request status is **In Progress**:
+
+ ### Details
+
+ Edit basic information about the Change Request.
+
+ 
+
+ ### Customizations
+
+ Add or remove **Existing Customizations** from the Customizations tab.
+
+ 
+
+ ### Proposed Customizations
+
+ Add or remove **Proposed Customizations** from the Proposed Customizations tab.
+
+ 
+
+ ### Release & Deployment
+
+ Manage release-related settings and deployment information.
+
+ 
-
## Preparing the Change Request for Approval
@@ -100,60 +137,46 @@ Review the change request:
- Run Impact Analysis
- View the DRD
-- Send the Change Request for Approval
+- Submit the Change Request for Approval
### Run Impact Analysis
-Open the **Impact Analysis** tab and review the information on the tabs: **Can Be Safely Deleted or
-Modified**, **Cannot Be Safely Deleted or Modified**, and **Inactive Customizations**.
+Open the **Impact Analysis** tab and review the information on the tabs: **Can Be Safely Deleted or Modified**,
+**Cannot Be Safely Deleted or Modified**, and **Inactive Customizations**.
Here is an example of items on the **Cannot Be Safely Deleted or Modified** tab. The Customizations
and Impacted Customizations are links to each customization record.
-
-
-Use the **Edit** button to return to the change request and make any required modifications.
+
### View the DRD
-Open the **DRD** tab to review the dependency diagram. Use the **Edit** button to return to the
-change request and make any required modifications.
+Open the **DRD** tab to review the dependency diagram.
-
+
-### Send the Change Request for Approval
+### Submit the Change Request for Approval
Change request approvers are automatically assigned based on the policy. In this section, you can
add additional approvers, approver notes and begin the approval process.
-1. Click **Edit** to modify the change request.
-2. Expand the **Approval** section.
+ 
- 
+1. Add the approval information:
-3. Add the approval information:
-
- - **Approval Status**: updates the status of the change request. Typically used for editing
- existing change requests. Set the **Approval Status** to **Pending Approval** when you are
- ready.
- - **Stage**: the type of change project: **Change Request**, **Development Project**,
- **Deployment Record**, or **Rollback Record**. This is an informational field.
- - **Approver Notes**: optional notes about the change request.
- - **Additional Approvers**: any additional approvers. Mandated approvers are set by the policy.
+ - **Additional Approvers**: Add any additional approvers. Mandated approvers are set by the policy.
Click **Add/Remove** and select approvers.
-4. Click **Save**.
+ - **Approver Notes**: optional notes about the change request.
- 
+2. Click **Save**.
-5. Click **Submit for Approval** to start the process. Approval notifications are sent to the
+3. Click **Submit for Approval** on the path to start the approval process. Approval notifications are sent to the
approvers.
-:::note
-If you created the Change Request in your sandbox to determine the scope of the change, recreate it
-in your Production environment to enable approvals and ongoing tracking.
-:::
+ 
+
+:::note
For new objects that do not yet exist in Production, edit the Change Request and enter the full API
-Names of these objects into the Proposed Customization fields in the Scope Section. You can add
-multiple API Names by using the Add button. Save the Change Request when complete.
+Names of these objects into the Proposed Customization fields in the Scope Section. You can add
\ No newline at end of file
diff --git a/docs/platgovsalesforce/changemanagement/using_change_logs.md b/docs/platgovsalesforce/changemanagement/using_change_logs.md
index 774392cc81..832cac6b73 100644
--- a/docs/platgovsalesforce/changemanagement/using_change_logs.md
+++ b/docs/platgovsalesforce/changemanagement/using_change_logs.md
@@ -10,20 +10,18 @@ Change Logs allow you to see the type of change, who made the change and view th
the Salesforce record. Change Logs are accessed from the **Change Logs** tab or through
[Change Enablement Reports](/docs/platgovsalesforce/changemanagement/change_management_reports.md).
-1. Expand the **Change Logs** tab.
+1. Click on **Change Logs** tab.
2. Change the **Recently Viewed** pinned list to show the types of Change Logs to view. For
- example**, Data tracking Changes** or **Profile and PermissionSet** changes. The **Details** and
+ example, **Data Tracking Changes** or **Profile and PermissionSet** changes. The **Details** and
**Diff Summary** differ slightly depending on the selected **Metadata Type**.
3. Click a **Change Log Name** to open it.
You can also open Change Logs from **Netwrix Dashboard** > **Reports** > **Change Enablement**.
Select a report, such as **What Changed** to see a list of Change Logs.
-
+Here is an example change log for a **CustomObject** Metadata type.
-Here is an example change log for a **Profile** Metadata type.
-
-
+
## Details Tab
@@ -34,24 +32,18 @@ Here is an example change log for a **Profile** Metadata type.
- **Metadata Type**: Salesforce metadata type of the Customization.
- **Field Name**: Name of the changed field.
- **Active**: Checked if the Customization is active.
-- **New Customization**: Checked if new customization.
-- **Package**: Name of the Managed Package if the customizations belong to a managed package.
-- **Operation**: Flag this field if a change or a new record is created.
+- **New Customization**: Checked if this is a new customization.
+- **Package**: Name of the Managed Package if the customization belongs to a managed package.
+- **Operation**: Flags whether a change was made, a new record was created or deleted.
- **Change Overview**: Overview of the change.
-- **Data Record Id**: ID of the data record changed. This field is not in all Metadata Types.
-- **Data Record Name**: Name of the data record changed. This field is not in all Metadata Types.
-- **Data Record SObject API**: API name of the parent SObject of the data record changed. This field is not in all Metadata Types.
-- **Related Change Request**: Change request related to the change or used to perform regression analysis of a non-compliant change.
+- **Related Change Request**: Change request related to the change or used to perform regression analysis of a non-compliant change. This field is editable.
- **Compliant Indicator**: Green flag indicates compliant, red flag indicates non-compliant.
- **Non-Compliant**: Checked if the change is non-compliant.
- **Compliance**: The change status: **Compliant** or **Non-compliant**.
- **Policy**: Policies associated with the Change Log.
- **Reason**: Name of the policy violated by the change.
-- **Filters**: List of filters satisfied for the data record change. If blank, no filters specified. This field is not in all Metadata Types.
-- **Parent Change Log**: Name of the parent change log if applicable.
-- **Resolution Description**: Description of any steps taken to bring the change back into compliance. This field is not in all Metadata Types.
-- **Short Resolution Description**: Summary description of any steps taken to bring the change back into compliance.
-- **Status**: Current state of the Change Log. This field is manually set.
+- **Short Resolution Description**: Summary description of any steps taken to bring the change back into compliance. This field is editable.
+- **Status**: Current state of the Change Log. This field is editable.
### Diff Summary
@@ -60,18 +52,21 @@ There is an **Export to PDF** option.
Example Diff Summary for a Data tracking Change Log:
-
+
-Example Diff Summary for a Profile metadata type Change Log:
+Example Diff Summary for a **CustomObject** metadata type Change Log:
-
+
### Values
The **Values** section displays the **New Value** and **Old Value** of each field after the update.
+
+
+
The **Created By** and **Last Modified By** users and dates are displayed at the end of the list.
-
+
### Audit
diff --git a/docs/platgovsalesforce/customizations/folder_customization_record.md b/docs/platgovsalesforce/customizations/folder_customization_record.md
new file mode 100644
index 0000000000..111e53355d
--- /dev/null
+++ b/docs/platgovsalesforce/customizations/folder_customization_record.md
@@ -0,0 +1,67 @@
+# Report and Dashboard Folder Customization
+
+## Overview
+This document describes the Netwrix customizations for Salesforce types ReportFolder and DashboardFolder.
+
+## Detailed Customization Description
+
+### 1. Folder Types
+- **Report Folders**: Contain Salesforce reports
+- **Dashboard Folders**: Contain Salesforce dashboards
+- Folders can be shared with users or public groups
+- Supports hierarchical folder structures with subfolders
+
+### 2. Detection Mechanism
+- Changes detected during Netwrix daily scan
+- Frequency depends on configured scan schedule
+
+### 3. Related Objects
+- Folders can have relationships with:
+ - Groups/Roles through access permissions
+ - Other folders (parent-child relationships)
+
+
+
+### 4. Metadata Information
+- Includes:
+ - Customization name
+ - Salesforce type
+ - Package details
+ - Active/Managed status
+ - Creation and modification timestamps
+
+
+
+### 5. Folder Sharing Settings
+- Access levels:
+ - View access
+ - Manage access
+- Sharing settings apply to all subfolders
+- Can be granted to:
+ - Individual users
+ - Public groups
+ - Roles
+
+
+
+
+
+
+
+
+### 6. Change Logging
+- Tracks changes to access permissions
+- Logs include:
+ - Who made the change
+ - Timestamp of change
+ - Type of modification (add/modify/remove)
+
+### 7. Metadata Storage
+- XML attachment stores:
+ - Folder structure details
+ - Access levels for users, groups, and roles
+
+
+
+## References
+- Additional Information: https://docs.netwrix.com/docs/platgovsalesforce/customizations/understanding_customization_record
diff --git a/docs/platgovsalesforce/installingstrongpoint/config_and_stats.md b/docs/platgovsalesforce/installingstrongpoint/config_and_stats.md
index a1c2c7a350..f21e32a843 100644
--- a/docs/platgovsalesforce/installingstrongpoint/config_and_stats.md
+++ b/docs/platgovsalesforce/installingstrongpoint/config_and_stats.md
@@ -25,6 +25,7 @@ The report is divided into multiple tabs:
- Scanner Logs
- Scanner Additional Information
- Change Log Creation (sandbox option)
+- Scanner Inactivity Alert
- Jira Configuration
- Credentials
- Status Mapping
@@ -64,9 +65,9 @@ The section displays details for each of the scanner logs:
This section only applies to sandbox orgs. It displays each scanner function and the status:
-- Last Scanner Run Date
-- Last Automated Scanner Run Date
-- Last Scanner Run Status
+- **Last Scanner Run Date**: The date and time when the scanner was last run manually.
+- **Last Automated Scanner Run Date**: The date and time when the scanner last ran on its automated schedule.
+- **Last Scanner Run Status**: Indicates the type of the most recent scanner execution (manual or automated).
@@ -79,6 +80,62 @@ you may want to disable change logs to save space.
+## Scanner Inactivity Alert
+
+The Scanner Inactivity Alert feature provides automated email notifications to designated administrators when the Auto Scanner fails to run according to its configured schedule. This proactive monitoring ensures that your Salesforce environment remains continuously protected.
+
+
+
+### Configuration Steps
+
+#### Step 1: Enable Scanner Inactivity Alert
+
+1. **Locate the Enable Checkbox**
+ - Find the checkbox labeled "Enable Scanner Inactivity Alert"
+
+2. **Enable the Feature**
+ - Select the checkbox to enable scanner inactivity alerts
+ - Once enabled, the Admin Users Selection panel appears below
+
+#### Step 2: Select Admin Users
+
+After enabling the alert, configure the recipients.
+
+##### Admin Users Selection Panel
+
+A multi-select list displays available administrator users.
+
+##### Select Recipients
+
+The system lists all Salesforce users with the System Administrator profile.
+
+
+
+Use the multi-select panel to manage recipients:
+
+- **Search**: Type to filter admin users by name
+- **Select**: Click a user to add them to the recipient list
+- **Remove**: Click a selected user again to remove them
+- Multiple users can be selected
+
+##### Review Selection
+
+- Confirm all intended recipients are selected
+- For redundancy, consider selecting more than one admin
+
+#### Step 3: Save Configuration
+
+##### Save Settings
+
+1. Click **Save Configuration** at the bottom of the page
+2. A loading spinner appears while the configuration is saved
+3. Wait for the confirmation message
+
+
+#### Alert Trigger Conditions
+
+The system continuously monitors the Auto Scanner and sends email alerts when it detects that the scanner is not running as configured in the scheduler.
+
## Jira Configuration
Use these features to enter your Jira credentials and map the statuses between Jira and Platform
diff --git a/docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md b/docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md
index fedde00e52..488b89a9d6 100644
--- a/docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md
+++ b/docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md
@@ -20,43 +20,108 @@ The installation runs in the background. An email notification is sent to you wh
is complete.
:::
-## Configure Platform Governance for Salesforce
+## Configure Authentication
-**Requirements**
+After installing the package, you need to configure authentication credentials. Platform Governance for Salesforce supports two authentication methods:
-- Create a **Connected App** to generate and extract the Salesforce **Consumer Key** and the
- Salesforce **Consumer Secret Key**
-- Your Salesforce **username**, **password** and **authentication token**
+### Recommended: Named Credential Authentication (OAuth)
-**Installation**
+**This is the recommended approach** for all organizations, and is **required** when High Assurance is enabled on user profiles.
-1. Open Salesforce **Setup** > **Apps** > **App Manager**
-2. Click **New Connected App**
-3. Select **Create a Connected App** and click **Continue**
-4. Under **Basic Information** enter the required fields:
+Named Credentials provide:
+- **High Assurance compatibility** - Required when Salesforce profiles have High Assurance enabled
+- **Independent authentication** - Does not rely on specific user credentials, improving security and reliability
+- **Automatic token refresh** - No session expiration issues
+- **Enhanced security** - Limited OAuth scopes instead of full user permissions
- - **Connected App Name**: **Netwrix Platform Governance**
- - **API Name**: **Netwrix_Platform_Governance**
- - **Contact E-mail**
+:::tip Recommended Setup
+For detailed step-by-step instructions on configuring Named Credentials with External Client App and OAuth, see [Named Credential Setup](named_credential.md).
+:::
+
+### Legacy: Session ID Authentication
+
+The traditional method uses direct user credentials (username, password, and security token) to authenticate API calls. **This method does not require a Connected App**, but has significant limitations:
+
+- **Does not work with High Assurance** - Fails when High Assurance is enabled on user profiles
+- **User-dependent** - Relies on specific user credentials; if using this method, we recommend creating a dedicated Integration User for this purpose
+
+:::warning High Assurance Incompatibility
+If your Salesforce organization has **High Assurance enabled on user profiles**, you **must** use the Named Credential authentication method. Session ID authentication will not work with High Assurance. While High Assurance is often associated with MFA requirements, it is the High Assurance setting itself that makes Named Credentials mandatory.
+:::
+
+
+Legacy Session ID Setup
+
+This method uses direct user credentials without requiring a Connected App setup.
+
+**Requirements:**
+- Salesforce **username** (we recommend using a dedicated Integration User)
+- Salesforce **password**
+- Salesforce **security token** (obtained from user settings)
+
+**Configuration:**
+The credentials are entered directly in the Platform Governance application during the Getting Started Wizard. No Connected App or OAuth configuration is needed.
+
+**Best Practice:**
+When using Session ID authentication, create a dedicated Integration User specifically for Platform Governance. This approach provides better control and reduces dependencies on individual user accounts.
+
+**Limitations:**
+- Cannot be used if High Assurance is enabled on user profiles
+- Depends on specific user credentials, creating maintenance overhead
+- Not suitable for organizations with High Assurance requirements
+
+
+
+## Assign Permission Set to Users
+
+After configuring authentication, you must assign the required Permission Set to users who will access Platform Governance for Salesforce.
+
+### Assign Netwrix Grant Permissions
+
+1. Navigate to **Setup** > **Users** > **Permission Sets**
+2. Search for and click on **Netwrix Grant Permissions**
+
+3. Click **Manage Assignments**
+
+4. Click **Add Assignments**
+
+5. Select the users who need access to Platform Governance for Salesforce
+6. Click **Assign**
+7. Click **Done**
+
+:::note Required Permission Set
+The **Netwrix Grant Permissions** permission set is required for all users who will access the Netwrix Lightning application. Without this permission set, users will not be able to use Platform Governance for Salesforce.
+:::
+
+### Verify Permission Assignment
+
+To verify that the permission set has been assigned correctly:
+
+1. Navigate to **Setup** > **Users** > **Users**
+2. Click on a user who should have access
+3. Scroll to the **Permission Set Assignments** section
+4. Verify that **Netwrix Grant Permissions** appears in the list
+
+## Access the Netwrix Lightning Application
+
+After configuring authentication (either Named Credentials or Session ID), access the Platform Governance application:
-5. Click **API (Enable OAuth Settings)** to expand the section.
-6. Set **Call Back URL** to **[https://localhost.com](https://localhost.com)**
-7. Set **Selected OAuth Scopes** to **Full access (full)**
+1. Open the Salesforce **App Launcher** (grid icon in the top navigation)
+2. Search for and select **Netwrix Lightning**
+
+3. A window will appear displaying the License Agreement and EULA. Please review the contents carefully and then select **Accept**.
- 
+
- **The Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows**
- should not be checked.
+You are now ready to begin using Platform Governance for Salesforce.
-8. Click **Save**. **Netwrix Platform Governance**is now listed under **Custom Apps**.
-9. Click on **Netwrix Platform Governance**.
+## Next Steps
- 
+After completing the installation and authentication setup:
-10. Click **Manage Consumer Details**. You must verify your identity before you can proceed.
-11. Copy the **Consumer Key** and the **Consumer Secret Key**.
-12. Open the Salesforce App Launcher.
-13. Locate and select **Netwrix Lightning**.
-14. Click **I Accept** for the EULA.
+1. **Configure Authentication:**
+ - **Recommended:** [Named Credential Setup](named_credential.md) - Required for High Assurance profiles, recommended for all organizations
+ - **Legacy:** Session ID setup - Only for organizations without High Assurance
-**Next Step:** [Run the Getting Started Wizard](/docs/platgovsalesforce/installingstrongpoint/using_getting_started_wizard.md)
+2. **Initial Configuration:**
+ - [Run the Getting Started Wizard](using_getting_started_wizard.md)
\ No newline at end of file
diff --git a/docs/platgovsalesforce/installingstrongpoint/license_manager.md b/docs/platgovsalesforce/installingstrongpoint/license_manager.md
index 10f57177b0..44162c342c 100644
--- a/docs/platgovsalesforce/installingstrongpoint/license_manager.md
+++ b/docs/platgovsalesforce/installingstrongpoint/license_manager.md
@@ -15,13 +15,12 @@ Click **Configuration and Stats** in the **Resources** section, or open **Settin
## Upgrade or Downgrade a License
-1. Send a request for an upgrade or downgrade to Netwrix support:
- [sp.support@netwrix.com](mailto:sp.support@netwrix.com?subject=Salesforce_Support)
+1. Send a request for an upgrade or downgrade to [Netwrix support](https://www.netwrix.com/support.html).
When you contact support, you must provide your **Instance ID** (**Setup** > **Company
Settings** > **Company Information**)
A representative will contact you and provide an authorization token.
2. Open **Netwrix Dashboard** > **Settings** > **Upgrade/Downgrade Package**
-3. Copy and paste the **Authorization Token**
+3. Copy and paste the **License Key**
4. Click **Accept**
diff --git a/docs/platgovsalesforce/installingstrongpoint/named_credential.md b/docs/platgovsalesforce/installingstrongpoint/named_credential.md
new file mode 100644
index 0000000000..ca9c13dd57
--- /dev/null
+++ b/docs/platgovsalesforce/installingstrongpoint/named_credential.md
@@ -0,0 +1,199 @@
+---
+title: "Named Credential Setup"
+description: "Configure Platform Governance for Salesforce using Named Credential authentication"
+sidebar_position: 15
+---
+
+# Named Credential Setup
+
+This guide explains how to configure Platform Governance for Salesforce using an External Client App for authentication. This configuration uses OAuth authentication exclusively to call Salesforce APIs and document all Salesforce metadata types.
+
+## Overview
+
+The legacy method uses user Session IDs which are incompatible with Profiles with High Assurance. The new configuration uses an External Client App with Named Credentials to access Salesforce APIs, providing a more secure and MFA-compatible authentication method.
+
+## Why Use Named Credentials
+
+Using Named Credentials with External Client App OAuth authentication is the recommended approach over using user Session IDs for several critical reasons:
+
+### High Assurance Compatibility
+
+**This is the primary reason for using Named Credentials.** When Salesforce organizations have High Assurance enabled—which is increasingly required by Salesforce and security best practices—user Session IDs do not work properly for API calls. The Session ID authentication method fails because:
+
+- **Enabling High Assurance Session on the Named Credential ensures that only Named Credentials work for authentication**, providing an additional security layer that ensures MFA compliance
+
+### Enhanced Security
+
+- **Session IDs inherit all permissions** of the authenticated user, creating potential security risks
+- **External Client Apps with OAuth** allow you to define specific scopes and limit API access to only what's needed
+- Named Credentials provide better audit trails and can be monitored independently
+- Credentials are stored securely by Salesforce and never exposed in code or logs
+
+### Automation and Scheduled Jobs
+
+- Automated processes and scheduled jobs cannot rely on user Session IDs
+- Named Credentials provide persistent authentication that works independently of user sessions
+- Ideal for background processes, scheduled scans, and continuous monitoring
+
+## Prerequisites
+
+- Salesforce Administrator access
+- Access to Setup menu
+
+## Step 1: Create an External Client App
+
+:::important
+If this is not a new installation and your org already has an existing Connected App named **Netwrix** or **Strongpoint**, you don't need to create a new one.
+
+You can use the existing app and continue to [Step 2: Create an Auth Provider](#step-2-create-an-auth-provider).
+
+If you don't have the Consumer Key and Consumer Secret saved, go to [Retrieve Consumer Key and Secret](#retrieve-consumer-key-and-secret), obtain the credentials, and then continue with [Step 2: Create an Auth Provider](#step-2-create-an-auth-provider).
+:::
+
+Create a new External Client App to enable OAuth authentication:
+
+1. Navigate to **Setup** > **Apps** > **App Manager**
+2. Click **New External Client App**
+3. Configure the following settings:
+ - **External Client App Name**: `Netwrix`
+ - **API Name**: `Netwrix` (auto-populated)
+ - **Contact Email**: Enter your administrator email
+ 
+4. Under **API (Enable OAuth Settings)**:
+ - **Callback URL**: `https://www.localhost.com` (we will modify this parameter later)
+ - **Selected OAuth Scopes**: Add the following scopes:
+ - **Full access (full)**
+ - **Perform requests at any time (refresh_token, offline_access)**
+ 
+
+5. **Uncheck** the following options:
+ - Require Secret for Web Server Flow
+ - Require Secret for Refresh Token Flow
+ 
+
+6. Click **Create**
+
+### Configure Session and Token Policies
+
+After creating the External Client App:
+
+1. From the External Client Apps Menu, locate the **Netwrix** External Client App
+2. Click the dropdown and select **Edit Policies**
+ 
+3. Configure the following:
+ - **Refresh Token Policy**: Set to **Refresh token is valid until revoked**
+ - **IP Relaxation**: Set to **Enforce IP restrictions**
+ - **Session Timeout In Minutes**: Set to **1440**
+ 
+
+4. Click **Save**
+
+### Retrieve Consumer Key and Secret
+
+1. From the **Netwrix** External Client App detail page
+
+2. Click **Consumer Key and Secret** From the OAuth Settings section
+
+3. Verify your identity (you may need to enter a verification code)
+4. Copy and save the **Consumer Key** and **Consumer Secret** - you'll need these in the next step
+
+## Step 2: Create an Auth Provider
+
+Create a new Authentication Provider to enable OAuth authentication:
+
+1. Navigate to **Setup** > **Identity** > **Auth. Providers**
+2. Click **New**
+3. Configure the following settings:
+ - **Provider Type**: Salesforce
+ - **Name**: `Strongpoint MFA` (this exact name is required)
+ - **Consumer Key**: Enter the Consumer Key from the External Client App created in Step 1
+ - **Consumer Secret**: Enter the Consumer Secret from the External Client App created in Step 1
+ - **Authorize Endpoint URL**:
+ - For Sandbox: `https://test.salesforce.com/services/oauth2/authorize`
+ - For Production: `https://login.salesforce.com/services/oauth2/authorize`
+ - **Token Endpoint URL**:
+ - For Sandbox: `https://test.salesforce.com/services/oauth2/token`
+ - For Production: `https://login.salesforce.com/services/oauth2/token`
+4. Leave all other fields at their default values
+
+
+5. Click **Save**
+
+### Update External Client App Callback URL
+
+After creating the Auth Provider:
+
+1. Copy the **Callback URL** displayed on the Auth Provider detail page
+
+2. Navigate back to **Setup** > **External Client Apps** > **External Client App Manager**
+3. Locate the **Netwrix** External Client App
+4. Click the dropdown and select **Edit Settings**
+5. Replace the **Callback URL** with the URL copied from the Auth Provider
+
+6. Click **Save**
+
+## Step 3: Create a Named Credential
+
+Create a Named Credential to establish the authentication connection:
+
+1. Navigate to **Setup** > **Security** > **Named Credentials**
+2. Click **New Named Credential** (or **New Legacy** if using Enhanced Named Credentials)
+3. Configure the following settings:
+ - **Label**: `Strongpoint MFA`
+ - **Name**: `Strongpoint_MFA` (auto-populated)
+ - **URL**: Enter your Salesforce base URL
+ - You can find this in **Setup** > **Company Settings** > **My Domain**
+ - **Identity Type**: Named Principal
+ - **Authentication Protocol**: OAuth 2.0
+ - **Authentication Provider**: Select `Strongpoint MFA` (created in Step 2)
+ - **Scope**: `refresh_token full`
+ - **Start Authentication Flow on Save**: Checked
+ - **Generate Authorization Header**: Checked
+ - **Allow Merge Fields in HTTP Body**: Checked
+ 
+4. Click **Save**
+
+:::tip High Assurance Session
+Enabling **Require High Assurance Session** ensures that the Named Credential can only be used after a high-assurance authentication event. This setting enforces the use of Named Credentials and provides an additional layer of security. For more information, see [Salesforce High Assurance Sessions documentation](https://help.salesforce.com/s/articleView?id=xcloud.security_auth_require_ha_session.htm&type=5).
+:::
+
+### Authenticate the Named Credential
+
+After saving:
+
+1. You will be redirected to the Salesforce login page
+2. Log in with your credentials
+3. Click **Allow** to grant access
+
+
+4. You will be redirected back to the Named Credential record
+5. Verify that the **Authentication Status** shows as **Authenticated**
+
+
+## Verification
+
+Once all steps are completed:
+
+- The External Client App should have OAuth enabled with the correct scopes
+- The Auth Provider should be configured with the correct endpoints
+- The Named Credential should show an **Authenticated** status
+
+Your Platform Governance for Salesforce is now configured to use External Client App authentication with Named Credentials.
+
+## Troubleshooting
+
+If you encounter authentication issues:
+
+- Verify that the Consumer Key and Consumer Secret match between the External Client App and Auth Provider
+- Ensure the Callback URL in the External Client App matches the one from the Auth Provider
+- Check that the Named Credential shows an **Authenticated** status
+- Verify that the correct endpoint URLs are used (Sandbox vs. Production)
+- Ensure all required OAuth scopes are selected in the External Client App
+- Confirm that My Domain is properly configured in your Salesforce org
+- Verify that IP Relaxation is enabled in the External Client App policies
+
+## Next Steps
+
+After completing the credentials setup, proceed to:
+
+- [Run the Getting Started Wizard](using_getting_started_wizard.md)
\ No newline at end of file
diff --git a/docs/platgovsalesforce/installingstrongpoint/running_scanner.md b/docs/platgovsalesforce/installingstrongpoint/running_scanner.md
index 983328000e..771aba1398 100644
--- a/docs/platgovsalesforce/installingstrongpoint/running_scanner.md
+++ b/docs/platgovsalesforce/installingstrongpoint/running_scanner.md
@@ -33,6 +33,8 @@ To run the scanner:
6. From the Netwrix Dashboard: click **Configuration and Stats** in the **Resources** section, or
open **Settings** > **Configuration and Stats**.
+## Creating a Custom View for Scanners
+
You can create your own Salesforce view for the scanners:
1. Open Salesforce **Setup**.
@@ -42,8 +44,8 @@ You can create your own Salesforce view for the scanners:
4. Enter a **View Name**. The system assigns **View Unique Name**. _Netwrix Jobs1_ is used in this example.
5. Select **Apex Class** for the **Field**.
6. Select **starts with** for the **Operator**.
- 7. Assign **FLO, Strongpoint** for the **Value**.
+ 7. Assign **FLO, Strongpoint, NetPG** for the **Value**.
8. Click **Save**. You can now see the status of all of the Strongpoint jobs.
- 
+ 
**Next Step:** [Validate the Data ](/docs/platgovsalesforce/installingstrongpoint/validating_data.md)
diff --git a/docs/platgovsalesforce/installingstrongpoint/setting_access_permission.md b/docs/platgovsalesforce/installingstrongpoint/setting_access_permission.md
index c56add3e70..afe4a269a0 100644
--- a/docs/platgovsalesforce/installingstrongpoint/setting_access_permission.md
+++ b/docs/platgovsalesforce/installingstrongpoint/setting_access_permission.md
@@ -19,10 +19,22 @@ access to other users:
-5. Select **Strongpoint Grant Permissions** from the **Available Permission Sets**
+5. Select **Netwrix Grant Permissions** from the **Available Permission Sets**
6. Click **Add**. It should now be shown in the **Enabled Permission Sets**.
7. Click **Save**.
The user is ready to view and use Platform Governance for Salesforce.
+
+:::note
+The previous image shows additional Permission Sets included in the package. Below is a brief description of each:
+ - **Netwrix Administrator**
+ Provides access to Netwrix configuration settings.
+
+ - **Netwrix CR Approval Override**
+ Allows users to approve a Change Request regardless of the current policy.
+
+ - **Netwrix Restricted**
+ A restricted set of permissions required for users who will be making data updates to tracked or controlled objects.
+:::
\ No newline at end of file
diff --git a/docs/platgovsalesforce/installingstrongpoint/setting_up_initial_scan.md b/docs/platgovsalesforce/installingstrongpoint/setting_up_initial_scan.md
index 1695f1b753..34bad2e797 100644
--- a/docs/platgovsalesforce/installingstrongpoint/setting_up_initial_scan.md
+++ b/docs/platgovsalesforce/installingstrongpoint/setting_up_initial_scan.md
@@ -43,6 +43,12 @@ You can schedule the scanners to auto-scan your environment:
+:::warning Scanner Timing
+Please change the day or time of your Scanner run to prevent overlap which may cause failures and/or execution delays. **Times need to be set 2 hours apart at a minimum.**
+
+
+:::
+
:::note
Netwrix recommends you schedule at least the following items:
@@ -59,7 +65,7 @@ The final screen is displayed. Click **Done** to close the wizard.
-If you open the home page, you see the **Scanner Status** is **In Progress**.
+Open the Home page and verify that the **Scanner Status** shows **In Progress**.
diff --git a/docs/platgovsalesforce/installingstrongpoint/using_getting_started_wizard.md b/docs/platgovsalesforce/installingstrongpoint/using_getting_started_wizard.md
index 77e77dbd29..63de297042 100644
--- a/docs/platgovsalesforce/installingstrongpoint/using_getting_started_wizard.md
+++ b/docs/platgovsalesforce/installingstrongpoint/using_getting_started_wizard.md
@@ -7,20 +7,30 @@ sidebar_position: 20
# Run the Getting Started Wizard
The Getting Started Wizard helps you set up Platform Governance for Salesforce after you have done
-the [basic installation](/docs/platgovsalesforce/installingstrongpoint/installing_strongpoint.md) and configuration.
+the [basic installation](installing_strongpoint.md) and configuration.
+
+## Prerequisites
+
+Before running the Getting Started Wizard, ensure you have completed:
+
+- ✅ [Installed the Platform Governance package](installing_strongpoint.md)
+- ✅ [Assigned the Netwrix Grant Permissions permission set](installing_strongpoint.md#assign-permission-set-to-users) to users
+- ✅ Configured authentication using **one** of these methods:
+ - **Recommended:** [Named Credentials](named_credential.md) (for MFA-enabled orgs)
+ - **Legacy:** Session ID authentication (username/password/token)
+
+## Access the Wizard
To use the Getting Started Wizard:
-1. Open **Netwrix Dashboard**.
-2. Open **Settings**> **Getting Started Wizard**
+1. Open **Netwrix Dashboard** from the Salesforce App Launcher
+2. Navigate to **Settings** > **Getting Started Wizard**
The **Getting Started Wizard** opens to help you finish the configuration and set up.
## Choose Your License Type
-On the Initial Setup Wizard page, choose the package type you have purchased. If you have an
-Intelligent Change Management or Enterprise Compliance License, enter the **Input Authorization
-Token** sent to you. Click **Next**.
+On the Initial Setup Wizard page, choose the package type you have purchased and enter the **License Key** sent to you. Click **Next**.
@@ -28,36 +38,56 @@ Token** sent to you. Click **Next**.
Once you have chosen your license type, you need to add your credentials. If your credentials
change, an alert is sent to update the saved credentials. Expired credentials can cause auto
-scanners to fail. Use **Netwrix Dashboard** > **Settings**> **SP Credentials** to update your
+scanners to fail. Use **Netwrix Dashboard** > **Settings**> **SP Credentials** to update your
credentials.
+:::warning High Assurance Users
+If your organization has High Assurance enabled, you **cannot** use this credential method. You must use [Named Credentials](named_credential.md) instead.
+:::
+
+**For Session ID Authentication only:**
+
1. On the Credentials page, add the following values:
- **Salesforce Username**
- **Salesforce Password**
- **Salesforce Security Token**
- - **Salesforce Consumer Key** Extracted when you created the Strongpoint Connected App
- - **Salesforce Consumer Secret** Extracted when you created the Strongpoint Connected App
+ - **Salesforce Consumer Key** (optional)
+ - **Salesforce Consumer Secret** (optional)
2. Click **Next**
## Test Your Connection
-Once you have set up your credentials, you need to configure the remote site settings.
+This step applies to **both** Named Credentials and Session ID authentication methods. You need to configure the remote site settings to allow Platform Governance to communicate with external services.
-1. Open Salesforce **Setup** > **Security** > **Remote Site Settings**.
-2. Click **New Remote Site**.
+### Configure Remote Site Settings
+
+1. Open Salesforce **Setup** > **Security** > **Remote Site Settings**
+2. Click **New Remote Site**
-3. Copy/paste the information from the wizard to create the remote sites.
-4. Click on **Test Connection**. **Test connection was Successful** is displayed if the connection
- succeeds. If the connection fails, the wizard suggests troubleshooting steps to resolve the
- issue.
-5. Click **Next**.
+3. Copy/paste the information from the wizard to create the remote sites
+4. Repeat for each remote site URL shown in the wizard
+
+:::tip Multiple Remote Sites
+You may need to create multiple remote site settings. The wizard will display all required URLs. Create a separate remote site entry for each URL shown.
+:::
+
+### Test the Connection
+
+1. Return to the Getting Started Wizard
+2. Click **Test Connection**
+3. **Test connection was Successful** is displayed if the connection succeeds
+4. Once the test is successful, click **Next**
+
+## Next Steps
+
+After completing the Getting Started Wizard:
-**Next Step:** [Set Up the Initial Scan](/docs/platgovsalesforce/installingstrongpoint/setting_up_initial_scan.md)
+- [Set Up the Initial Scan](setting_up_initial_scan.md)
diff --git a/docs/platgovsalesforce/installingstrongpoint/validating_data.md b/docs/platgovsalesforce/installingstrongpoint/validating_data.md
index 3602e0701b..ed731354a1 100644
--- a/docs/platgovsalesforce/installingstrongpoint/validating_data.md
+++ b/docs/platgovsalesforce/installingstrongpoint/validating_data.md
@@ -31,17 +31,4 @@ To validate data with the DRD:
2. Select an **Object(s) Type** from the pull-down menu.
3. Click on a field and validate the data.
-
-
-## Customization Quick Search
-
-The Customization Quick Search opens a report with all customizations. From this report, you can add
-filters to find specific customizations that you need to validate the data.
-
-To validate data with the Customization Quick Search:
-
-1. Open **Netwrix Dashboard** > **Reports** > **Customizations** > **All Customizations**
-2. Scroll, **Search** or add **Filter(s)** to locate the customization.
-3. Click on the **Customization** and validate the data.
-
-
+
diff --git a/docs/platgovsalesforce/integrations/jiraintegration/jira_field_map.md b/docs/platgovsalesforce/integrations/jiraintegration/jira_field_map.md
index 28f8458b4f..8082a9d806 100644
--- a/docs/platgovsalesforce/integrations/jiraintegration/jira_field_map.md
+++ b/docs/platgovsalesforce/integrations/jiraintegration/jira_field_map.md
@@ -32,7 +32,7 @@ where you added the custom fields to get the field names. This example maps the
Version** and **Salesforce Version Number** fields, using the fields from the **Details** section in
Jira.
-
+
### Verify Field Creation
@@ -76,7 +76,7 @@ Add the fields to the Page Layouts.
In Jira, update the details for the fields. This example sets the **Strongpoint Version** field to
**2.2800** and the **Salesforce Version** to **6.1**.
-
+
### Access Mapping Configuration
diff --git a/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md b/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md
index b073f1a500..48e985d7d4 100644
--- a/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md
+++ b/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md
@@ -59,17 +59,17 @@ Cloud Integration Credentials after installing the app.
### Jira Cloud Installation
:::note
-You must be a Jira system administrator to install the **Strongpoint for Salesforce** app. Contact
+You must be a Jira system administrator to install the **Netwrix for Salesforce** app. Contact
your Jira system administrator if you do not have administrative permissions.
:::
1. Open your **Jira Software Dashboard**.
2. Select **Apps** > **Explore more Apps >**
-3. Search for **Strongpoint**.
+3. Search for **Netwrix**.
- 
+ 
-4. Click **Strongpoint for Salesforce** to install the app.
+4. Click **Netwrix for Salesforce** to install the app.
#### Access Data with API Integration
@@ -111,6 +111,37 @@ Configure the connected app:
If you do not use a connected app, you can set up Jira Cloud Integration Credentials as an
alternative.
+:::note
+You can use either Connected Apps or External Client Apps.
+The option you use depends on whether the app already exists or if you are creating a new version.
+:::
+
+Configure the External Client Apps (new version of connected apps):
+
+1. Log in to your Salesforce org.
+2. Open the Connected App:
+ **Setup** > **Apps** > **External Client Apps** > **Netwrix Pg Jira** (Netwrix Pg Jira is just an example; it doesn't need to have that exact name.)
+
+ 
+
+3. Click the drop down arrow on the right side and select **Edit Settings**.
+4. Set the **Callback URL** to **https://spjira.my.salesforce-sites.com/SpHandleJiraAuth** under the Oauth Settings Section
+5. These **Oauth Scopes** must be selected:
+ **Full access (full)**
+ **Perform requests at any time (refresh_token, offline_access)**
+6. Click **Save**.
+
+ :::note
+ Your connected app requires 2-10 minutes after you save before it is available.
+ :::
+
+7. Click **Consumer Key and Secret**.
+
+ 
+
+8. Copy the Consumer Key and the Consumer Secret codes to a clipboard. You are prompted for this
+ information when you use the app.
+
#### Set Up Jira Cloud Integration Credentials
1. From the Netwrix Dashboard: click **Configuration and Stats** in the **Resources** section, or
diff --git a/docs/platgovsalesforce/integrations/jiraintegration/jira_walkthrough_example.md b/docs/platgovsalesforce/integrations/jiraintegration/jira_walkthrough_example.md
index c674488662..f0819ce475 100644
--- a/docs/platgovsalesforce/integrations/jiraintegration/jira_walkthrough_example.md
+++ b/docs/platgovsalesforce/integrations/jiraintegration/jira_walkthrough_example.md
@@ -43,13 +43,13 @@ Alerts and notifications may occur during this walkthrough, and are not included
## Connect to the App
-1. Open the **Comments** tab and select **Strongpoint Salesforce**.
+1. Open the **Comments** tab and select **Netwrix Salesforce**.
- 
+ 
2. There are two ways to connect: **Login User** or **Connected App** tabs.
- 
+ 
### Connected App
@@ -58,7 +58,7 @@ Use the **Connected App** tab if you set up the connected app using the procedur
1. Open the **Connected App** tab.
- 
+ 
2. Enter the **Consumer Key** and **Consumer Secret**.
3. Click **Is Sandbox account?** if you are logging in to a sandbox.
@@ -84,7 +84,7 @@ Enter your Salesforce **Username**, **Password** and **Security Token**. If you
SSO: use your SSO Password. The Security token is the changing 6 digit code from your SSO or MFA
app.
-
+
If you do not have your security token, you can use these steps to reset your token:
@@ -108,7 +108,7 @@ consecutive attempts to login, your account is suspended for 30 minutes.
Once you have logged in, the form is displayed.
-
+
- **Synchronized with** displays the connected Org. Click **Change Account** if you need to switch
Orgs.
@@ -128,26 +128,18 @@ Once you have logged in, the form is displayed.
### Add Existing Customizations by Name or API Name
1. Enter all or part of a Name in **Add customization** for **Existing Customizations**. This
- example uses **maintenance** as the search string.
-2. Click **+** to search for matching Customizations. Hover over **View** to display the **Type**
- and **API Name** for a Customization.
+ example uses **add** as the search string.
+2. Click **Search** to search for matching Customizations.
- 
+ 
-3. Select one or more Customizations. This example uses **Maintenance Type (Parent: Account)**, a
- customization in the _Strongpoint Demo Org_.
+3. Select one or more Customizations (With Add or Remove buttons).
4. Click **Add Selected Customizations**. The selected Customization is added to the **Existing
Customizations** list.
- 
+ 
-5. Enter an **API Name** in **Add customization** for **Existing Customizations** and click **+**.
- This example uses **UpsellOpportunities**, an API in the _Strongpoint Demo Org_.
-6. The **API Name** is displayed. Select it, and click **Add Selected Customizations**. The selected
- Customization is added to the **Existing Customizations** list. This example shows
- **UpsellOpportunities (ApexClass)**, an API in the _Strongpoint Demo Org_.
- 
### Add Proposed Customizations
@@ -155,10 +147,10 @@ In this procedure, we are adding a new Customization.
1. Enter a new, valid API Name in the **Add Customization** for **Proposed Customizations** field.
For this example, enter **CustomerPriorities**.
-2. Click (**+**) to add it. If the API Name is valid, and does not match an existing API Name, the
+2. Click (**Add Proposed customizations**) to add it. If the API Name is valid, and does not match an existing API Name, the
new Customization is added to the **Proposed Customizations** list.
- 
+ 
### Create the Change Request
@@ -175,12 +167,12 @@ up the **[Jira Statuses](/docs/platgovsalesforce/integrations/jiraintegration/ji
3. Expand the **Change Request** field on the right. The status is now **None/In Progress**. There
is a link to open the Change Request in Salesforce.
- 
+ 
Note the **Policy** and **Change Level Req** reflect the most stringent requirement for your
-selected customizations, in this example, **Change Request**.
+selected customizations, in this example, **Marketing and Log Changes Only**.
-
+
## Perform Risk Assessment
@@ -210,18 +202,17 @@ Customizations and all dependencies.
Once you have resolved any risk or conflicts, your changes are ready for development:
-1. Change the Jira status of your ticket to match the status set up for **CR Pending Approval**. For
- example, **Selected for Development**.
+1. Change the Jira status of your ticket to match the status set up for **CR Pending Approval**.
2. Click **Push** if you are not using [Automatic Synchronization](/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md) to push
status changes.
3. Expand the **Change Request** field on the right. The status is now **Pending Approval / In
Progress**. There is a link to open the Change Request in Salesforce.
- 
+ 
4. Click the **Go To Record** link to view the Change Request.
- 
+ 
## Deploy Changes and Complete the Ticket
@@ -230,10 +221,9 @@ ticket is ready to be updated.
1. Expand the **Change Request** field on the right. The status is **Approved / In Progress**.
- 
+ 
-2. Change the Jira status of your ticket to match the status set up for **CR Approved**. For
- example, **Ready for Deployment**.
+2. Change the Jira status of your ticket to match the status set up for **CR Approved**.
3. Click **Push** if you are not using [Automatic Synchronization](/docs/platgovsalesforce/integrations/jiraintegration/jira_integration.md) to push
status changes.
4. Once your deployment and verification activities are complete, change the Jira status of your
diff --git a/docs/platgovsalesforce/integrations/jiraintegrationForge/_category_.json b/docs/platgovsalesforce/integrations/jiraintegrationForge/_category_.json
index 61e497d01d..192d07327f 100644
--- a/docs/platgovsalesforce/integrations/jiraintegrationForge/_category_.json
+++ b/docs/platgovsalesforce/integrations/jiraintegrationForge/_category_.json
@@ -6,6 +6,5 @@
"link": {
"type": "generated-index",
"description": "Jira Integration Forge"
-
}
}
\ No newline at end of file
diff --git a/docs/platgovsalesforce/navigate_strongpoint.md b/docs/platgovsalesforce/navigate_strongpoint.md
index ee7df0643f..84b5725859 100644
--- a/docs/platgovsalesforce/navigate_strongpoint.md
+++ b/docs/platgovsalesforce/navigate_strongpoint.md
@@ -6,56 +6,120 @@ sidebar_position: 7
# Launch Platform Governance for Salesforce
-To access Platform Governance for Salesforce:
+To access Platform Governance for Salesforce in Salesforce Lightning Experience:
-- Click the Apps Launcher in the upper left of Salesforce.
+1. Select the **App Launcher** (grid icon) in the upper-left corner of the Salesforce header.
-- Click **Netwrix Lightning**. You may have to click **View All** to see the choices.
+2. Search for and select **Netwrix Lightning**.
+ If you do not see the app, select **View All** to display all available apps.
+The Netwrix Lightning app opens.
+
+---
+
## Netwrix Dashboard
-When you open the **Netwrix Lightning** app in Salesforce, the default application tabs are loaded.
-Use + to add other tabs.
+When you open the **Netwrix Lightning** app, the default navigation items load in the navigation bar.
+
+To add additional items to the navigation bar, select **+ (Add More Items)**.
+
+The following navigation items are available:
-- **Netwrix Dashboard**: accesses the Platform Governance for Salesforce dashboard.
-- **Customizations**: opens the Customizations home page.
-- **Change Requests**: opens the Change Requests list.
-- **Change / Approval Policies**: opens the Policies list.
-- **Change Logs**: opens the Change Logs list.
-- **Reports**: opens the Reports list.
-- **Export Attachments**: opens the Export Attachments list.
+- **Netwrix Dashboard** – Opens the main Platform Governance dashboard.
+- **Customizations** – Opens the Customizations home page.
+- **Change Requests** – Opens the Change Requests list view.
+- **Change / Approval Policies** – Opens the Policies list view.
+- **Change Logs** – Opens the Change Logs list view.
+- **Reports** – Opens the Reports list view.
+- **Export Attachments** – Opens the Export Attachments list view.
-The **Netwrix Dashboard** displays menu tabs, status information, apps, and links.
+---
+
+## Netwrix Dashboard Overview
+
+The **Netwrix Dashboard** provides access to scanning status, tools, reports, and key account information.
-Menu tabs access functions through drop down menus:
+### Top Navigation Menu
+
+Use the dropdown menus at the top of the dashboard to access the main features:
+
+- **Settings** – Access Getting Started, system status, installation tools, credentials, and the Knowledge Center.
+- **Scanner** – Access the Scheduler, manual scanners, the field-level scanner, and the DLU Configuration scanner.
+- **Tools** – Access tools such as the dependency relationship diagram, environment comparison, profile comparison, and the access review assistant.
+- **Reports** – Access reports related to customizations, change enablement, cleanup, release and deployment, audit, and financial controls.
+
+---
+
+## Scanner Status
+
+The **Scanner Status** panel provides an overview of scanning activity in your Salesforce environment. It shows:
+
+- The current status of each scanner
+- The number of days since the system scanner was last run
+
+To run the system scanner immediately, select **Rescan Now**.
+
+**Important:**
+The **Rescan Now** option runs the main system scanner only. It does not include the following scanners:
+
+- **Permissions Assignment**
+- **System Permissions Scanner**
+- **Fast Scan Profile / PermissionSets**
+- **Non-Triggerable Data Scanner**
+
+To run any of these scanners, select **Start** next to the corresponding scanner in the list.
-- **Settings**: accesses getting started, status, installation tools, credentials, user guide and
- the support contact form.
-- **Scanner**: accesses the scheduler, manual scanners and the field level scanner.
-- **Tools**: accesses tools such as the dependency relationship diagram, environment comparison,
- profile comparison, and the access review assistant.
-- **Reports**: accesses lists and reports for all of the features such as customizations, change
- enablement, clean up, release and deployment, audit, and financial controls.
+You can also access and manage these scanners from **Scanner > Scheduler**.
-**Scanner Status** displays the **Scanner Status** and the number of days since the system scanner
-was run. There is a **Rescan Now** option.
+---
+
+## DRD Generator
+
+The **DRD Generator** displays a graphical view of a selected item and its relationships.
+
+To generate a diagram:
+
+1. Enter the **Name** or **API Name**.
+2. Select **Find**.
+
+---
+
+## Key Tools
+
+The **Key Tools** section provides quick access to frequently used tools, such as:
+
+- DRD
+- Fields
+- Export Objects
+- Permissions Comparison
-**DRD Generator** displays graphic display of an item. Enter a **Name** or **API Name** to search.
-Click **Find**.
+---
+
+## Netwrix Key Information
+
+The **Netwrix Key Information** panel displays a dynamic overview of your account, including general information, change management metrics, and access details.
+
+---
+
+## Contact Support
+
+To open the Netwrix support site, select **Contact Support**.
+
+---
-**Key Tools** and **Resources** have shortcut links to frequently used items.
+## Download Files
-**Netwrix Key Information** displays a dynamic overview of your account.
+The **Download Files** section displays files generated by Platform Governance for Salesforce and their current status.
-**Contact Support** launches the [support site](https://www.netwrix.com/support.html).
+To download a file:
-**Download Files** opens a list of files created by Platform Governance for Salesforce and the
-current status. Click on files to download them.
+1. Locate the file in the list.
+2. Select the file name.
diff --git a/docs/platgovsalesforce/release_7_0/index.md b/docs/platgovsalesforce/release_7_0/index.md
new file mode 100644
index 0000000000..00d6de1cc0
--- /dev/null
+++ b/docs/platgovsalesforce/release_7_0/index.md
@@ -0,0 +1,92 @@
+---
+title: "Release 7.0"
+description: "What's New in Release 7.0"
+sidebar_position: 2
+sidebar_label: "⭐ Release 7.0 (Latest)"
+---
+
+# Release 7.0
+
+Platform Governance for Salesforce Release 7.0 introduces powerful new capabilities for enhanced governance, monitoring, and change tracking across your Salesforce environment.
+
+## New Features
+
+### Document Report and Dashboard Folders
+
+Track and monitor access to Report and Dashboard folders with comprehensive change logging. This feature provides visibility into folder-level permissions and user access patterns, helping you maintain security and compliance for your reporting infrastructure.
+
+[Learn more →](/docs/platgovsalesforce/customizations/folder_customization_record)
+
+### DLU Scanner Improvements
+
+Enhanced Date Last Used (DLU) Scanner with improved configuration options and performance optimizations. The new DLU Configuration tool provides granular control over which metadata types and fields are processed, allowing you to focus on what matters most to your organization.
+
+[Learn more →](/docs/platgovsalesforce/tools/dlu_configuration)
+
+### Auto Scanner Inactivity Alert
+
+Proactive monitoring system that automatically sends email notifications to designated administrators when the Auto Scanner fails to run according to its configured schedule. This ensures your Salesforce environment remains continuously protected and documented.
+
+[Learn more →](/docs/platgovsalesforce/installingstrongpoint/config_and_stats#scanner-inactivity-alert)
+
+### Track Specific Permission Assignments
+
+Monitor and detect changes in System Permissions across Permission Sets and Profiles. Each scan compares selected permissions against previous snapshots and generates Change Logs for any detected differences, providing complete visibility into permission changes at the user level.
+
+[Learn more →](/docs/platgovsalesforce/tools/system_permission_tracking)
+
+### Track Access to Specific Fields
+
+New Field Tracking capability allows you to monitor changes to specific fields across your Salesforce org. Create custom monitoring rules based on objects, compliance categories, or data types, and receive notifications when tracked fields are modified.
+
+[Learn more →](/docs/platgovsalesforce/tools/field_tracking)
+
+### Change Request Re-architecture
+
+Redesigned Change Request system with improved performance, enhanced user interface, and better integration with deployment workflows. The new architecture provides faster processing and more intuitive change management capabilities.
+
+[Learn more →](/docs/platgovsalesforce/changemanagement/creating_change_request)
+
+### Customizations for Public Groups
+
+Enhanced support for Public Groups with improved documentation and change tracking. Monitor group membership changes, access permissions, and usage patterns to maintain security and compliance.
+
+[Learn more →](/docs/platgovsalesforce/customizations/understanding_customization_record)
+
+### Expanded Change Log List Views
+
+Change Log List Views have been expanded to support all new tracking capabilities, including System Permissions, Field Tracking, and Report/Dashboard Folder access. This provides a unified view of all changes across your Salesforce environment.
+
+### Note - Required Manual Configuration for Package Upgrades
+
+This package version introduces a new version of the Change / Approval Policy layout: **Strongpoint Change/Approval Policy Layout v11**.
+
+This new layout includes updates to the fields displayed for **Policy** records.
+
+For package upgrades, the new layout must be **manually assigned** after pushing the updates in order to take effect.
+
+**Steps to Assign the New Layout:**
+
+ 1. Go to **Setup**
+ 2. Open **Object Manager**
+ 3. Select **Change/Approval Policy**
+ 4. Go to **Page Layouts**
+ 5. Click **Page Layout Assignment**
+ 6. Click **Edit Assignment**
+ 7. Select the profile(s) that have access to the Policy record. In most cases, this will be the System Administrator profile. However, some customers may use a custom profile instead of the standard one.
+ 8. Change the current layout to **Strongpoint Change/Approval Policy Layout v11**
+ 9. Click **Save**
+
+For new installations, the latest layout will be assigned automatically by default.
+
+---
+
+## Getting Started
+
+To take advantage of these new features:
+
+1. Ensure your Platform Governance for Salesforce package is updated to Release 7.0
+2. Review the documentation for each feature to understand configuration requirements
+3. Configure the new scanners and monitoring tools based on your organization's needs
+
+For questions or assistance with Release 7.0 features, contact our Customer Success team.
\ No newline at end of file
diff --git a/docs/platgovsalesforce/releasemanagement/deployments.md b/docs/platgovsalesforce/releasemanagement/deployments.md
index 6b3e37ab60..cfe62c9c1f 100644
--- a/docs/platgovsalesforce/releasemanagement/deployments.md
+++ b/docs/platgovsalesforce/releasemanagement/deployments.md
@@ -18,10 +18,9 @@ entire deployment process is maintained.The process is:
## Create a Change Request
-1. Open **Change Requests** > **New Change Request**
-2. Enter a meaningful **Name** and **Change Overview**
-3. Modify the **Change Type** as needed. Add any other supporting information, change sets, package
- manifests, or customizations.
+1. Open **Change Requests** > **New**
+2. Enter a meaningful **Change Request Name**, select the **Change Request Type** (Between Record Type and customization) and **Change Overview**
+3. Modify the **Change Type** as needed. Add any other supporting information, such as Parent Change Request, customizations or data records.
4. **Save** the change request.
5. Click **Submit for Approval**
@@ -63,7 +62,6 @@ These steps can be completed after the deployment record is approved.
This creates a package to:
- - **Check Dependencies**: Use to check what has been referenced.
- **Validate Customizations**: Use to check the deployment is going to work. It simulates your
deployment.
- **Deploy Retrieved Customizations**: Use to deploy your customizations when you are ready to
diff --git a/docs/platgovsalesforce/releasemanagement/multiple_environments.md b/docs/platgovsalesforce/releasemanagement/multiple_environments.md
index e9c6511e8e..8d7d14ff51 100644
--- a/docs/platgovsalesforce/releasemanagement/multiple_environments.md
+++ b/docs/platgovsalesforce/releasemanagement/multiple_environments.md
@@ -23,9 +23,6 @@ Salesforce is installed, and to deploy changes and promote code from one environ
2. Edit the change request and add all necessary details.
-
- 
-
3. Click on **Sync CR**.
diff --git a/docs/platgovsalesforce/releasemanagement/rollback.md b/docs/platgovsalesforce/releasemanagement/rollback.md
index 53571f0bc5..0c94497c0b 100644
--- a/docs/platgovsalesforce/releasemanagement/rollback.md
+++ b/docs/platgovsalesforce/releasemanagement/rollback.md
@@ -29,8 +29,7 @@ The Deployment Record status must be **Completed** to be eligible for Rollback.
-4. By default, all of the customizations are selected for rollback. Deselect any customizations to
- keep. The **Rollback Type** specifies the effect of the rollback:
+4. By default, all of the customizations are selected for rollback. Deselect any customizations to keep. The **Rollback Type** specifies the effect of the rollback:
- **Delete**: If a customization was created during the deployment, it is deleted during the
rollback.
diff --git a/docs/platgovsalesforce/scanner/FastScan.md b/docs/platgovsalesforce/scanner/FastScan.md
new file mode 100644
index 0000000000..7707c5f041
--- /dev/null
+++ b/docs/platgovsalesforce/scanner/FastScan.md
@@ -0,0 +1,131 @@
+# FastScan Feature
+
+## Overview
+
+The FastScan feature is an automated scanning feature that monitors and tracks changes to **Profiles**, **Permission Sets**, and **Permission Set Groups** in your Salesforce org. Unlike the standard scanner that performs full metadata retrieval, the FastScan feature uses the **SetupAuditTrail** to detect changes incrementally, providing faster and more efficient change tracking for security-related metadata.
+
+## What FastScan Does
+
+The FastScan monitors your org for changes to security permissions by:
+
+- Querying the **SetupAuditTrail** object for permission-related changes
+- Identifying modified Profiles, Permission Sets, and Permission Set Groups
+- Creating Change Log records to document what changed and when
+- Triggering targeted rescans only for the modified customizations
+- Running on a scheduled basis to keep your documentation up to date
+
+This approach significantly reduces processing time compared to full metadata scans while ensuring you capture all security changes in near real-time.
+
+### Special Profile Settings Detection
+
+The FastScan is the **only method** that detects and documents changes to:
+
+- **ProfilePasswordPolicy**: Password policies and requirements configured at the Profile level
+- **ProfileSessionSetting**: Session timeout and security settings for Profiles
+
+When changes are made to these settings, it automatically creates Change Log records at the Profile level, ensuring complete visibility of security configuration changes that are not captured by the standard scanner.
+
+---
+
+## Key Benefits
+
+- **Faster Processing**: Scans only changed items instead of all metadata
+- **Incremental Updates**: Tracks changes since the last scan run
+- **Automated Monitoring**: Runs on a schedule you define
+- **Focused on Security**: Specifically monitors Profiles, Permission Sets, and Permission Set Groups
+- **Exclusive Detection**: Only the FastScan detects ProfilePasswordPolicy and ProfileSessionSetting changes, registering them at the Profile level
+
+---
+
+## How The FastScan feature Works
+
+### 1. Scheduled Execution
+
+The FastScan runs automatically based on the schedule you configure in the **Scheduling** section of the Platform Governance Scheduler. You can set it to run daily, weekly, or at custom intervals to continuously monitor permission changes in your org.
+
+### 2. Change Detection
+
+The FastScan monitors changes by:
+
+1. Checking the SetupAuditTrail for permission-related modifications since the last scan (up to 8 days back)
+2. Identifying which Profiles, Permission Sets, or Permission Set Groups were modified
+3. Creating Change Log records to document the changes
+
+### 3. Change Log Creation
+
+1. **Consolidates Changes**: Groups multiple changes to the same customization on the same day
+2. **Creates Change Logs**: Generates Change Log records with detailed change information
+3. **Updates Timestamps**: Records when changes were detected
+4. **Triggers Rescan**: Initiates a targeted rescan of modified customizations
+
+### 4. Targeted Rescan
+
+After Change Logs are created, the FastScan triggers a rescan process that:
+
+1. Retrieves fresh metadata only for the modified Profiles/Permission Sets/Permission Set Groups
+2. Updates the Customization records with current values
+3. Creates detailed Change Logs showing what specifically changed
+4. Updates junctions and dependencies
+
+---
+
+### Scheduling the FastScan feature
+
+You can schedule the FastScan to run automatically:
+
+1. Go to the **Netwrix Dashboard** page
+2. Navigate to the **Scanner** > **Scheduler** menu
+3. Locate the **FastScan Profile/Permission Set** scheduler
+4. Select your desired frequency (e.g., Daily, Weekly)
+5. Choose the time of day to run
+6. Click **Enable** to activate
+
+For more information about the scheduler, see the [Scheduler documentation](/docs/platgovsalesforce/scanner/scheduler.md).
+
+**Best Practice**: Schedule the FastScan to run daily during off-peak hours to ensure timely change detection without impacting users.
+
+### Manual Execution
+
+To run the FastScan feature manually:
+
+1. Navigate to the **Netwrix Dashboard** page
+2. Locate the **Fast Scan Profile / PermissionSets** section
+3. Click **Start**
+4. Monitor the progress in the **Running Jobs** section
+
+---
+
+## Understanding the FastScan Results
+
+### Change Log Records
+
+The FastScan creates Change Log records with the following information:
+
+- **Customization**: The Profile, Permission Set, or Permission Set Group that changed
+- **Change Overview**: Description of what changed
+- **Actual Change DateTime**: When the change occurred in Salesforce
+- **Modified By**: User who made the change
+- **Field Name**: Specific field or permission that changed
+
+---
+
+### Troubleshooting
+
+Not change logs detected by the FastScan:
+
+1. **Verify Schedule**: Confirm the FastScan scheduler is active in Setup → Scheduled Jobs
+2. **Review Apex Jobs**: Look for failed batch jobs in Setup → Apex Jobs
+3. **Check Permissions**: Verify the running user has access to SetupAuditTrail and related objects
+4. **Review Time Range**: The FastScan looks back maximum 8 days; older changes won't be detected
+
+---
+
+## Best Practices
+
+1. **Schedule Regularly**: Run the FastScan daily to ensure timely change detection
+2. **Monitor Results**: Review Change Logs regularly to stay informed of security changes
+3. **Off-Peak Execution**: Schedule during low-usage hours to minimize impact
+4. **Review Failed Jobs**: Check Apex Jobs regularly for any processing errors
+5. **Maintain Custom Setting**: Keep **Fast_Scan_Params__c** properly configured
+
+---
\ No newline at end of file
diff --git a/docs/platgovsalesforce/scanner/field_level_scanner.md b/docs/platgovsalesforce/scanner/field_level_scanner.md
index ce7e878010..d558f4f7bb 100644
--- a/docs/platgovsalesforce/scanner/field_level_scanner.md
+++ b/docs/platgovsalesforce/scanner/field_level_scanner.md
@@ -6,6 +6,29 @@ sidebar_position: 40
# Field Level Security Scanner
+## Overview
+
+The Field Level Security scanner allows users to analyze access to selected fields across multiple Salesforce objects that may be critical to the organization. It evaluates and records which Profiles, Permission Sets, and Permission Set Groups have read access, write access, or both, for the specified fields.
+
+This scanner captures an exact snapshot of the system at the moment it is executed.
+
+It allows users to review the results in the **Field Permissions** report.
+
+
+## Accessing Field Level Security
+
+Navigate to the Netwrix Dashboard:
+
+**Scanner** > **Field-Level Security Scanner**
+
+
+## Field Level Security Scanner UI
+
+From this screen, users can search for and select multiple fields from different objects. The selected fields will be displayed in the table at the bottom of the screen.
+Currently, the maximum number of fields that can be selected is 50.
+
+
+
The Field Level Security Scanner creates a comprehensive list of Customizations, Field API Name,
Parent Object, Package, and Salesforce Type for a selected Object.
@@ -13,30 +36,46 @@ Parent Object, Package, and Salesforce Type for a selected Object.
Run the scanners before you search to ensure you have the latest data.
:::
-1. Open **Netwrix Dashboard** > **Scanner** > Field-Level Security Scanner.
-
- 
+Below is a step-by-step example of how to run the scanner:
-2. Start typing the name of a **Salesforce Object**. Pick from the completion list.
-3. Click **Search Fields**.
+1. Start typing the name of a **Salesforce Object**, then select it from the autocomplete list.
+2. Click **Search Fields**.
-4. Select one or more fields to scan. The **Customization Name** is a link to the Customization
- Record.
+3. Select one or more fields from different objects to be analyzed by the scanner. The **Customization Name** is a link to the Customization Record.
- :::note
- It is not technically possible to scan permissions on all fields in each object.
- :::
+:::note
+ It is not technically possible to scan permissions on all fields in each object.
+:::
+
+4. Selected fields are shown in a list at the bottom of the form. You can uncheck individual fields
+ or all fields from the **Selected Fields** list.
+
+
+
+5. Click **Run Scanner**.
+
+Once the scan is complete, open the Reports tab and select **Field Permissions** Report.
-5. Selected fields are shown in a list at the bottom of the form. You can uncheck individual fields
- or all fields from the **Selected Field** list.
+:::note
+Once the scanner is executed, the functionality will be locked until the process is complete.
- 
+If you need to run it again, keep in mind that the results represent a snapshot at the time of execution. Previous executions are not stored, and no historical data is maintained.
+:::
-6. Click **Run Scanner**.
+## Field Level Security Report
-Once the scan is complete, open the Reports tab and select Field Permissions Report. The report is
-also available from the Netwrix Dashboard: **Reports** > **Access Reports** > **Field Permissions**.
+The report is available from the Netwrix Dashboard: **Reports** > **Access Reports** > **Field Permissions**.
+
+## Best Practices
+
+- Make sure the customization record for the field you want to analyze has been created before running the scanner.
+- Carefully select the fields to be analyzed.
+
+## Limitations
+
+- Execution history is not stored.
+- The maximum number of fields that can be selected across multiple objects is 50.
diff --git a/docs/platgovsalesforce/scanner/running_scanner.md b/docs/platgovsalesforce/scanner/running_scanner.md
index 71a953d59c..0288971e8a 100644
--- a/docs/platgovsalesforce/scanner/running_scanner.md
+++ b/docs/platgovsalesforce/scanner/running_scanner.md
@@ -4,6 +4,46 @@ description: "Manual Scanners"
sidebar_position: 20
---
-import ManualScanners from '/docs/platgovsalesforce/installingstrongpoint/running_scanner.md';
+# Manual Scanners
-
\ No newline at end of file
+When the initial scan is complete, you can run additional on demand scans as required.
+
+When you add or change a specific customization, you can choose to run an on demand scan of only the
+Metadata type of the affected customization, instead of scanning the entire environment. This type
+of scan reduces the run time. For example if you change a Report, pick reports as the Metadata type
+and Platform Governance for Salesforce only scans reports.
+
+:::note
+The scanner is only available to Administrators.
+:::
+
+To run the scanner:
+
+1. Open **Netwrix Dashboard** > **Scanner** > **Manual Scanners**
+2. Use the optional **Search Types** to narrow the focus of the list if you are looking for a
+ specific type.
+3. You can select + beside one or more types to scan or you can scan the whole environment by
+ clicking + on the **Name** row to select all the types.
+
+ 
+
+4. Click **Run Scanner**.
+5. The batch runs in the background. You receive an email notification when the scan is complete.
+
+6. From the Netwrix Dashboard: click **Configuration and Stats** in the **Resources** section, or
+ open **Settings** > **Configuration and Stats**.
+
+You can create your own Salesforce view for the scanners:
+
+ 1. Open Salesforce **Setup**.
+ 2. Search for **apex jobs** or navigate to **Environments** > **Jobs** > **Apex Jobs**.
+ 3. Click **Create New View**.
+ 
+ 4. Enter a **View Name**. The system assigns **View Unique Name**. _Netwrix Jobs1_ is used in this example.
+ 5. Select **Apex Class** for the **Field**.
+ 6. Select **starts with** for the **Operator**.
+ 7. Assign **FLO, Strongpoint, NetPG** for the **Value**.
+ 8. Click **Save**. You can now see the status of all of the Strongpoint jobs.
+ 
+
+**Next Step:** [Validate the Data ](/docs/platgovsalesforce/installingstrongpoint/validating_data.md)
\ No newline at end of file
diff --git a/docs/platgovsalesforce/scanner/scanner_troubleshooting_guide.md b/docs/platgovsalesforce/scanner/scanner_troubleshooting_guide.md
new file mode 100644
index 0000000000..0708416009
--- /dev/null
+++ b/docs/platgovsalesforce/scanner/scanner_troubleshooting_guide.md
@@ -0,0 +1,129 @@
+# Scanner Troubleshooting Guide
+
+## Overview
+This guide helps you troubleshoot the Strongpoint scanner system in your Salesforce org. You'll find verification methods, scanner limits, duration estimates, and best practices for running initial scans—especially useful for large organizations.
+
+---
+
+## Table of Contents
+1. [Understanding Scanner Performance](#1-understanding-scanner-performance)
+2. [Scanner Status](#2-scanner-status)
+3. [Initial Scan Recommendations](#3-initial-scan-recommendations)
+
+---
+
+## 1. Understanding Scanner Performance
+
+### 1.1 Estimating Scan Duration
+
+Understanding how long a scan will take helps you plan accordingly:
+
+| Org Size | Metadata Count | Estimated Duration | Characteristics |
+|----------|----------------|-------------------|-----------------|
+| **Small** | < 20,000 | 1 - 3 days | Standard objects, minimal customization |
+| **Medium** | 20,000 - 70,000 | 4 - 6 days | Multiple custom objects, moderate automation |
+| **Large** | 70,000 - 100,000 | 7 - 10 days | Extensive customization, complex integrations |
+
+**Factors Affecting Duration:**
+
+*Accelerating Factors:*
+- Fewer dependencies between components
+- Standard objects vs. custom objects
+- Inactive metadata excluded
+
+*Slowing Factors:*
+- Complex Flow conditions requiring separate processing
+- Deep folder hierarchies (Reports/Dashboards)
+- Large number of picklist values
+- API rate limiting during peak hours
+
+### 1.2 Scanner Limits
+
+**Salesforce Governor Limits:**
+
+The scanner operates within standard Salesforce governor limits:
+
+| Limit Type | Value | Impact |
+|------------|-------|--------|
+| **Concurrent Batch Jobs** | 5 | Maximum parallel scanners |
+| **Batch Size** | 1-2000 records | Configurable per scanner |
+| **Heap Size** | 12 MB (sync) / 12 MB (async) | Memory constraint |
+| **CPU Time** | 10,000 ms (sync) / 60,000 ms (async) | Processing time limit |
+| **SOQL Queries** | 100 (sync) / 200 (async) | Query limit per transaction |
+| **DML Statements** | 150 | Insert/Update operations |
+| **Callouts** | 100 | API calls per transaction |
+| **Batch Job Timeout** | 24 hours | Maximum execution time |
+
+**Scanner-Specific Limits:**
+
+Due to Salesforce governor limit constraints, the scanner processes metadata in batches with configurable size limits. Each batch run has a processing limit that typically ranges between 1,000 and 7,000 records per batch, depending on the metadata type and complexity. These limits ensure the scanner operates within Salesforce API call limits and governor thresholds while optimizing performance.
+
+### 1.3 Verifying Complete Metadata Documentation
+
+To confirm that all metadata has been successfully documented, verify the scanner completion status in the [Scanner Status](/docs/platgovsalesforce/installingstrongpoint/config_and_stats.md#scanner-status) section of **Configuration and Stats**:
+
+1. Navigate to **Netwrix Dashboard** > **Settings** > **Configuration and Stats**
+2. Open the **Scanner Status** tab
+3. Review the **Scanner Logs** section
+
+For each Salesforce Type listed, verify the following:
+
+- **Retrieved Stage**: Must show **Verified** for all metadata types
+- **Total Customization**: Must match the **Scanner Count** value exactly
+
+When the **Retrieved Stage** shows **Verified** and both count values match, it confirms that the scanner has successfully processed all metadata for that type. If any type shows a different status or mismatched counts, the scan is still in progress.
+
+---
+
+## 2. Scanner Status
+
+You can monitor the scanner execution status in real-time through the Strongpoint UI. For detailed instructions on how to view scanner progress, check the status of running batches, and interpret the Scanner Status page, see the [Scanner Status documentation](../navigate_strongpoint#scanner-status).
+
+You can also create your own Salesforce view to monitor scanner jobs directly in Salesforce. For step-by-step instructions on creating a custom view for the scanners, see the [Running Scanner documentation](/docs/platgovsalesforce/installingstrongpoint/running_scanner.md#creating-a-custom-view-for-scanners).
+
+## 3. Initial Scan Recommendations
+
+### 3.1 Running the Full Scan
+
+Before setting up incremental or scheduled scans, you must complete an initial full scan of your Salesforce org. This full scan documents all existing metadata and establishes the baseline for future change detection.
+
+**To configure and run the full scan:**
+
+1. Navigate to the Strongpoint Scanner configuration
+2. Configure the automated scan settings following the [Scanner Scheduler documentation](./scheduler)
+3. Start the full scan and monitor its progress using the [Scanner Status page](../navigate_strongpoint#scanner-status)
+
+**Important:** Wait for the full scan to complete before configuring incremental scans. You can verify completion by checking the information in [section 1.3](#13-verifying-complete-metadata-documentation).
+
+### 3.2 Configuring Metadata Types to Document
+
+You can configure which Salesforce metadata types you want to document based on your organization's needs. This allows you to focus on the most relevant components and optimize scan performance.
+
+**To select specific metadata types:**
+
+Follow the instructions in the [Daily Scan Configuration documentation](./daily_scan) to:
+- Choose which metadata types to include in your scans
+- Configure scan frequency for different metadata types
+- Optimize scan performance based on your org size
+
+**Common Configuration Scenarios:**
+
+- **Development-focused orgs**: Prioritize Apex Classes, Triggers, Flows, and Custom Fields
+- **Admin-focused orgs**: Focus on Profiles, Permission Sets, Validation Rules, and Workflows
+- **Report-heavy orgs**: Include Reports, Dashboards, and List Views
+- **Compliance-focused orgs**: Document all metadata types for complete audit trails
+
+### 3.3 Best Practices
+
+**Timing Recommendations:**
+- ✅ **DO**: Run initial scan during off-peak hours (evenings/weekends)
+- ✅ **DO**: Schedule during maintenance windows if possible
+- ❌ **DON'T**: Run during business-critical periods
+- ❌ **DON'T**: Run concurrent with data loads or deployments
+- ❌ **DON'T**: Interrupt scan mid-process
+
+**Resource Management:**
+- Keep other batch jobs to minimum during scan
+- Avoid scheduled Apex jobs during scan window
+- Monitor API usage to stay within limits
+- Review heap size warnings and adjust if needed
\ No newline at end of file
diff --git a/docs/platgovsalesforce/scanner/scheduler.md b/docs/platgovsalesforce/scanner/scheduler.md
index e9c12703ff..470a8dc578 100644
--- a/docs/platgovsalesforce/scanner/scheduler.md
+++ b/docs/platgovsalesforce/scanner/scheduler.md
@@ -19,6 +19,50 @@ To use the scheduler tool:
2. Select the category to automate by clicking on **Disabled** to enable it. There is no save
- button, automation is turned on and saved by toggling **Disabled**/**Enabled**.
+ button, automation is turned on and saved by toggling **Enabled**/**Disabled**.
3. Select the **Frequency** , **Day** and **Time**. Your selections are automatically saved.
4. Click any menu item to close the **Scheduler**.
+
+---
+
+## Best Practices
+
+### Initial Documentation Phase
+
+When you first install Platform Governance for Salesforce, enable only the **Automated Scan** with **Daily** frequency. Do not enable other scanners until your org is fully documented. This approach ensures:
+
+- Complete baseline documentation before change detection begins
+- Optimal resource utilization during initial scan
+- Accurate change logs once incremental scanning starts
+
+### Profile and Permission Set Heavy Orgs
+
+If your org contains many profiles and permission sets, you can enable the **Fast Scan** for more agile change detection and change log generation. The Fast Scan provides quicker turnaround than the Daily Scan while maintaining accuracy for permission-related changes.
+
+### Scanner Selection
+
+Enable only the scanners necessary for your organization's requirements. Consider:
+
+- Your compliance and audit needs
+- The metadata types your team actively modifies
+- Your organization's change management processes
+
+Avoid enabling all scanners by default, as this can consume unnecessary resources and processing time.
+
+### Scheduling Strategy
+
+Configure logical time windows between scanners to prevent batch execution conflicts. Stagger your scanner schedules to ensure:
+
+- Scanners do not run concurrently
+- Each scanner completes before the next one starts
+- System resources remain available for other Salesforce operations
+
+### Field Usage & DLU Scanner
+
+For the **Field Usage & DLU** scanner, schedule weekly execution during weekends. This recommendation helps:
+
+- Minimize resource consumption during business hours
+- Avoid impact on user activities
+- Ensure thorough field usage analysis without time pressure
+
+Configure this scanner to run on Saturday or Sunday when system usage is typically lower.
diff --git a/docs/platgovsalesforce/settings/credentials.md b/docs/platgovsalesforce/settings/credentials.md
index 15c0bcd3c6..8f7ad87a7e 100644
--- a/docs/platgovsalesforce/settings/credentials.md
+++ b/docs/platgovsalesforce/settings/credentials.md
@@ -7,7 +7,7 @@ sidebar_position: 40
# Credentials
Credentials organizes your user credentials across all environments It is available from **Netwrix
-Dashboard** > **Settings** > **SP Credentials**
+Dashboard** > **Settings** > **App Credentials/Test Connection**
diff --git a/docs/platgovsalesforce/techdebt/tech_debt_auto_documentation.md b/docs/platgovsalesforce/techdebt/tech_debt_auto_documentation.md
index b09d516a6d..0928e48088 100644
--- a/docs/platgovsalesforce/techdebt/tech_debt_auto_documentation.md
+++ b/docs/platgovsalesforce/techdebt/tech_debt_auto_documentation.md
@@ -48,8 +48,8 @@ the dependencies.
-3. The DRD exposes other critical metadata such as the Owner, API Name, Data Type, and Date Last
- Used (DLU). This data expedites clean up, enabling you to filter and group Customizations in List
+3. The DRD exposes other critical metadata such as the Owner, API Name, Data Type, Date Last
+ Used (DLU), Compliance Group and Security Classification. This data expedites clean up, enabling you to filter and group Customizations in List
Views or Reports.
@@ -65,56 +65,204 @@ Click **Show/Hide Standard Fields** to toggle displaying Standard Fields in the
## Customization Record
-The Customization record is the heart of Platform Governance for Salesforce’s automated
-documentation — all of the gathered metadata is organized into an easy to understand format. Each
-Customization record includes the information you expect from excellent documentation:
-
-- What the customization is
-- What it is part of
-- What it depends upon
-- What depends on it
-- When it was last used
-- Who owns it
-- Who created it
-- Other metadata to help change agents understand it, such as formulas, filters and API calls if
- relevant
-
-If you have Intelligent Change Enablement, you also see:
-
-- Change history
-
-The tabs on each Customization record break out the information you need to fully understand the
-basic metadata, dependencies by type and change history (requires _Intelligent Change Enablement_ or
-_Enterprise Compliance_ [license](/docs/platgovsalesforce/installingstrongpoint/features_by_license_type.md)). Click
-**Go To Record** to open the actual Salesforce record for users with proper access. Customization
-records can be edited to assist in organizing records for clean up and optimization.
-
-Here are five methods to access Customizations to explore:
-
-- Open the DRD to get the object overview or investigate the fields on an object.
-- Enter a Customization name in the main **Search Salesforce** bar. All Customization records are
- searchable and include the **DRD** tab.
-- **Customizations** tab: Navigate like any other record to see different views, such as recently
- changed Customizations.
-- **Finder** is another powerful tool for searching and visualizing relationships between
- Customizations.
-- Create your own Dashboards, Reports and List Views to get exactly what you want. Platform
- Governance for Salesforce is a native Salesforce app, so you can use all your skills to create
- exactly what you need.
+The Customization record is the central element of Platform Governance for Salesforce documentation. It consolidates technical, operational, and governance-related metadata into a single, structured view that helps administrators, architects, and change agents fully understand a customization, its context, and its impact.
+
+Each Customization record is organized into sections and tabs, allowing users to easily navigate between metadata, dependencies, change controls, and historical activity.
+
+- **Main Customization Record Sections**
+
+1. Header and Overview
+
+At the top of the Customization record, you can see key identifying information:
+
+- Customization Name
+- Owner
+- Salesforce Type (for example, CustomField)
+- API Name
+- Description (if provided)
+
+The header also provides quick access to actions such as Rescan and Go To Record, allowing authorized users to open the underlying Salesforce record directly.
+
+
+
+2. Related Objects Panel
+
+This panel summarizes the main dependency categories for the customization and provides quick navigation to them:
+
+- Data-Model – Objects, fields, and data structures related to the customization
+- Display-UI – Layouts and UI elements where the customization is exposed
+
+Each category shows a count, indicating how many related items are associated.
+
+
+
+- **Customization Tabs**
+
+1. Metadata Tab
+
+The Metadata tab provides the foundational details of the customization, including:
+
+- Customization name and Salesforce type
+- Active status and manageability state
+- Data type and package information
+- Created by / Last modified by
+- Creation and last modification dates
+- Whether a value is required (for applicable types)
+
+This tab answers the question: "What is this customization?"
+
+
+
+2. Custom Tab
+
+The Custom tab displays usage and lifecycle-related data gathered through scanning, such as:
+
+- Last scan date
+- First detected (join) date
+- Last used date (when available)
+- Percentage populated (for data fields)
+- DLU (Data Lifecycle Usage) status
+- Parent last update date
+- Track History Field enablement status
+
+This information helps assess data relevance, usage, and technical debt.
+
+
+
+3. DRD Tab
+
+The DRD tab provides a visual representation of how the customization relates to other components in Salesforce.
+It shows dependencies grouped by category, such as:
+
+- Data-Model – Objects and fields using or referenced by the customization
+- Display-UI – Layouts and UI elements where it appears
+
+This tab answers: "What does this customization depend on, and what depends on it?"
+
+
+
+4. Change Enablement Tab
+
+The Change Enablement tab displays governance and control-related configuration, including:
+
+- Associated Change / Approval Policy
+- Whether the customization is added to a Change Request
+- Data Tracking settings (when enabled)
+
+This tab is available when Intelligent Change Enablement or Enterprise Compliance is licensed and helps control how changes to this customization are governed.
+
+
+
+5. Clean-Up Tab
+
+The Clean-Up tab supports technical debt management by allowing classification and status tracking:
+
+- Clean-up status
+- Clean-up classification
+
+This tab helps teams identify candidates for remediation, optimization, or removal.
+
+
+
+6. Related Tab
+
+The Related tab provides historical and operational context, including:
+
+- Change Logs: A list of all detected changes related to the customization.
+- Notes & Attachments: Any supporting files or documentation associated with the customization.
+- Customization History: A record of lifecycle events over time.
+
+
+
+### Additional Customization Record Actions
+
+Two key actions are available in the Customization Record:
+
+1. **ReScan Button**:
+ - Click the "ReScan" button to manually trigger a new scan of the customization.
+ - This helps detect any recent changes that might not have been captured in the previous scan.
+ - Useful for ensuring you have the most up-to-date information about the customization.
+
+2. **Go To Record Button**:
+ - Click the "Go To Record" button to directly navigate to the original Salesforce record for this customization.
+ - Provides immediate access to the full Salesforce configuration of the component.
+ - Requires appropriate user permissions in Salesforce.
+
+
## Finder
-[Finder](/docs/platgovsalesforce/tools/finder.md) is another flexible tool for understanding dependencies across objects.
-You can search for Customizations by:
+The Customization Finder is a powerful search and filtering tool that helps you locate and analyze Customization records across your Salesforce instance. It enables users to quickly find specific customizations, understand ownership and usage, and export results for further analysis.
+
+Finder is especially useful for audits, clean-up initiatives, impact analysis, and documentation reviews.
+
+### Finder Filters
+
+The upper section of the Finder page provides a comprehensive set of filters to refine search results.
+
+#### Text and API Name Search
+
+**Search by text / API Name**
+Allows free-text searching across customization names and API names.
+
+#### Date Filters
+
+**Created After**
+Filters Customizations created after a specific date.
+
+**Modified After**
+Filters Customizations modified after a specific date.
+
+#### Package Filtering
+
+**Include components from packages**
+When enabled, Finder includes managed package components in the results. When disabled, only custom (non-package) components are returned.
+
+#### Customization Type Filtering
+
+This section allows you to narrow results by customization type.
+
+**Search Types**
+Quickly filter the list of available customization types.
+
+**Select Types**
+Choose one or more customization types (for example, Apex Classes, Apex Pages, Custom Fields, Reports, etc.) to include in the search.
+
+Only selected types are included in the results.
+
+#### Created By Filtering
+
+This section allows filtering Customizations based on the user who created them.
+
+**Search Users**
+Quickly locate users by name.
+
+**Select Users to filter**
+Choose one or more Salesforce users to include as creators in the results.
+
+#### Search Actions
+
+At the bottom of the filter section, Finder provides the following actions:
+
+- **Search** – Executes the search using the selected filters
+- **Export to PDF** – Exports the current result set to a PDF file
+- **Export to XLS** – Exports the current result set to an Excel file
+
+### Search Results
+
+Search results are displayed in a tabular format and include key information for each Customization, such as:
+
+- Name
+- Type
+- API Name
+- Direct / Dependency – Indicates whether the customization is directly selected or included as a dependency
+- Last Modified Date / DLU
+- Created By
+- Modified By
-- Text / API Name
-- Creation Date
-- Date Last Used (DLU)
-- Creator / Owner
-- Customization Type
+Pagination controls and page size options allow you to navigate large result sets efficiently.
-You can **Include** or **Exclude** Package Customizations to filter your lists. Results can be
-exported in PDF or Excel formats.
+
## Object Exporter
diff --git a/docs/platgovsalesforce/techdebt/tech_debt_change_monitoring.md b/docs/platgovsalesforce/techdebt/tech_debt_change_monitoring.md
index f5fb8d56eb..a511c3bb6b 100644
--- a/docs/platgovsalesforce/techdebt/tech_debt_change_monitoring.md
+++ b/docs/platgovsalesforce/techdebt/tech_debt_change_monitoring.md
@@ -27,10 +27,9 @@ escalating levels of rigor and/or skill required to address a change:
| Change Level | Change Process | Example | Skill Level Required |
| --------------------------------------- | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| L1: Log Changes | This is a safe change. | Ordinary report. | Anyone. |
-| L2: Process Issue | This is a relatively safe change but should be reviewed afterward. | Public report. | Anyone. |
-| L3: Change Request | This needs approval from management but not sandbox review. | Management report or Control. | Anyone, provided prior approval is granted. |
-| L4: Sandbox Development and Testing | This is not a complex change, but best practices require it to be tested in a sandbox first. | Data model changes with no dependencies. For example, adding a new field. | Business Analyst or Admin with prior approval, working in sandbox before deploying in production. |
-| L5: Full Software Development Lifecycle | This is not a safe change. It needs to be changed carefully with rigorous testing. | Changes to code or a picklist used in field with code or SoQL dependencies. | Admin / Developer with prior approval working through a full development cycle in multiple sandboxes. |
+| L2: Change Request | This needs approval from management but not sandbox review. | Management report or Control. | Anyone, provided prior approval is granted. |
+| L3: Sandbox Development and Testing | This is not a complex change, but best practices require it to be tested in a sandbox first. | Data model changes with no dependencies. For example, adding a new field. | Business Analyst or Admin with prior approval, working in sandbox before deploying in production. |
+| L4: Full Software Development Lifecycle | This is not a safe change. It needs to be changed carefully with rigorous testing. | Changes to code or a picklist used in field with code or SoQL dependencies. | Admin / Developer with prior approval working through a full development cycle in multiple sandboxes. |
Changes made without the policy-required approval are reported as Non-Compliant. Review the
Non-Compliant Changes Report to ensure dangerous changes do not slip through and cause process or
@@ -43,7 +42,10 @@ Policies can also be used to block unauthorized changes.
Netwrix recommends our default policy as a foundational best practice. In addition, consider
Specific Monitoring for anything needing special protection.
-
+
+
+
+
Platform Governance for Salesforce documents **Unresolved Non-Compliant Changes** in both a List
View and a Report. Both show you all the changes that should have received approval and the level of
@@ -57,6 +59,87 @@ prioritize what you see.
+## Related Tab Overview
+
+The Related tab on the Policy page provides a consolidated view of all elements associated with a Change / Approval Policy and serves as the main workspace for managing policy scope and tracking its usage.
+
+From this tab, you can:
+
+### View Customizations Associated with the Policy
+
+The Customizations section shows which Salesforce customizations are currently governed by the policy.
+
+### Add or Manage Customizations
+
+You can associate new customizations with the policy using two actions:
+
+- **Add Customizations**: Manually select and assign specific customizations to the policy.
+- **Select Change Level By SF Type**: Assign the policy automatically to all customizations of selected Salesforce Types (for example, ApexClass, Profile, PermissionSet, CustomObject).
+
+### Review Change Logs
+
+The Change Logs section lists all change events related to customizations and/or change requests that are governed by this policy. This provides visibility into what was changed, when it was changed, and the type of operation performed.
+
+### Review Change Requests
+
+The Change Requests section displays all change requests that have this policy applied, along with their current approval status and stage.
+
+### Track Policy History
+
+The Change / Approval Policy History section records all modifications made to the policy itself, including changes to approvers, settings, and creation details, providing a full audit trail.
+
+Together, these sections make the Related tab the central place to manage policy assignments, understand how a policy is being applied, and audit both customization activity and policy configuration changes.
+
+
+
+## Automatic Policy Assignment
+
+Platform Governance introduces an intelligent policy assignment mechanism for Salesforce customizations. When you define a policy and select specific Salesforce Types (such as Profile, PermissionSet, CustomObject), the system automatically applies this policy to any new customizations that match those types.
+
+### How Automatic Policy Assignment Works
+
+There are two primary methods for assigning policies to customizations:
+
+
+
+#### Option 1: Select Change Level By SF Type
+
+To configure Automatic Policy Assignment by Salesforce Type:
+
+1. Navigate to the Policy record.
+2. Go to the Related tab in the Customizations panel.
+3. Click on the "Select Change Level By SF Type" button.
+
+
+
+
+This method allows you to automatically assign policies to specific Salesforce object types.
+
+#### Option 2: Add Customization
+
+Alternatively, you can manually add specific customizations to a policy:
+
+1. Navigate to the Policy record.
+2. Go to the Related tab in the Customizations panel.
+3. Click on the "Add Customization" button.
+4. Select the customizations you want to apply the policy to.
+
+
+
+This method provides flexibility in applying policies to individual customizations.
+
+The core process remains the same:
+
+1. **Policy Configuration**: Select target Salesforce Types or specific customizations in the policy configuration interface.
+2. **Customization Creation**: When a new customization is created, the system checks its type against the defined policy.
+3. **Automatic Mapping**: If the customization type matches the policy's selected types, the policy is automatically assigned.
+
+This feature ensures consistent governance by:
+- Reducing manual policy assignment
+- Maintaining uniform change monitoring across your Salesforce org
+- Minimizing human error in policy management
+
+
## Specific Monitoring
The default policy may be all you require. However, you should consider whether there are specific
@@ -86,30 +169,39 @@ advantage of showing you the Non-Compliant Changes and providing an easy workflo
### Specific Customizations
-In some cases, it is essential to monitor changes to specific Customizations, Objects, or Fields.
-For example:
+In some cases, it is essential to monitor and govern individual customizations, regardless of their Salesforce Type, rather than applying policies broadly by type. This approach is useful when specific components require stricter oversight than others of the same category.
+
+Typical examples include:
+
+- **Business-critical Apex classes, triggers, or flows.**
+- **Sensitive objects or fields related to security, privacy, or compliance.**
+- **High-impact reports, dashboards, or list views used for management or regulatory purposes.**
+- **Any customization that requires special approvals or tighter change control due to risk or business impact.**
+
+While policies can be automatically applied from the Policy record itself (as described in [Automatic Policy Assignment](#automatic-policy-assignment)), you can also assign a policy directly from the Customization record for more granular control.
+
+#### Applying a Policy from a Customization
+
+To associate a Change / Approval Policy with a specific customization:
-- Encrypted fields or other privacy-related fields. Changes likely need to be reviewed by the data
- security team.
-- Important List Views or Reports with role, SOQL, dashboard/script dependencies, or selected by
- owner.
-- Financially-sensitive Customizations such as contracts and compensation-related objects and
- fields.
-- Any other specific fields requiring special approvals.
+1. **Navigate to Customizations** and open the relevant list view (for example, Apex Scripts, Objects, Fields, or any other Salesforce Type).
-You can create a special policy with heightened sensitivity for these Customizations. For example,
-you can require general approval of report changes and add special approvers, such as the CFO.
+2. **Select the customization** you want to govern.
-To apply the policy to Customizations you are concerned about:
+3. **Click Edit** from the row action menu.
-1. Create a **List View** that selects the Customization records to protect, based on your criteria.
-2. Add a **Record Type** filter with a single Record Type so that you can edit directly from the
- List View.
-3. Include the **Change / Approval Policy** field as a List View column.
-4. Select one or more Customizations and select the **Change / Approval Policy**.
+4. In the **Edit Customization** dialog:
+ - Use the **Change / Approval Policy** field to search for and assign an existing policy, or create a new one.
+ - Optionally, associate the customization with an existing Change Request using the **Add to Change Request** field.
+
+5. **Click Save** to apply the changes.
+
+This method provides fine-grained governance at the individual customization level and complements the automatic assignment mechanisms described in the [Automatic Policy Assignment](#automatic-policy-assignment) section.
+ 
+
### Specific Changes
Sometimes, you are more concerned about what is being changed than who is doing it. The Technical
@@ -118,21 +210,29 @@ watching your org to spot problems before they happen.
### Adding Custom Fields and Objects to the Policy
-When you add sensitive objects to the Policy, you may also need to add the Custom Fields that belong
-to that Object. There is a new **Set Policy** option on the Customization record to easily add it to
-the policy.
+When you add sensitive objects to a policy, you may also need to apply the same policy to the Custom Fields that belong to that object. Platform Governance for Salesforce provides a streamlined **Set Policy** action directly on the Customization record to support this workflow.
+
+#### Applying a Policy from a Custom Object
+To assign a Change / Approval Policy to a Custom Object and its related fields:
+
+1. Navigate to Customizations.
+2. Search for and open the CustomObject you want to govern.
+3. On the Customization record, click Set Policy.
-1. Open **Customizations**.
-2. Search for **Customizations** **CustomObject**.
+
- 
+4. In the Set Policy dialog:
+ - Assign the desired Change / Approval Policy to the Custom Object.
+ - Review the list of related Custom Fields associated with the object.
+5. Select individual fields, or use the header checkbox to select all fields.
+6. Click:
+ - Update Selection to apply the policy only to the selected fields, or
+ - Update All to apply the policy to the object and all its fields.
-3. Open the Customization to add to a policy.
-4. Click **Set Policy**.
+7. Click Save to complete the assignment.
- 
+
-5. Select individual customizations or click the check box in the heading bar to select all.
-6. Click **Save**.
+This approach ensures consistent governance across an object and its underlying fields while allowing flexibility to apply policies only where needed.
-**Next Technical Debt Topic:** [Org Clean Up](/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up.md)
+**Next Technical Debt Topic:** [Org Clean Up](/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up.md)
\ No newline at end of file
diff --git a/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up.md b/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up.md
index 6791cc35fa..cb0bb97551 100644
--- a/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up.md
+++ b/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up.md
@@ -63,34 +63,6 @@ Some are critical to ongoing business processes, others are quick solutions to d
These one-time quick reports accumulate in your orgs, causing confusion and inefficiency. Refer to
[Automated Report Clean Up](/docs/platgovsalesforce/tools/automated_report_clean_up.md) for more details.
-Automated Report Clean Up safely archives Reports following the rules and criteria you set up. The
-process is simple:
-
-1. Set up default rules. For example,
-
- - Reports not used within the past year
- - Reports owned by people who no longer have access to Salesforce and have not used in 6 months
-
-2. Run the analysis on an ad hoc basis and review your results.
-3. Exclude any Reports to be retained, either manually by changing the rule settings to exclude
- Reports based on:
-
- - Report Owners
- - Related Roles
- - Scheduled
- - Private Reports
- - Date Last Used
-
-4. Excludes Reports covered by a special policy or with any downstream dependencies to ensure you do not delete something important.
-
- - Emails Report owners (if desired) that the Report is being archived. The owner can retain the
- Report with a simple mouse click. The Date Last Used is updated to the current date.
- - Deletes the Reports that were not retained, but keeps the Report definition.
-
- When you run the Clean Up, Archived Reports can be easily be restored if needed.
-
-5. Schedule your rules to run on a regular basis to keep your orgs cleaned up and efficient.
-
## Employees Related to a Customization
Knowing who is using a customization is useful. This is tackled in steps, by Users and Owners.
diff --git a/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up_example.md b/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up_example.md
index 6945684e5c..282d24a6ed 100644
--- a/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up_example.md
+++ b/docs/platgovsalesforce/techdebt/tech_debt_org_clean_up_example.md
@@ -108,33 +108,60 @@ a problem. Some things to consider:
## Step 4: Group Customizations for Approval and Clean Up
-Now that you have identified what you can clean up, you can proceed with the Approval process. Some
-Customizations may require different levels of approval or different approvers. If you are using
-Intelligent Change Enablement, you can group related Customizations for approval and assign them to
-a Change Request directly from the List View:
+Now that you have identified the Customizations that can be cleaned up, you can proceed with the
+approval process. Related Customizations can be grouped and managed using a **Change Request**.
1. Click the **Change Request** tab and click **New**.
2. Enter the name and a brief description of the clean up project. Set the **Change Type** to
**Clean Up**. If you are using an external change approval system such as Jira or ServiceNow, you
can enter the **External Change Request Number**.
- 
+ 
-3. On your List View, set the **Add To Change Request** field for the Customizations you are
- planning to clean up with this Change Request.
+3. Open the Change Request and navigate to the **Customizations** tab.
+4. Click **Add/Remove** to add Customizations to the Change Request.
- 
+ 
-4. Open your Change Request and view the Impact Analysis for the Customizations you want to clean
- up. You are warned if there are SOQL, code, workflow, role, profile filter report or List View
- dependencies or if the field affects actively used Reports.
+5. In the **Add Customizations to Change Request** window:
+ - Use **Customization Name** to search for Customizations.
+ - Use **Salesforce Type** to filter by metadata type (for example, **CustomField**).
+ - Optionally filter by **Namespace** or **Last Modified By**.
+ - Select one or more Customizations using the checkboxes.
+ - Click **Confirm Selection** to add them to the Change Request.
- 
+ 
+
+6. The selected Customizations appear in the **Customizations** tab of the Change Request. From this
+ view, you can:
+ - Review the list of Customizations included in the clean up.
+ - Remove Customizations if needed.
+ - Export the list using **Export to CSV**.
+
+ 
+
+7. Navigate to the **Impact Analysis** tab to review the potential impact of cleaning up the selected
+ Customizations.
+
+ 
+
+ 
+
+ The Impact Analysis categorizes Customizations into the following sections:
+ - **Can Be Safely Deleted or Modified**
+ - **Cannot Be Safely Deleted or Modified**
+ - **Inactive Customizations**
+
+ This analysis identifies dependencies such as references in reports, scripts, workflows, or other
+ metadata that could be affected by the clean up.
+
+8. Review the Impact Analysis results carefully. If Customizations appear under
+ **Cannot Be Safely Deleted or Modified**, further investigation or remediation may be required
+ before proceeding.
+
+9. When you are satisfied with the scope and impact of the clean up, submit the Change Request for
+ approval.
-5. If you need to make changes to the Customizations, **Edit** the Change Request and select **View
- All** in the Customizations field. You can **Add** or **Remove** Customizations to the **Selected
- Customizations** list. **Save** when you are finished.
-6. When you are ready, Submit your Change Request for Approval.
:::tip
You can add additional approvers (beyond what is required for the policy) to the Change Request. Initially, only the approvers from your default policy are required. There are two methods to add additional approvers:
diff --git a/docs/platgovsalesforce/techdebt/tech_debt_org_specific_clean_up_approaches.md b/docs/platgovsalesforce/techdebt/tech_debt_org_specific_clean_up_approaches.md
index 83e7e37a97..e620ac47c7 100644
--- a/docs/platgovsalesforce/techdebt/tech_debt_org_specific_clean_up_approaches.md
+++ b/docs/platgovsalesforce/techdebt/tech_debt_org_specific_clean_up_approaches.md
@@ -130,8 +130,7 @@ Points to consider:
- Restricting the List View to one Record Type enables you to edit records directly from the List
View.
-- Search carefully if using multiple terms (refer to this
- [Salesforce Search guide](https://help.salesforce.com/articleView?id=000247472andtype=1)) - quotes
+- Search carefully if using multiple terms - quotes
can be useful to enforce just the string you are looking for. **"Search Term"** (in quotes) finds
objects with that phrase whereas **Search Term** (unquoted) finds anything with **Search** and
**Term** even if they are in different fields in the List View.
diff --git a/docs/platgovsalesforce/tools/automated_report_clean_up.md b/docs/platgovsalesforce/tools/automated_report_clean_up.md
index b0c3fee86c..e4b54e87e0 100644
--- a/docs/platgovsalesforce/tools/automated_report_clean_up.md
+++ b/docs/platgovsalesforce/tools/automated_report_clean_up.md
@@ -14,193 +14,272 @@ Archived reports can be restored.
The **Automated Report Clean Up** tool has two operating modes:
-- **Automatic** - scheduled automated report clean up that runs continuously using all rules marked
- Automatic.
-- **Run Now** - starts report clean up that runs once and completes within seven days using current
- clean up rule.
+- **Automatic** - scheduled automated report clean up that runs based on the configured schedule for
+ rules marked **Automatic**.
+- **Run Now** - starts report clean up immediately using the current clean up rule.
Menu options are available to access the rules and lists:
+- New Rule
- Report Clean Up Rules
- Report Clean Up Status
- Archived Reports
- Retained Reports
-- Reports To Be Archived
+- Reports to be Archived
+- Reports to Restore
-### Report Clean Up Rules
+## Report Clean Up Rules
Report Clean Up rules are created by the administrator and used to locate Reports matching the rule
-criteria. Report Clean Up rules are used for both Automatic and Run Now.
+criteria. Report Clean Up rules are used for both **Automatic** and **Run Now**.
-To create or edit rules, access **Netwrix Dashboard**> **Tools** > **Automated Report Clean Up
-Tool**
+To create or edit rules, access **Netwrix Dashboard** > **Tools** > **Automated Report Clean Up Tool**
+and select **New Rule** or **Report Clean Up Rules**.
-- **Name** is the assigned name for the **Report Clean Up Rule Record**.
+
+
+### Rule Details
+
+- **Name** is the assigned name for the **Report Clean Up Rule**.
- **Description** is the purpose of the rule record. An informative description helps administrators
easily maintain and identify rules.
- **Notify Report Owners Prior to Archive** check to send email to report owners prior to archive.
Default is checked.
-- **Automatic** is used to include the rule in the automated report. This option is not available
- until the **Preview** function has been used.
-- **Inactive** check to exclude this Report Clean Up Rule from the automated report.
-- **Filter Summary** displays all of the current filters for the rule. If default filters such as
- **Exclude Private Reports** are turned off, they are displayed in red as **Included**.
-- **Notes** displays information about the Report Clean Up for this rule.
+- **Automatic** check to include the rule in the automated report clean up.
+- **Inactive** check to disable this Report Clean Up Rule.
+
+**Please Note:** The following reports are excluded from clean up:
+
+- Reports in private folders
+- Reports with Change/Approval Policy that requires a Change Record
+- Managed Package Reports
+
+### Schedule
-**Basic Filters**
+When **Automatic** is enabled, configure the schedule for the rule.
+
+- **Weekly Event**
+- **Monthly Event**
+- **Yearly Event**
+- **Repeat Every "N" Week(s)** (weekly schedule)
+- **End By**:
+ - **Date**
+ - **Time**
+ - **No End Date**
+- **Next Run Date** displays the next scheduled execution date/time (system calculated).
+
+### Filters
+
+#### Basic Filters
- **Report Name** filters reports to clean-up by name. Filter operator is _startswith_ and the
wildcard _%_ may be used. Default is blank.
- Example: _Custom % Report%_ returns all reports with a name starting with '_Custom_ ' followed by
- any character and the name must contain '_Report_' such as _Custom Inventory Detail Report_.
+ Example: _Custom % Report%_ returns all reports with a name starting with '_Custom_' followed by
+ any character and containing '_Report_'.
- **Report API Name** filters reports to clean-up by API Name. Filter operator is _startswith_ and
the wildcard _%_ may be used. Default is blank.
- Example: _%testing_ returns all reports with an API Name containing the word '_testing_' such as
- _customreport_testing_1_.
-- **Months Since Date Last Used, Retained/Restored** filters reports by the last run date of the
- report or the restore/retain date, whichever is the most recent. Reports that have been used,
- restored, or retained within the specified timeframe are excluded from the report. Default is
- **6** months.
-- **Exclude Private Reports** excludes reports set as **Private** by report owners. Default is
- checked.
+ Example: _%testing_ returns all reports with an API Name containing '_testing_'.
+- **Months Since Date Last Used, Retained** filters reports by the most recent activity date (last
+ run date, retained, or restored). Reports used within the specified timeframe are excluded.
+ Default is **6** months.
- **Exclude Reports Less Than A Month Old** excludes new reports that have not been run. Default is
checked.
-**Advanced Filters**
+#### Advanced Filters
- **Select/Selected Report Owner(s)** filters reports by matching selected owners for the rule or if
- **Exclude Owner(s)** is checked, to exclude matching owners for the rule. Scroll or use the
- **Search User** box for **Select Report Owners**. Multiple owners can be selected. Click the right
- arrow to add to the **Selected Report Owner(s)**. Remove owners by selecting them in the
- **Selected Report Owner(s)** field and clicking the left arrow. Default is blank.
-- **Select/Selected Role(s)** filters reports by matching selected roles for the rule or if
- **Exclude Role(s)** is checked, to exclude matching roles for the rule. Select one or more roles
- in the **Select Roles** field. Click the right arrow to add to the **Selected Role(s)**. Remove
- roles by selecting them in the **Selected Role(s)** field and clicking the left arrow. Default is
- blank.
-- **Select/Selected Inactive Owner(s)** filters reports by matching selected owners for the rule or
- if **Exclude Inactive Owner(s)** is checked, to exclude matching owners for the rule.Select one or
- more inactive owners in the **Select Inactive Owners** field. Click the right arrow to add to the
- **Selected Inactive Owner(s)**. Remove owners by selecting them in the **Selected Inactive
- Owner(s)** field and clicking the left arrow. Default is blank.
-
-**Excluded Reports From Preview**
-
-Lists any reports excluded after the **Preview** function is used.
-
-#### Rule Preview
-
-The **Preview** function provides a quick method to mark reports to be retained or to included for
-clean up. The Run Now feature begins an immediate run for the rule.
-
-1. Administrators can click **Preview** on an Report Clean Up Rule. **Preview** displays the rule,
- filters and conditions.
-2. Review the Report List.
- Click **Include All** or **Exclude All** to mark all the reports. **Include** triggers a final
- notification email to be sent to the report owners. Unchecked retains the report.
-3. Click Run Now to begin a Report Clean Up for the rule.
-4. After previewing, you can click **Automatic** on the Report Clean Up Rule to include the rule for
- automatic reports.
+ **Exclude Owner(s)** is checked, to exclude matching owners.
+- **Select/Selected Inactive Owner(s)** filters reports by matching selected inactive owners.
+ **All Inactive Owner(s)** includes all inactive owners.
+
+### Rule Preview
+
+The **Preview** function provides a quick method to validate the rule and review the list of
+matching reports.
+
+1. Administrators can click **Preview** on a Report Clean Up Rule.
+2. Review the rule summary including **Rule Name**, **Number of Reports to Clean Up**, and
+ **Rule Filters**.
+3. Review the **Report List**, which includes:
+ - **Name**
+ - **API Name**
+ - **Owner**
+ - **Date Created**
+ - **Date Last Used**
+4. Available actions:
+ - **Back**
+ - **Save**
+ - **Save & Run**
+ - **Delete**
-#### Run Now
+### Run Now
-This option immediately begins an Report Clean Up using the current rule.
+The **Save & Run** option immediately begins a Report Clean Up using the current rule.
If a Report matches the Clean Up Rule:
-1. Summary notification of all the matching reports is sent to the rule owner.
-2. Immediate notice to all report owners with their reports that are about to be archived.
- Notifications include a **Retain this Report** link. A **Preview** link is available for the user
- to view the Report.
-3. If the **Retain Report** link is not used and the Report has not been used, final notifications
- are sent to all report owners seven calendar days after the **Run Now** option was used. The
- notification includes the date the report is to be archived.
-4. If the **Retain Report** link is not used and the Report has not been used by the archive date:
-
- - Report is archived.
- - Archive notifications are sent to rule owner and all report owners.
- - Report is added to administrator's Archived Reports list.
- - Summary notification of all auto-archived reports are sent to the rule owner.
+1. Summary notification of all matching reports is sent to the rule owner.
+2. Immediate notice is sent to all report owners. Notifications include a **Retain this Report**
+ link and a **Preview** link.
+3. If the report is not retained and not used, a final notification is sent prior to the archive
+ date.
+4. If the report is not retained and not used by the archive date:
+ - Report is archived.
+ - Archive notifications are sent to rule owner and report owners.
+ - Report is added to **Archived Reports**.
+ - Summary notification is sent to the rule owner.
-### Automated Run Workflow
+## Automated Run Workflow
-**Automated Report Clean Up** runs continuously comparing reports to all rules marked **Automatic**.
-Administrators receive weekly summary information containing: **identified reports**, **retained
-reports**, **scheduled to be archived reports** and **archived reports**.
+**Automated Report Clean Up** runs based on the schedule of rules marked **Automatic**.
1. When a Report matches a Clean Up Rule:
+ - Notification is emailed to the rule owner.
+ - Notification is emailed to report owners unless disabled.
+ - All notifications include a **Retain this Report** link.
+ - Report is added to **Reports to be Archived**.
+2. If the report is not retained and not used:
+ - Final notifications are sent.
+3. If the report is not retained and not used by the archive date:
+ - Report is archived.
+ - Notifications are sent.
+ - Report is added to **Archived Reports**.
+
+## Report Clean Up Status
+
+Open **Netwrix Dashboard** > **Tools** > **Automated Report Clean Up Tool** > **Report Clean Up Status**
+to view current status.
- - Notification is emailed to the rule owner. The Report is also included in the summary
- notification to the rule owner.
- - Notifications are sent the first closest Sunday since the rule was marked **Automatic**.
- - Notification is emailed to the report owners unless **Notify Report Owners Prior to Archive**
- is turned off for the rule.
- - All email notifications include a **Retain this Report** link. A **Preview** link is available
- for the user to view the Report.
- - Report is added to the **Automated Report Clean Up** > **Reports To Be Archived (Auto)** list.
+- **Status**:
+ - **Pending**
+ - **Pending Notification**
+ - **In Notice Period**
+ - **Processing**
+ - **Completed**
+ - **Canceled**
+- **Automatic** indicates whether the rule is scheduled.
-2. If the **Retain Report** link is not used and the Report has not been used, second notifications
- are sent the following Sunday after the first notification date. The notification includes the
- date the report is to be archived.
-3. If the **Retain Report** link is not used and the Report has not been used by the archive date:
+## Retaining a Report
- - Report is archived.
- - Archive notifications are sent to rule owner and all report owners.
- - Report is added to administrator's Archived Reports list.
+Notification emails contain a **Retain this Report** link.
-### Report Clean Up Status
+- Updates **Date Last Used, Retained/Restored**.
+- Adds the report to **Retained Reports**.
+- Prevents archiving.
-Open **Netwrix Dashboard**> **Tools** > **Automated Report Clean Up Tool** > **Report Clean Up
-Status** to view current status.
+## Auto Archiving a Report
-- **Status**:
- **Pending** - initial status for the run.
- **Pending Notification** - reports have been identified, no notifications sent.
- **In Notice Period** - at least one notification has been sent.
- **Processing** - report is being auto-archived.
- **Completed** - all identified reports have been archived, and email sent to rule owner and
- administrator.
- **Canceled** - **Automatic** checkbox was turned off for the rule.
-- **Automatic**: rule is set to **Automatic** if checked.
+If a report is not retained:
-
+- Report is archived.
+- Customization record is marked **Inactive**.
+- Report is added to **Archived Reports**.
+- A **Restore** option becomes available.
+- Notifications are sent to rule owner and administrators.
-### Retaining a Report
+
-Notification emails contain a link to **Retain this report** for each identified report.
+## Restoring an Auto Archived Report
-Users can click on **Retain this report** to prevent archiving the report. Use **Preview** link to
-view the Report. The Retain process:
+A Salesforce Administrator can restore an archived report from **Archived Reports**,
+**Reports to Restore**, or using the **Restore** link in notification emails.
-- Updates the **Date Last Used, Retained/Restored** to the current date.
-- Adds the report to the **Automated Report Clean Up** > **Retained Reports** report.
-- Notifies the owners the report will be retained.
+- Report is restored with a new internal ID.
+- **Date Last Used, Retained/Restored** is updated.
+- Report is added to **Retained Reports**.
-### Auto Archiving a Report
+## Report Clean Up Reports
-If report owners or users do not click on **Retain this report** in the email notifications, the
-report is archived. The Archive process:
+The Automated Report Clean Up tool includes Salesforce reports that allow administrators to monitor
+the clean up process.
-- Archives the report.
-- Adds the report to the **Automated Report Clean Up** > **Archived Reports** report.
-- Marks Customization record for the report I**nactive**.
-- A **Restore** button is added to the **Clean Up** tab on the customization record for the report.
-- Auto Archive notifications are sent to the rule owner and administrators. A **Restore** link is
- included in the email.
+### Reports to Restore
-
+**Filters used:**
+
+- **Archive** equals **True**
+- **Clean-up Status** not equal to **Restored**
+
+**Visible Columns:**
+
+- **Customization: ID**
+- **Customization: Customization Name**
+- **API Name**
+- **Archive**
+- **Clean Up Rule Name**
+- **Clean Up Archived Date**
+- **Restore Url**
+
+### Reports to be Archived
+
+**Filters used:**
+
+- **To be Archived** equals **True**
+
+**Visible Columns:**
+
+- **Customization: ID**
+- **Customization: Customization Name**
+- **Archive**
+
+### Retained Reports
+
+**Filters used:**
+
+- **Retain** equals **True**
+
+**Visible Columns:**
+
+- **Customization: Created By**
+- **Customization: Customization Name**
+- **API Name**
+- **Date Last Used**
+- **Active**
+- **Archive**
+
+### Archived Reports
+
+**Filters used:**
+
+- **Archive** equals **True**
+- **Clean-up Status** equals **Archived**
+
+**Visible Columns:**
+
+- **Customization: ID**
+- **Customization: Customization Name**
+- **Clean-up Status**
+
+### Report Clean Up Status (Report)
+
+**Filters used:**
+
+- **Automated** equals **True**
+
+**Visible Columns:**
+
+- **Search Clean-up Rule: ID**
+- **Status**
+- **Search Clean-up Rule: Name**
+- **Description**
+- **Report API Name**
+- **Report Name**
+- **Months Since Last Used, Retained/Restored**
+- **Automatic**
-### Restoring an Auto Archived Report
+### Report Clean Up Rules (Report)
-A Salesforce Administrator can restore an auto archived report. Open the **Clean Up** tab of the
-Customization record for the report or the report **Automated Report Clean Up** > **Archived
-Reports**. Click **Restore**. Or use the **Restore** link in the email sent to the rule owner and
-administrators.
+**Visible Columns:**
-- Report is restored. Restored reports have a different internal ID from their original version.
-- Updates the **Date Last Used, Retained/Restored** to the current date.
-- Adds the report to the **Automated Report Clean Up** > **Retained Reports** list.
+- **Search Clean-up Rule: Name**
+- **Description**
+- **Archive Date**
+- **Search Clean-up Rule: Created Date**
+- **Report API Name**
+- **Report Name**
+- **Months Since Last Used, Retained/Restored**
+- **Automatic**
diff --git a/docs/platgovsalesforce/tools/dlu_configuration.md b/docs/platgovsalesforce/tools/dlu_configuration.md
new file mode 100644
index 0000000000..b63942b379
--- /dev/null
+++ b/docs/platgovsalesforce/tools/dlu_configuration.md
@@ -0,0 +1,68 @@
+---
+title: "DLU Configuration"
+description: "DLU Configuration User Guide"
+sidebar_position: 110
+---
+
+# DLU Configuration
+
+## Overview
+
+The DLU Configuration tool provides comprehensive support for the Date Last Use (DLU) Scheduler in Netwrix for Salesforce.
+
+## Accessing DLU Configuration
+
+Navigate to **Netwrix Dashboard** > **Scanner** > **DLU Configuration**.
+
+
+
+## General Configuration
+
+The General Configuration section allows administrators to select which Salesforce metadata types the DLU batches should process.
+
+
+
+- Only metadata types currently supported by the DLU Scanner are displayed. Unsupported Salesforce types are not shown and cannot be selected.
+- Once selected, the scheduler will process only the chosen types. If no types are selected, the DLU Scanner will process all supported types shown in the list.
+
+## Custom Fields Configuration
+
+The Custom Fields Configuration section provides granular, field-level control.
+
+
+
+Administrators can:
+- Choose whether to search for Standard Fields or Custom Fields
+- Select specific fields
+- Save their preferences
+
+Only the selected fields will be processed by the DLU Scanner, allowing customers to focus on what they want and reduce unnecessary processing.
+
+## How the Configuration Is Used
+
+The DLU Scanners use the saved configuration to determine which Salesforce metadata types, objects, and fields are included in each scheduled execution.
+
+Any changes made in the DLU Configuration are applied to subsequent scanner runs.
+
+## DLU Scanner Scheduler Configuration
+
+To ensure the DLU Scanner runs automatically, you must configure and enable the scheduler.
+
+### Steps to configure the scheduler:
+
+1. Navigate to **Netwrix Dashboard** > **Scanner** > **Scheduler**.
+
+ 
+
+2. Locate the DLU Scanner in the scheduler list.
+
+ 
+
+3. Configure the execution frequency according to your organization's requirements.
+4. Enable the scheduler by selecting the highlighted option.
+5. Save the configuration.
+
+Once enabled, the scheduler will execute the DLU Scanner according to the configured frequency and use the settings defined in DLU Configuration.
+
+:::note
+If the scheduler is disabled, no DLU scans will run, even if the DLU Configuration is correctly defined.
\ No newline at end of file
diff --git a/docs/platgovsalesforce/tools/export_object_attachment_records.md b/docs/platgovsalesforce/tools/export_object_attachment_records.md
index 1af6d2528d..d073cae2a0 100644
--- a/docs/platgovsalesforce/tools/export_object_attachment_records.md
+++ b/docs/platgovsalesforce/tools/export_object_attachment_records.md
@@ -1,37 +1,39 @@
---
-title: "Export Object Attachment Records"
-description: "Export Object Attachment Records"
+title: "Export Attachment Records"
+description: "Export Attachment Records"
sidebar_position: 60
---
-# Export Object Attachment Records
+# Export Attachment Records
When an [Environment Comparison](/docs/platgovsalesforce/tools/environment_comparison.md) is run, or [Object](/docs/platgovsalesforce/tools/export_objects.md),
[Profile](/docs/platgovsalesforce/tools/export_profiles.md) or [User](/docs/platgovsalesforce/tools/export_profiles.md) information is exported, an **Export
-Object Attachment** Record is created for the export. When an export request is completed, you
+Attachment** Record is created for the export. When an export request is completed, you
receive an email notification your export file is ready. The link in the notification opens the
-**Export Object Attachment** Record in Salesforce. Your download file is available under **Notes &
+**Export Attachment** Record in Salesforce. Your download file is available under **Notes &
Attachments**.
-
+
-The export history is saved in Salesforce. You can view the list, or add the Export Object
-Attachments tabs to your menu bar. The steps are different depending on if you are using the Lightning app or the Classic view.
+
+
+The export history is saved in Salesforce. The **Export Attachments** tab appears by default in both Salesforce Lightning and Classic views. If the tab is not visible, you can add it using the following methods:
## Salesforce Lightning
### View the List
-Enter **Export Object Attachments** in the **Search Salesforce** entry box on the top of your page.
+Enter **Export Attachments** in the **Search Salesforce** entry box on the top of your page.
-### Add the **Export Object Attachments** Tab
+### Add the **Export Attachments** Tab (if not visible)
-1. Open **Setup** > **Apps** > **App Manager**
-2. Locate **Strongpoint** in the list. From the pull down menu on the right, select **Edit**.
-3. Select **Export Object Attachments** from the **Available Tabs** and add it to the **Selected
- Tabs**.
+1. Click the pencil icon (⚙️) next to the navigation bar to **Personalize your Nav Bar**.
+2. Click **Add More Items**.
+3. Find **Export Attachments** in the list and add it to your navigation bar.
- 
+ 
+
+ 
4. Click **Save**.
@@ -40,17 +42,17 @@ Enter **Export Object Attachments** in the **Search Salesforce** entry box on th
### View the List
1. Click the **+** in the menu bar to open the **All Tabs** list (Salesforce Classic).
-2. Select **Export Object Attachments**.
+2. Select **Export Attachments**.
-
+
-### Add the **Export Object Attachments** Tab
+### Add the **Export Attachments** Tab (if not visible)
1. Click the **+** in the menu bar to open the **All Tabs** list.
2. Click **Customize My Tabs**
-3. Select **Export Object Attachments** from the **Available Tabs** and add it to the **Selected
+3. Select **Export Attachments** from the **Available Tabs** and add it to the **Selected
Tabs**.
- 
+ 
4. Click **Save**.
diff --git a/docs/platgovsalesforce/tools/export_objects.md b/docs/platgovsalesforce/tools/export_objects.md
index 678e15c9d3..03df3d6f98 100644
--- a/docs/platgovsalesforce/tools/export_objects.md
+++ b/docs/platgovsalesforce/tools/export_objects.md
@@ -29,10 +29,10 @@ Open **Netwrix Dashboard** > **Tools** > **Export Objects**
**Objects**
-Enter all or part of a name in **Filter** to filter the list of objects.
+Search for an object by entering all or part of its name in **Search Objects**.
-Select one or more objects in the list. Selected options are shown below the filter. Click the **X**
-within the selected option to remove it. You can use the **Select All** and **Clear All** options.
+Select one or more profiles from the Available list and use the arrow buttons to move them to Selected.
+To remove profiles, select them in the Selected list and use the left arrow to move them back to Available.
@@ -44,21 +44,19 @@ Click the toggles to activate or inactivate the settings you want to export.
**Profiles: Object and Field Level Security (Optional)**
-Enter all or part of a name in **Filter** to filter the list of profiles.
+Search for a Profile by entering all or part of its name in **Search Profile**.
-Select one or more profiles in the list. Selected options are shown below the filter. Click the
-**X** within the selected option to remove it. You can use the **Select All** and **Clear All**
-options.
+Select one or more profiles from the Available list and use the arrow buttons to move them to the Selected list.
+To remove profiles, select them in the Selected list and use the left arrow to move them back to Available.
**Permission Sets: Object and Field Level Security (Optional)**
-Enter all or part of a name in **Filter** to filter the list of permission sets.
+Search for a permission set by entering all or part of its name in **Search PermissionSet**.
-Select one or more permission sets in the list. Selected options are shown below the filter. Click
-the **X** within the selected option to remove it. You can use the **Select All** and **Clear All**
-options.
+Select one or more permissions set from the Available list and use the arrow buttons to move them to Selected.
+To remove permissions set, select them in the Selected list and use the left arrow to move them back to Available.
diff --git a/docs/platgovsalesforce/tools/export_profiles.md b/docs/platgovsalesforce/tools/export_profiles.md
index 0cb7e0ae11..97f24598f4 100644
--- a/docs/platgovsalesforce/tools/export_profiles.md
+++ b/docs/platgovsalesforce/tools/export_profiles.md
@@ -12,21 +12,43 @@ Governor Limits. You will receive an email with a link to the
[Export Object Attachment](/docs/platgovsalesforce/tools/export_object_attachment_records.md) record, where you can download your
file.
-1. Open **Netwrix Dashboard** > **Tools** > **Export Objects**.
-2. Open the **Profiles & Permission Sets** tab.
+Open **Netwrix Dashboard** > **Tools** > **Export Objects**.
+Open the **Profiles & Permission Sets** tab.
- 
+
-3. Scroll through the **Select Profile to be Exported**.
-4. Select one or more objects in the scroll box. Use **Shift** or **Ctrl** to select multiple
- objects.
-5. Click the right arrow to move the items to the **Selected Profiles** list. To remove an item from
- the **Selected Profiles** list, select it and click the left arrow.
-6. Select the **Settings to be exported**.
+**Profiles**
- 
+Search for an Profile by entering all or part of its name in **Search Profile**.
-7. Click **Download XLS**. The file _ProfileExport.xls_ is created.
+Select one or more profiles from the Available list and use the arrow buttons to move them to Selected.
+To remove profiles, select them in the Selected list and use the left arrow to move them back to Available.
+
+
+
+**Permission Sets**
+
+Search for a Permission Set by entering all or part of its name in **Search PermissionSet**.
+
+Select one or more permission sets from the Available list and use the arrow buttons to move them to Selected.
+To remove permission sets, select them in the Selected list and use the left arrow to move them back to Available.
+
+
+
+**Download XLS**
+
+Click **Download XLS** to export your selections. An email is sent with a link to the file
+_ProfilesExport.xls_.
+
+**Download Files**
+
+Click **Download Files** to see a list of generated files. The file does not appear in the list
+until it is complete.
+
+
+
+Click on the export name. The Export Attachments tab is opened, showing the attachment detail for
+your file. Click **View file** to download it to your Downloads folder.
### ProfilesExport.xls File
diff --git a/docs/platgovsalesforce/tools/export_users.md b/docs/platgovsalesforce/tools/export_users.md
index 2cd52d71d0..2a7c14483c 100644
--- a/docs/platgovsalesforce/tools/export_users.md
+++ b/docs/platgovsalesforce/tools/export_users.md
@@ -14,22 +14,41 @@ Governor Limits. You receive an email with a link to the
[Export Object Attachment](/docs/platgovsalesforce/tools/export_object_attachment_records.md) record, where you can download your
file.
-1. Open **Netwrix Dashboard** > **Tools** > **Export Objects**
-2. Open the **Users** tab.
+Open **Netwrix Dashboard** > **Tools** > **Export Objects**
+Open the **Users** tab.
-3. Scroll through the **Select User to be Exported** or enter all of part .of a user name in the
- **Filter** field.
-4. Select one or more objects in the scroll box. Use **Shift** or **Ctrl** to select multiple
- objects.
-5. Click the right arrow to move the items to the **Selected Users** list. To remove an item from
- the **Selected Users** list, select it and click the left arrow.
-6. Select the **Settings to be exported**.
+**Users**
+
+Search for a user by entering all or part of the name in **Search Users**.
+
+Select one or more users from the Available list and use the arrow buttons to move them to Selected.
+To remove users, select them in the Selected list and use the left arrow to move them back to Available.
+
+
+
+
+**Settings to be Exported**
+
+Click the toggles to activate or inactivate the settings you want to export.
-7. Click **Download XLS**. The file _UserExport.xls_ is created.
+**Download XLS**
+
+Click **Download XLS** to export your selections. An email is sent with a link to the file
+_User_Export.xls_.
+
+**Download Files**
+
+Click **Download Files** to see a list of generated files. The file does not appear in the list
+until it is complete.
+
+
+
+Click on the export name. The Export Attachments tab is opened, showing the attachment detail for
+your file. Click **View file** to download it to your Downloads folder.
#### UserExport.xls File
diff --git a/docs/platgovsalesforce/tools/field_tracking.md b/docs/platgovsalesforce/tools/field_tracking.md
new file mode 100644
index 0000000000..b8fc17168d
--- /dev/null
+++ b/docs/platgovsalesforce/tools/field_tracking.md
@@ -0,0 +1,177 @@
+# Field Tracking
+
+## Overview
+Field Tracking is a specialized configuration tool designed to monitor and detect changes in field permissions across Permission Sets and Profiles in your Salesforce environment. Each time the Field Tracking Scanner runs, it reads active monitoring rules, determines the monitored fields, and checks for permission changes.
+
+Monitoring Rules are a specialized configuration tool designed to track and detect changes in field permissions across Permission Sets and Profiles in your Salesforce environment.
+
+Changes in field access for Profiles and Permission Sets will no longer be documented by the autoscanner. This new tool replaces the previous feature for Fields, so it is crucial to add all sensitive fields to the Monitored Rules.
+
+## Accessing Field Tracking
+Navigate to the Netwrix Dashboard:
+- Tools > Access > Field Tracking
+
+## Key Sections
+The left-hand panel contains three main sections:
+1. Settings
+2. Monitoring Rules
+3. Monitored Fields
+
+
+
+## Settings
+
+### Monitoring Settings
+- Manually run the batch process by clicking "Run Now"
+- Automate the process with a Scheduler (daily, weekly, or monthly)
+- The process takes a snapshot of field permissions and creates a Change Log for detected modifications
+
+
+
+### Notification Settings
+You can enable Email Notifications to subscribe to reports showing field changes. Select the notification frequency — daily, weekly, or monthly — and define the list of recipients.
+As a user, you don’t need to manually subscribe to the report — the system automatically handles that for you. Simply enable notifications and add the users who should receive the emails.
+Any user receiving email notifications must have the "Netwrix Grant Permissions" PermissionSet assigned, as this permission set grants access to the related objects and features within the application.
+
+- Enable Email Notifications
+ - Choose notification frequency: daily, weekly, or monthly
+ - Define recipient list
+
+ 
+
+- Enable In-App Notifications
+If In-App Notifications are enabled, each batch execution creates a record in the Download Files component on the Netwrix Dashboard. This component provides links to daily reports showing all field permission changes detected for each day.
+
+Additionally, an Export Attachment record is created for each report. This tab is visible within the application and contains the export file associated with the report. However, users don’t need to access it directly, as all relevant information is already available through the Dashboard’s Downloaded Files bar.
+
+
+
+
+
+To save all configuration changes, click Save Settings.
+
+## Monitoring Rules
+This screen displays all existing monitoring rules. You can create, edit, or deactivate rules, and you can also search for rules by name or status.
+
+
+
+
+
+### Creating a New Rule
+Use the three-step wizard:
+
+1. **General Information**
+ - Enter rule name
+ - Add description
+ - Set activation status
+
+
+
+2. **Criteria Selection**
+ You can filter fields by:
+ - **Objects**
+ - Maximum of 5 different objects per criterion
+ - Error message if more than 5 objects are selected
+ - If you first select the “individual fields” criterion, the “objects” criterion will display only the objects of the fields selected under “individual fields.”
+
+
+
+ - **Individual Fields**
+ - Maximum of 25 fields total
+ - Automatic removal of associated fields when an object is deselected
+ - If you first select the “objects” criterion, the “individual fields” criterion will display only the fields of the objects selected under “objects"
+
+
+
+ - **Compliance Categories**
+ - Compliance Categories are classifications used to group data, records, or processes according to regulatory or compliance requirements, helping organizations manage and track adherence to laws, standards, and internal policies.
+ - No maximum limit
+ - Based on "Compliance Group" field in custom field customizations
+
+
+
+ - **Data Types**
+ - Free selection
+ - Requires prior object selection
+
+
+
+:::note
+The tracked fields must match all selected criteria.
+:::
+
+3. **Summary**
+ - Review selections
+ - Click Create to finalize the rule
+
+
+
+After creation, a confirmation message appears, and the list of rules updates automatically.
+
+
+
+### Rule Management
+- Edit or deactivate rules directly from the list
+- Deleting a rule sets it to Inactive
+
+
+
+
+
+## Monitored Fields
+After running the batch process, view:
+- All monitored fields
+- Last monitoring date
+- Current tracking status
+
+
+
+## Change Logs
+Change logs are automatically generated by the Field Tracking tool when the batch process is run. These logs provide a detailed record of field permission changes detected during the monitoring process.
+
+### Example Change Log
+
+
+The change log provides a comprehensive record of field permission modifications, typically including:
+- Timestamp of the change
+- Object name
+- Field name
+- Change Type
+- Monitoring Rule
+- Profile or Permission Set
+- Old Access and New Access
+
+## Available Reports
+
+### Monitored Fields Tracking Changes Report
+This report can be accessed through:
+- Menu: Reports > Access Reports > Monitored Fields Tracking Changes
+
+
+
+### Field Permission Changes By Date Report
+This report can be accessed through:
+- Component: Download Field on the Home page
+
+
+
+
+
+## Best Practices
+- Carefully select fields to track
+- Use compliance categories for better organization
+- Regularly review monitoring rules
+- Set up notifications to stay informed about field changes
+- Every time you create a new field, evaluate if the new field needs to be added to any existing Monitored Rule or if you need to create a new one.
+- Make sure the Field Tracking [scanner is scheduled](/docs/platgovsalesforce/scanner/scheduler.md) on a regular basis.
+
+## Limitations
+- Object selection limited to 5 per criterion
+- Field selection limited to 25 total
+- Requires careful configuration to avoid performance impacts
+
+## Troubleshooting
+- Check notification settings if reports are not received
+- Verify object and field selection criteria
+- Ensure proper permissions for tracking
+- Missing field access change log: Review if the field is part of a monitoring rule and/or if the rule is active.
diff --git a/docs/platgovsalesforce/tools/system_permission_tracking.md b/docs/platgovsalesforce/tools/system_permission_tracking.md
new file mode 100644
index 0000000000..ee9f665a28
--- /dev/null
+++ b/docs/platgovsalesforce/tools/system_permission_tracking.md
@@ -0,0 +1,205 @@
+---
+title: "System Permission Tracking"
+description: "System Permission Tracking User Guide"
+sidebar_position: 112
+---
+
+# System Permission Tracking
+
+## Overview
+
+System Permission Tracking monitors and detects changes in System Permissions across Permission Sets and Profiles in your Salesforce environment. Each scan compares the selected permissions against previous snapshots and generates a Change Log for any detected differences. When a permission changes—either because a Permission Set/Profile is modified or because a user gains or loses an assignment—the system records the impact at the user level, creating an individual Change Log entry for every affected user.
+
+## Accessing System Permission Tracking
+
+Navigate to: **Tools** > **Access** > **System Permission Tracking**
+
+
+
+## Key Sections
+
+- **Settings**
+- **Recommended Permissions**
+- **All Permissions**
+- **Selected Permissions**
+
+## Settings
+
+The Settings section contains all configuration options for enabling change detection, running the scanner, scheduling automated scans, and configuring email and in-app notifications.
+
+### Run Now
+
+Runs the System Permission scanner immediately, generating updated results without waiting for the scheduled scan.
+
+### Tracker Scheduler
+
+Automates the scanning process. You can choose between three scheduling options—**Daily**, **Weekly**, or **Monthly**—and configure only the essential fields such as time and applicable days.
+
+
+
+### Email Notifications
+
+You can enable Email Notifications to receive reports showing System Permission changes. Select a notification frequency and define the list of recipients. Users do not need to manually subscribe—the system handles this automatically. Recipients must have the 'Netwrix Grant Permissions' Permission Set assigned.
+
+
+
+#### Email Frequency & Timing
+
+Choose whether the report should be sent daily, weekly, or monthly, and configure the corresponding delivery time or date.
+
+#### Recipients
+
+Add users who will receive notification emails. Recipients must have the required Permission Set to access the internal components used by this feature. After saving, the recipients are automatically subscribed to the System Permission Change Log report.
+
+
+
+### In-App Notifications
+
+If In-App Notifications are enabled, each scan creates a record in the Downloaded Files component on the Netwrix Dashboard. This provides links to reports showing all detected System Permission changes. An Export Attachment record is also created, but users typically do not need to access it directly.
+
+**Example of a System Permission Change in Downloaded Files:**
+
+
+
+The Downloaded Files component displays a new entry for each scan that detects changes.
+
+**Example of a System Permission Change Log report opened from Downloaded Files:**
+
+
+
+The report shows detailed information about each permission change, including the affected users and the specific permissions that were modified.
+
+
+
+## Recommended Permissions
+
+Displays a curated list of high-risk permissions recommended for tracking. You can select or remove permissions and then click **Save** to update the tracked list.
+
+
+
+## All Permissions
+
+Allows searching and selecting System Permissions not included in the recommended list. Use the search bar to filter results, and click **Save** after selecting or removing permissions.
+
+
+
+## Selected Permissions
+
+Displays all System Permissions currently selected for tracking, whether selected from Recommended Permissions or All Permissions. You can remove all tracked permissions or selectively remove only specific ones.
+
+
+
+## Change Log
+
+The Change Log provides a detailed record of each detected change. Key fields include:
+
+- **Customization**: Related Profile or Permission Set
+- **Field Name**: System Permission name
+- **Assigned User**: User impacted by the change
+- **Enabled**: Indicates whether the permission was granted (True) or removed (False)
+
+
+
+
+
+### Viewing Change Logs
+
+1. Navigate to the Change Log section
+2. Review the list of detected changes
+3. Use filters to narrow down results by:
+ - Date range
+ - User
+ - Permission type
+ - Customization (Profile/Permission Set)
+4. Click on individual entries to view detailed information
+
+### Exporting Change Logs
+
+Change logs can be exported for further analysis or compliance reporting:
+
+1. Select the desired change log entries
+2. Click **Export** to download the data
+3. The export includes all relevant details about the permission changes
+
+## Best Practices
+
+- **Start with Critical and High-risk permissions**: Focus on the most important permissions first
+- **Use the Recommended Permissions list as your baseline**: This list is curated based on security best practices
+- **Avoid tracking large numbers of permissions**: This can increase scan duration and complexity
+- **Schedule scans outside peak business hours**: Minimize impact on system performance
+- **Periodically review selected permissions**: Ensure alignment with your organization's security policies
+- **Document your tracking strategy**: Maintain clear documentation of which permissions are tracked and why
+- **Set up appropriate notifications**: Ensure the right people receive alerts about permission changes
+- **Regular review of change logs**: Establish a routine for reviewing and acting on detected changes
+
+## Limitations
+
+- Tracking too many permissions can increase scan times
+- Some Salesforce permissions may behave differently depending on org configuration
+- Historical data is limited to the period since tracking was enabled
+- Change detection requires at least two scans to establish a baseline
+
+## Troubleshooting
+
+### No Change Logs Are Created
+
+**Issue**: The scanner runs but no change logs appear
+
+**Solutions**:
+- Confirm System Permission Scanning is enabled
+- Verify that Selected Permissions contains at least one permission
+- Ensure recent changes occurred in Profiles, Permission Sets, or user assignments
+- Check that at least two scans have been completed (baseline + comparison)
+- Review scanner execution logs for errors
+
+### Email Notifications Not Being Received
+
+**Issue**: Configured recipients are not receiving email notifications
+
+**Solutions**:
+- Ensure Email Notifications are enabled
+- Verify at least one valid recipient is added
+- Check that recipients have the required Permission Set ('Netwrix Grant Permissions')
+- Make sure a valid schedule is configured
+- Verify email addresses are correct in Salesforce
+- Check spam/junk folders for notification emails
+
+### Permissions Not Appearing in All Permissions
+
+**Issue**: Expected permissions are not showing in the All Permissions list
+
+**Solutions**:
+- Clear any applied search filters
+- Permissions already marked as selected will not appear in search results
+- Use **Refresh** to reload the list
+- Verify the permission exists in your Salesforce org
+- Check if the permission is already in the Recommended Permissions list
+
+### Scanner Takes Too Long to Complete
+
+**Issue**: System Permission scans are taking excessive time
+
+**Solutions**:
+- Reduce the number of tracked permissions
+- Schedule scans during off-peak hours
+- Review system resources and performance
+- Consider tracking only critical permissions
+- Contact Netwrix support if performance issues persist
+
+### Change Logs Show Unexpected Results
+
+**Issue**: Change logs contain entries that don't match expected changes
+
+**Solutions**:
+- Verify the baseline scan was completed successfully
+- Check for bulk permission changes or user assignments
+- Review the time range of the changes
+- Ensure no other administrators made concurrent changes
+- Validate that the tracked permissions are correctly configured
+
+## Related Topics
+
+- [Access Review Assistant](/docs/platgovsalesforce/tools/access_review.md)
+- [User Activity](/docs/platgovsalesforce/tools/user_activity.md)
+- [Profile Permission Comparison](/docs/platgovsalesforce/tools/profile_permission_comparison.md)
+- [Scanner Overview](/docs/platgovsalesforce/scanner/scanner_overview.md)
\ No newline at end of file
diff --git a/docs/platgovsalesforce/tools/tools_overview.md b/docs/platgovsalesforce/tools/tools_overview.md
index b73a32129e..da1e078697 100644
--- a/docs/platgovsalesforce/tools/tools_overview.md
+++ b/docs/platgovsalesforce/tools/tools_overview.md
@@ -24,3 +24,5 @@ The **Tools** tab accesses:
- [User Activity](/docs/platgovsalesforce/tools/user_activity.md) displays all activity for a specific user or all users. This tool is used before you can deactivate a user.
- [Automated Report Clean Up](/docs/platgovsalesforce/tools/automated_report_clean_up.md) runs automatically or on demand using custom rules to find and manage reports.
- [Change Logs Clean Up](/docs/platgovsalesforce/tools/change_logs_clean_up.md) sets the schedule to run the tool.
+- [DLU Configuration](/docs/platgovsalesforce/tools/dlu_configuration.md) provides comprehensive support for the Date Last Use (DLU) Scheduler.
+- [System Permission Tracking](/docs/platgovsalesforce/tools/system_permission_tracking.md) monitors and detects changes in System Permissions across Permission Sets and Profiles.
diff --git a/static/images/platgovsalesforce/app_netwrix_lightning.webp b/static/images/platgovsalesforce/app_netwrix_lightning.webp
index e421567440..9914202307 100644
Binary files a/static/images/platgovsalesforce/app_netwrix_lightning.webp and b/static/images/platgovsalesforce/app_netwrix_lightning.webp differ
diff --git a/static/images/platgovsalesforce/change_management/DRD.webp b/static/images/platgovsalesforce/change_management/DRD.webp
new file mode 100644
index 0000000000..3ed1c4f436
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/DRD.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_approvals_light.webp b/static/images/platgovsalesforce/change_management/change_request_approvals_light.webp
new file mode 100644
index 0000000000..a4a8ed2ba6
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_approvals_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_customizations_section_light.webp b/static/images/platgovsalesforce/change_management/change_request_customizations_section_light.webp
new file mode 100644
index 0000000000..ff9b7c3fc1
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_customizations_section_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_detail_section_light.webp b/static/images/platgovsalesforce/change_management/change_request_detail_section_light.webp
new file mode 100644
index 0000000000..77ae4c0d74
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_detail_section_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_drd_light.webp b/static/images/platgovsalesforce/change_management/change_request_drd_light.webp
new file mode 100644
index 0000000000..eabd5402c1
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_drd_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_impact_analysis_light.webp b/static/images/platgovsalesforce/change_management/change_request_impact_analysis_light.webp
new file mode 100644
index 0000000000..d343dda5c1
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_impact_analysis_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_new2_light.webp b/static/images/platgovsalesforce/change_management/change_request_new2_light.webp
index 0b937a2db9..dc632fc093 100644
Binary files a/static/images/platgovsalesforce/change_management/change_request_new2_light.webp and b/static/images/platgovsalesforce/change_management/change_request_new2_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_new4_light.webp b/static/images/platgovsalesforce/change_management/change_request_new4_light.webp
index dcffef3aaa..ae821922b8 100644
Binary files a/static/images/platgovsalesforce/change_management/change_request_new4_light.webp and b/static/images/platgovsalesforce/change_management/change_request_new4_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_new5_light.webp b/static/images/platgovsalesforce/change_management/change_request_new5_light.webp
index cfc30088c4..b790754e25 100644
Binary files a/static/images/platgovsalesforce/change_management/change_request_new5_light.webp and b/static/images/platgovsalesforce/change_management/change_request_new5_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_new6_light.webp b/static/images/platgovsalesforce/change_management/change_request_new6_light.webp
index b01fc68a4a..d68d6caec6 100644
Binary files a/static/images/platgovsalesforce/change_management/change_request_new6_light.webp and b/static/images/platgovsalesforce/change_management/change_request_new6_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_new_light.webp b/static/images/platgovsalesforce/change_management/change_request_new_light.webp
index 2d8deb69a9..61b0253576 100644
Binary files a/static/images/platgovsalesforce/change_management/change_request_new_light.webp and b/static/images/platgovsalesforce/change_management/change_request_new_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_proposed_section_light.webp b/static/images/platgovsalesforce/change_management/change_request_proposed_section_light.webp
new file mode 100644
index 0000000000..50c6c17119
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_proposed_section_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_release_section_light.webp b/static/images/platgovsalesforce/change_management/change_request_release_section_light.webp
new file mode 100644
index 0000000000..1396d5cd7a
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_release_section_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/change_request_submit_approval.webp b/static/images/platgovsalesforce/change_management/change_request_submit_approval.webp
new file mode 100644
index 0000000000..0243304210
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/change_request_submit_approval.webp differ
diff --git a/static/images/platgovsalesforce/change_management/changelog_details_light.webp b/static/images/platgovsalesforce/change_management/changelog_details_light.webp
new file mode 100644
index 0000000000..bda19ff467
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/changelog_details_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/changelog_diff_light.webp b/static/images/platgovsalesforce/change_management/changelog_diff_light.webp
new file mode 100644
index 0000000000..215779e7c0
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/changelog_diff_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/changelog_values1_light.webp b/static/images/platgovsalesforce/change_management/changelog_values1_light.webp
new file mode 100644
index 0000000000..8e29220128
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/changelog_values1_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/changelog_values2_light.webp b/static/images/platgovsalesforce/change_management/changelog_values2_light.webp
new file mode 100644
index 0000000000..12d7393097
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/changelog_values2_light.webp differ
diff --git a/static/images/platgovsalesforce/change_management/diffsummary_data_light.webp b/static/images/platgovsalesforce/change_management/diffsummary_data_light.webp
new file mode 100644
index 0000000000..268bb0a6c9
Binary files /dev/null and b/static/images/platgovsalesforce/change_management/diffsummary_data_light.webp differ
diff --git a/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_1.webp b/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_1.webp
new file mode 100644
index 0000000000..d1d1a75563
Binary files /dev/null and b/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_1.webp differ
diff --git a/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_2.webp b/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_2.webp
new file mode 100644
index 0000000000..048577690b
Binary files /dev/null and b/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_2.webp differ
diff --git a/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_3.webp b/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_3.webp
new file mode 100644
index 0000000000..ba08212b03
Binary files /dev/null and b/static/images/platgovsalesforce/changelogs/changelog_reporfolder_dashboardfolder_3.webp differ
diff --git a/static/images/platgovsalesforce/clean_up/scheduler.webp b/static/images/platgovsalesforce/clean_up/scheduler.webp
index a00c5405aa..af1f283b5a 100644
Binary files a/static/images/platgovsalesforce/clean_up/scheduler.webp and b/static/images/platgovsalesforce/clean_up/scheduler.webp differ
diff --git a/static/images/platgovsalesforce/customizations/customization_record.webp b/static/images/platgovsalesforce/customizations/customization_record.webp
index 6109d2f6a2..6eaafca10c 100644
Binary files a/static/images/platgovsalesforce/customizations/customization_record.webp and b/static/images/platgovsalesforce/customizations/customization_record.webp differ
diff --git a/static/images/platgovsalesforce/customizations/customization_record_lightning.webp b/static/images/platgovsalesforce/customizations/customization_record_lightning.webp
index 2c727ff919..1885e669f0 100644
Binary files a/static/images/platgovsalesforce/customizations/customization_record_lightning.webp and b/static/images/platgovsalesforce/customizations/customization_record_lightning.webp differ
diff --git a/static/images/platgovsalesforce/customizations/custquicksearch.webp b/static/images/platgovsalesforce/customizations/custquicksearch.webp
new file mode 100644
index 0000000000..85a7f4c7db
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/custquicksearch.webp differ
diff --git a/static/images/platgovsalesforce/customizations/folder_customization_record_1.webp b/static/images/platgovsalesforce/customizations/folder_customization_record_1.webp
new file mode 100644
index 0000000000..f42160bf20
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/folder_customization_record_1.webp differ
diff --git a/static/images/platgovsalesforce/customizations/folder_customization_record_2.webp b/static/images/platgovsalesforce/customizations/folder_customization_record_2.webp
new file mode 100644
index 0000000000..8b707e36b9
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/folder_customization_record_2.webp differ
diff --git a/static/images/platgovsalesforce/customizations/folder_customization_record_3.webp b/static/images/platgovsalesforce/customizations/folder_customization_record_3.webp
new file mode 100644
index 0000000000..ad3460fef1
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/folder_customization_record_3.webp differ
diff --git a/static/images/platgovsalesforce/customizations/folder_customization_record_4.webp b/static/images/platgovsalesforce/customizations/folder_customization_record_4.webp
new file mode 100644
index 0000000000..0875245fb9
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/folder_customization_record_4.webp differ
diff --git a/static/images/platgovsalesforce/customizations/folder_customization_record_5.webp b/static/images/platgovsalesforce/customizations/folder_customization_record_5.webp
new file mode 100644
index 0000000000..ff50989686
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/folder_customization_record_5.webp differ
diff --git a/static/images/platgovsalesforce/customizations/folder_customization_record_6.webp b/static/images/platgovsalesforce/customizations/folder_customization_record_6.webp
new file mode 100644
index 0000000000..f2dd3e6f24
Binary files /dev/null and b/static/images/platgovsalesforce/customizations/folder_customization_record_6.webp differ
diff --git a/static/images/platgovsalesforce/dlu_configuration/DLU_Custom_Fields.webp b/static/images/platgovsalesforce/dlu_configuration/DLU_Custom_Fields.webp
new file mode 100644
index 0000000000..f1836354f4
Binary files /dev/null and b/static/images/platgovsalesforce/dlu_configuration/DLU_Custom_Fields.webp differ
diff --git a/static/images/platgovsalesforce/dlu_configuration/DLU_General_Configuration.webp b/static/images/platgovsalesforce/dlu_configuration/DLU_General_Configuration.webp
new file mode 100644
index 0000000000..dfda1e50f9
Binary files /dev/null and b/static/images/platgovsalesforce/dlu_configuration/DLU_General_Configuration.webp differ
diff --git a/static/images/platgovsalesforce/dlu_configuration/DLU_Menu.webp b/static/images/platgovsalesforce/dlu_configuration/DLU_Menu.webp
new file mode 100644
index 0000000000..11db82e9a1
Binary files /dev/null and b/static/images/platgovsalesforce/dlu_configuration/DLU_Menu.webp differ
diff --git a/static/images/platgovsalesforce/dlu_configuration/Scheduler.webp b/static/images/platgovsalesforce/dlu_configuration/Scheduler.webp
new file mode 100644
index 0000000000..276ef81398
Binary files /dev/null and b/static/images/platgovsalesforce/dlu_configuration/Scheduler.webp differ
diff --git a/static/images/platgovsalesforce/dlu_configuration/Scheduler_Menu.webp b/static/images/platgovsalesforce/dlu_configuration/Scheduler_Menu.webp
new file mode 100644
index 0000000000..ffe8637b05
Binary files /dev/null and b/static/images/platgovsalesforce/dlu_configuration/Scheduler_Menu.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/AddAssignment.webp b/static/images/platgovsalesforce/installing_strongpoint/AddAssignment.webp
new file mode 100644
index 0000000000..17a84aa532
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/AddAssignment.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ApproveUseOfNamedCredential.webp b/static/images/platgovsalesforce/installing_strongpoint/ApproveUseOfNamedCredential.webp
new file mode 100644
index 0000000000..4859b22975
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ApproveUseOfNamedCredential.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ApproveUseOfNamedCredential2.webp b/static/images/platgovsalesforce/installing_strongpoint/ApproveUseOfNamedCredential2.webp
new file mode 100644
index 0000000000..d9b592248c
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ApproveUseOfNamedCredential2.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/AuthProviderView.webp b/static/images/platgovsalesforce/installing_strongpoint/AuthProviderView.webp
new file mode 100644
index 0000000000..42f187a53d
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/AuthProviderView.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ClickKeyAndSecret.webp b/static/images/platgovsalesforce/installing_strongpoint/ClickKeyAndSecret.webp
new file mode 100644
index 0000000000..59de1ee543
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ClickKeyAndSecret.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/CreateAuthProvider.webp b/static/images/platgovsalesforce/installing_strongpoint/CreateAuthProvider.webp
new file mode 100644
index 0000000000..275a2de240
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/CreateAuthProvider.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/CreateNameCredential.webp b/static/images/platgovsalesforce/installing_strongpoint/CreateNameCredential.webp
new file mode 100644
index 0000000000..a894b0e1a3
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/CreateNameCredential.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/EditPolicy.webp b/static/images/platgovsalesforce/installing_strongpoint/EditPolicy.webp
new file mode 100644
index 0000000000..c5ca8b112f
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/EditPolicy.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/EditPolicyMenu.webp b/static/images/platgovsalesforce/installing_strongpoint/EditPolicyMenu.webp
new file mode 100644
index 0000000000..0d942f815b
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/EditPolicyMenu.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ExternalApp1.webp b/static/images/platgovsalesforce/installing_strongpoint/ExternalApp1.webp
new file mode 100644
index 0000000000..2c5223e1b4
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ExternalApp1.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ExternalApp2.webp b/static/images/platgovsalesforce/installing_strongpoint/ExternalApp2.webp
new file mode 100644
index 0000000000..b9f9e51de6
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ExternalApp2.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ExternalApp3.webp b/static/images/platgovsalesforce/installing_strongpoint/ExternalApp3.webp
new file mode 100644
index 0000000000..7bc676b1c8
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ExternalApp3.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/ManageAssignment.webp b/static/images/platgovsalesforce/installing_strongpoint/ManageAssignment.webp
new file mode 100644
index 0000000000..ed52d4e19d
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/ManageAssignment.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/NamedCredentialView.webp b/static/images/platgovsalesforce/installing_strongpoint/NamedCredentialView.webp
new file mode 100644
index 0000000000..f7d1ad508e
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/NamedCredentialView.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/NetwrixLightningMenu.webp b/static/images/platgovsalesforce/installing_strongpoint/NetwrixLightningMenu.webp
new file mode 100644
index 0000000000..6d528b6054
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/NetwrixLightningMenu.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/NetwrixPermissionSet.webp b/static/images/platgovsalesforce/installing_strongpoint/NetwrixPermissionSet.webp
new file mode 100644
index 0000000000..1e3b135a5c
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/NetwrixPermissionSet.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/OpenExternalApp.webp b/static/images/platgovsalesforce/installing_strongpoint/OpenExternalApp.webp
new file mode 100644
index 0000000000..8c9325a43e
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/OpenExternalApp.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/UpdateCallbackURL.webp b/static/images/platgovsalesforce/installing_strongpoint/UpdateCallbackURL.webp
new file mode 100644
index 0000000000..d275ff419a
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/UpdateCallbackURL.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/config_stats_overview.webp b/static/images/platgovsalesforce/installing_strongpoint/config_stats_overview.webp
index bdc1edcf53..74a989f44b 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/config_stats_overview.webp and b/static/images/platgovsalesforce/installing_strongpoint/config_stats_overview.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/editassignments.webp b/static/images/platgovsalesforce/installing_strongpoint/editassignments.webp
index 9f8d91e1db..c2cee268aa 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/editassignments.webp and b/static/images/platgovsalesforce/installing_strongpoint/editassignments.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/enablepermissionsets.webp b/static/images/platgovsalesforce/installing_strongpoint/enablepermissionsets.webp
index 37f0f21422..73986882b6 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/enablepermissionsets.webp and b/static/images/platgovsalesforce/installing_strongpoint/enablepermissionsets.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/eula.webp b/static/images/platgovsalesforce/installing_strongpoint/eula.webp
new file mode 100644
index 0000000000..0554406f66
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/eula.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard10.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard10.webp
index 51367f6d3b..9ca16de958 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard10.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard10.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard11.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard11.webp
index 7d5f0d30bd..05db8b5019 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard11.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard11.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard2.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard2.webp
index 1c4de828f4..a67f432a20 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard2.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard2.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard3.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard3.webp
index 914c8c392a..7c38f76343 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard3.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard3.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5.webp
index 0f8842bcd2..3dc76df408 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5_scan.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5_scan.webp
index 49ccfdf6c6..099564cef3 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5_scan.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard5_scan.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard6.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard6.webp
index c1397ec66e..ed87b17654 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard6.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard6.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard8.webp b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard8.webp
index 5e2330aa35..821dfcc540 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard8.webp and b/static/images/platgovsalesforce/installing_strongpoint/getting_started_wizard8.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/governor.webp b/static/images/platgovsalesforce/installing_strongpoint/governor.webp
index 926dc908ad..fe8f86fe10 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/governor.webp and b/static/images/platgovsalesforce/installing_strongpoint/governor.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/input_auth_token.webp b/static/images/platgovsalesforce/installing_strongpoint/input_auth_token.webp
index 85704b809c..e92d7620c2 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/input_auth_token.webp and b/static/images/platgovsalesforce/installing_strongpoint/input_auth_token.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/install1.webp b/static/images/platgovsalesforce/installing_strongpoint/install1.webp
index 81127a631c..08bcc6f78f 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/install1.webp and b/static/images/platgovsalesforce/installing_strongpoint/install1.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials.webp b/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials.webp
index 23228724fd..bb042282b5 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials.webp and b/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials_new.webp b/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials_new.webp
index 4b31bc0828..bcc99b5c88 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials_new.webp and b/static/images/platgovsalesforce/installing_strongpoint/orgs_credentials_new.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/scanner.webp b/static/images/platgovsalesforce/installing_strongpoint/scanner.webp
index 7d22c478cf..88cd3a2102 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/scanner.webp and b/static/images/platgovsalesforce/installing_strongpoint/scanner.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/scanner_view.webp b/static/images/platgovsalesforce/installing_strongpoint/scanner_view.webp
index dc7eccd378..9f00a79abe 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/scanner_view.webp and b/static/images/platgovsalesforce/installing_strongpoint/scanner_view.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/scheduler_error_msg.webp b/static/images/platgovsalesforce/installing_strongpoint/scheduler_error_msg.webp
new file mode 100644
index 0000000000..7a77ed99b0
Binary files /dev/null and b/static/images/platgovsalesforce/installing_strongpoint/scheduler_error_msg.webp differ
diff --git a/static/images/platgovsalesforce/installing_strongpoint/statusreport.webp b/static/images/platgovsalesforce/installing_strongpoint/statusreport.webp
index 4c55712347..4bc28af95b 100644
Binary files a/static/images/platgovsalesforce/installing_strongpoint/statusreport.webp and b/static/images/platgovsalesforce/installing_strongpoint/statusreport.webp differ
diff --git a/static/images/platgovsalesforce/integrations/consumerKeyAndSecretExternalClientApp.webp b/static/images/platgovsalesforce/integrations/consumerKeyAndSecretExternalClientApp.webp
new file mode 100644
index 0000000000..caa172408e
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/consumerKeyAndSecretExternalClientApp.webp differ
diff --git a/static/images/platgovsalesforce/integrations/crMainView.webp b/static/images/platgovsalesforce/integrations/crMainView.webp
new file mode 100644
index 0000000000..a57c8bbf8a
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/crMainView.webp differ
diff --git a/static/images/platgovsalesforce/integrations/customizationListJiraRebrand.webp b/static/images/platgovsalesforce/integrations/customizationListJiraRebrand.webp
new file mode 100644
index 0000000000..410d16f43e
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/customizationListJiraRebrand.webp differ
diff --git a/static/images/platgovsalesforce/integrations/externalClientAppSearch.webp b/static/images/platgovsalesforce/integrations/externalClientAppSearch.webp
new file mode 100644
index 0000000000..79709b6df1
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/externalClientAppSearch.webp differ
diff --git a/static/images/platgovsalesforce/integrations/field_map_get_fields.webp b/static/images/platgovsalesforce/integrations/field_map_get_fields.webp
index 8b5f0e4caa..badce9ab61 100644
Binary files a/static/images/platgovsalesforce/integrations/field_map_get_fields.webp and b/static/images/platgovsalesforce/integrations/field_map_get_fields.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraConnectedAppView.webp b/static/images/platgovsalesforce/integrations/jiraConnectedAppView.webp
new file mode 100644
index 0000000000..96bd100a27
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraConnectedAppView.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraLoginUserViewRebrand.webp b/static/images/platgovsalesforce/integrations/jiraLoginUserViewRebrand.webp
new file mode 100644
index 0000000000..0ae4d73053
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraLoginUserViewRebrand.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraOpenCrLinkRebrand.webp b/static/images/platgovsalesforce/integrations/jiraOpenCrLinkRebrand.webp
new file mode 100644
index 0000000000..59d507532c
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraOpenCrLinkRebrand.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraRebrandAddCustomizations.webp b/static/images/platgovsalesforce/integrations/jiraRebrandAddCustomizations.webp
new file mode 100644
index 0000000000..4ccff87bbb
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraRebrandAddCustomizations.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraRebrandApprovedLink.webp b/static/images/platgovsalesforce/integrations/jiraRebrandApprovedLink.webp
new file mode 100644
index 0000000000..4fc2ff1dee
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraRebrandApprovedLink.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraRebrandFieldsCompleted.webp b/static/images/platgovsalesforce/integrations/jiraRebrandFieldsCompleted.webp
new file mode 100644
index 0000000000..61eefdd043
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraRebrandFieldsCompleted.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraRebrandLoginOptions.webp b/static/images/platgovsalesforce/integrations/jiraRebrandLoginOptions.webp
new file mode 100644
index 0000000000..459a08af85
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraRebrandLoginOptions.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jiraRebrandTabs.webp b/static/images/platgovsalesforce/integrations/jiraRebrandTabs.webp
new file mode 100644
index 0000000000..401f6c5166
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/jiraRebrandTabs.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jira_sp_credentials.webp b/static/images/platgovsalesforce/integrations/jira_sp_credentials.webp
index b90894ef79..6e3b9a210b 100644
Binary files a/static/images/platgovsalesforce/integrations/jira_sp_credentials.webp and b/static/images/platgovsalesforce/integrations/jira_sp_credentials.webp differ
diff --git a/static/images/platgovsalesforce/integrations/jira_status_settings.webp b/static/images/platgovsalesforce/integrations/jira_status_settings.webp
index 61c5493d80..b76296cd47 100644
Binary files a/static/images/platgovsalesforce/integrations/jira_status_settings.webp and b/static/images/platgovsalesforce/integrations/jira_status_settings.webp differ
diff --git a/static/images/platgovsalesforce/integrations/pendingApprovalLinkJiraRebrand.webp b/static/images/platgovsalesforce/integrations/pendingApprovalLinkJiraRebrand.webp
new file mode 100644
index 0000000000..31276048a9
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/pendingApprovalLinkJiraRebrand.webp differ
diff --git a/static/images/platgovsalesforce/integrations/proposedCustomizationsListJiraRebrand.webp b/static/images/platgovsalesforce/integrations/proposedCustomizationsListJiraRebrand.webp
new file mode 100644
index 0000000000..14a980278b
Binary files /dev/null and b/static/images/platgovsalesforce/integrations/proposedCustomizationsListJiraRebrand.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/1_See_integration_after_create_a_zendesk_ticket.webp b/static/images/platgovsalesforce/integrations/zendesk/1_See_integration_after_create_a_zendesk_ticket.webp
index 69f625c77c..0dd7c0660e 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/1_See_integration_after_create_a_zendesk_ticket.webp and b/static/images/platgovsalesforce/integrations/zendesk/1_See_integration_after_create_a_zendesk_ticket.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Customization.webp b/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Customization.webp
index 35d537677e..c3ae9b0029 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Customization.webp and b/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Customization.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Data_Record.webp b/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Data_Record.webp
index 0097c38f87..5910b795d2 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Data_Record.webp and b/static/images/platgovsalesforce/integrations/zendesk/Add_Proposed_Data_Record.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_Oauth.webp b/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_Oauth.webp
index 64c8d7f7bd..70c6236f8c 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_Oauth.webp and b/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_Oauth.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_configuration.webp b/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_configuration.webp
index 4765d9b02f..ac542d95af 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_configuration.webp and b/static/images/platgovsalesforce/integrations/zendesk/Admin_Panel_configuration.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/App_Change_Setting.webp b/static/images/platgovsalesforce/integrations/zendesk/App_Change_Setting.webp
index 8def4c2c22..24da661239 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/App_Change_Setting.webp and b/static/images/platgovsalesforce/integrations/zendesk/App_Change_Setting.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/App_Installed.webp b/static/images/platgovsalesforce/integrations/zendesk/App_Installed.webp
index 27882ee5e6..ecbcd3297f 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/App_Installed.webp and b/static/images/platgovsalesforce/integrations/zendesk/App_Installed.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/App_Setup.webp b/static/images/platgovsalesforce/integrations/zendesk/App_Setup.webp
index c876ab1d28..45e44d0bd4 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/App_Setup.webp and b/static/images/platgovsalesforce/integrations/zendesk/App_Setup.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Approval_Process_-_Push.webp b/static/images/platgovsalesforce/integrations/zendesk/Approval_Process_-_Push.webp
index 7b11b128b3..078bf8fd51 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Approval_Process_-_Push.webp and b/static/images/platgovsalesforce/integrations/zendesk/Approval_Process_-_Push.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_After_Complete.webp b/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_After_Complete.webp
index 954aef0db1..edbdb339ee 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_After_Complete.webp and b/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_After_Complete.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_Complete.webp b/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_Complete.webp
index 3d959c4fcf..6a75c39610 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_Complete.webp and b/static/images/platgovsalesforce/integrations/zendesk/Approval_process_-_Complete.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Approve_or_Reject.webp b/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Approve_or_Reject.webp
index 8c4be86eae..8ddf5b7b29 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Approve_or_Reject.webp and b/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Approve_or_Reject.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Request_Approval.webp b/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Request_Approval.webp
index 4d91533466..ab4e627f3a 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Request_Approval.webp and b/static/images/platgovsalesforce/integrations/zendesk/Approve_Process_-_Request_Approval.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Customization_Added.webp b/static/images/platgovsalesforce/integrations/zendesk/Customization_Added.webp
index bda6e524b0..f8830cea4d 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Customization_Added.webp and b/static/images/platgovsalesforce/integrations/zendesk/Customization_Added.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup.webp b/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup.webp
index ecbd7ef3e5..0121175724 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup.webp and b/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup_Result.webp b/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup_Result.webp
index 6d3c8615be..0e5e5b13c2 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup_Result.webp and b/static/images/platgovsalesforce/integrations/zendesk/Customization_Lookup_Result.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Record.webp b/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Record.webp
index 99137bc310..1f978eaabe 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Record.webp and b/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Record.webp differ
diff --git a/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Records_Result.webp b/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Records_Result.webp
index 8242f649b4..81c75800a9 100644
Binary files a/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Records_Result.webp and b/static/images/platgovsalesforce/integrations/zendesk/Lookup_Data_Records_Result.webp differ
diff --git a/static/images/platgovsalesforce/release_management/apex_enviro_comparison.webp b/static/images/platgovsalesforce/release_management/apex_enviro_comparison.webp
index da5c8f2c6b..ed38297409 100644
Binary files a/static/images/platgovsalesforce/release_management/apex_enviro_comparison.webp and b/static/images/platgovsalesforce/release_management/apex_enviro_comparison.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deploy.webp b/static/images/platgovsalesforce/release_management/deploy.webp
index f7465f8719..3e6a07c1ff 100644
Binary files a/static/images/platgovsalesforce/release_management/deploy.webp and b/static/images/platgovsalesforce/release_management/deploy.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deployment_log.webp b/static/images/platgovsalesforce/release_management/deployment_log.webp
index 77021e103b..89f7ae1047 100644
Binary files a/static/images/platgovsalesforce/release_management/deployment_log.webp and b/static/images/platgovsalesforce/release_management/deployment_log.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deployment_tool-2.webp b/static/images/platgovsalesforce/release_management/deployment_tool-2.webp
index 05dbab1d96..387e7d5794 100644
Binary files a/static/images/platgovsalesforce/release_management/deployment_tool-2.webp and b/static/images/platgovsalesforce/release_management/deployment_tool-2.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deployment_tool-3.webp b/static/images/platgovsalesforce/release_management/deployment_tool-3.webp
index 70683a04ea..bbb5f16d7e 100644
Binary files a/static/images/platgovsalesforce/release_management/deployment_tool-3.webp and b/static/images/platgovsalesforce/release_management/deployment_tool-3.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deployment_tool-4.webp b/static/images/platgovsalesforce/release_management/deployment_tool-4.webp
index 83e14e5495..5d13a5d17a 100644
Binary files a/static/images/platgovsalesforce/release_management/deployment_tool-4.webp and b/static/images/platgovsalesforce/release_management/deployment_tool-4.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deployment_tool-5.webp b/static/images/platgovsalesforce/release_management/deployment_tool-5.webp
index d2d10f800f..34c22a3488 100644
Binary files a/static/images/platgovsalesforce/release_management/deployment_tool-5.webp and b/static/images/platgovsalesforce/release_management/deployment_tool-5.webp differ
diff --git a/static/images/platgovsalesforce/release_management/deployment_tool.webp b/static/images/platgovsalesforce/release_management/deployment_tool.webp
index 2fbcbca918..d4fff44887 100644
Binary files a/static/images/platgovsalesforce/release_management/deployment_tool.webp and b/static/images/platgovsalesforce/release_management/deployment_tool.webp differ
diff --git a/static/images/platgovsalesforce/release_management/pullchangerequest.webp b/static/images/platgovsalesforce/release_management/pullchangerequest.webp
index 7c56d86a28..a218631eb9 100644
Binary files a/static/images/platgovsalesforce/release_management/pullchangerequest.webp and b/static/images/platgovsalesforce/release_management/pullchangerequest.webp differ
diff --git a/static/images/platgovsalesforce/release_management/pullcr.webp b/static/images/platgovsalesforce/release_management/pullcr.webp
index af7ee20b5a..38846af06a 100644
Binary files a/static/images/platgovsalesforce/release_management/pullcr.webp and b/static/images/platgovsalesforce/release_management/pullcr.webp differ
diff --git a/static/images/platgovsalesforce/release_management/push_pull_popup.webp b/static/images/platgovsalesforce/release_management/push_pull_popup.webp
index b96092b1e5..edcbfe9ac0 100644
Binary files a/static/images/platgovsalesforce/release_management/push_pull_popup.webp and b/static/images/platgovsalesforce/release_management/push_pull_popup.webp differ
diff --git a/static/images/platgovsalesforce/release_management/push_pull_sync_cr.webp b/static/images/platgovsalesforce/release_management/push_pull_sync_cr.webp
index c180f468ef..c49daaac91 100644
Binary files a/static/images/platgovsalesforce/release_management/push_pull_sync_cr.webp and b/static/images/platgovsalesforce/release_management/push_pull_sync_cr.webp differ
diff --git a/static/images/platgovsalesforce/release_management/push_pullcr-1.webp b/static/images/platgovsalesforce/release_management/push_pullcr-1.webp
index c1d3f4b5e1..cc24bf702f 100644
Binary files a/static/images/platgovsalesforce/release_management/push_pullcr-1.webp and b/static/images/platgovsalesforce/release_management/push_pullcr-1.webp differ
diff --git a/static/images/platgovsalesforce/release_management/pushcr.webp b/static/images/platgovsalesforce/release_management/pushcr.webp
index ccbf4639a0..efd2b8b354 100644
Binary files a/static/images/platgovsalesforce/release_management/pushcr.webp and b/static/images/platgovsalesforce/release_management/pushcr.webp differ
diff --git a/static/images/platgovsalesforce/release_management/rollback_button.webp b/static/images/platgovsalesforce/release_management/rollback_button.webp
index 616e894fa0..4eb76eec4d 100644
Binary files a/static/images/platgovsalesforce/release_management/rollback_button.webp and b/static/images/platgovsalesforce/release_management/rollback_button.webp differ
diff --git a/static/images/platgovsalesforce/release_management/rollback_confirmation.webp b/static/images/platgovsalesforce/release_management/rollback_confirmation.webp
index 4a843d304d..d2dd44e092 100644
Binary files a/static/images/platgovsalesforce/release_management/rollback_confirmation.webp and b/static/images/platgovsalesforce/release_management/rollback_confirmation.webp differ
diff --git a/static/images/platgovsalesforce/release_management/rollback_selected.webp b/static/images/platgovsalesforce/release_management/rollback_selected.webp
index 88f3cfd6d1..1ee0be013a 100644
Binary files a/static/images/platgovsalesforce/release_management/rollback_selected.webp and b/static/images/platgovsalesforce/release_management/rollback_selected.webp differ
diff --git a/static/images/platgovsalesforce/release_management/rollback_validation.webp b/static/images/platgovsalesforce/release_management/rollback_validation.webp
index a8a53fe7d8..26911da2b5 100644
Binary files a/static/images/platgovsalesforce/release_management/rollback_validation.webp and b/static/images/platgovsalesforce/release_management/rollback_validation.webp differ
diff --git a/static/images/platgovsalesforce/scanner_inactivity_alert/Config_Stats_Menu.webp b/static/images/platgovsalesforce/scanner_inactivity_alert/Config_Stats_Menu.webp
new file mode 100644
index 0000000000..2d60522ecb
Binary files /dev/null and b/static/images/platgovsalesforce/scanner_inactivity_alert/Config_Stats_Menu.webp differ
diff --git a/static/images/platgovsalesforce/scanner_inactivity_alert/Scanner_Inactivity_Alert.webp b/static/images/platgovsalesforce/scanner_inactivity_alert/Scanner_Inactivity_Alert.webp
new file mode 100644
index 0000000000..e93333034a
Binary files /dev/null and b/static/images/platgovsalesforce/scanner_inactivity_alert/Scanner_Inactivity_Alert.webp differ
diff --git a/static/images/platgovsalesforce/scanner_inactivity_alert/Scanner_Inactivity_Alert_Select.webp b/static/images/platgovsalesforce/scanner_inactivity_alert/Scanner_Inactivity_Alert_Select.webp
new file mode 100644
index 0000000000..8b0649253a
Binary files /dev/null and b/static/images/platgovsalesforce/scanner_inactivity_alert/Scanner_Inactivity_Alert_Select.webp differ
diff --git a/static/images/platgovsalesforce/scanners/daily_scan.webp b/static/images/platgovsalesforce/scanners/daily_scan.webp
index cc5efb0484..3693d6362d 100644
Binary files a/static/images/platgovsalesforce/scanners/daily_scan.webp and b/static/images/platgovsalesforce/scanners/daily_scan.webp differ
diff --git a/static/images/platgovsalesforce/scanners/field_level_scanner.webp b/static/images/platgovsalesforce/scanners/field_level_scanner.webp
index bf5bad0d06..4052085dd4 100644
Binary files a/static/images/platgovsalesforce/scanners/field_level_scanner.webp and b/static/images/platgovsalesforce/scanners/field_level_scanner.webp differ
diff --git a/static/images/platgovsalesforce/scanners/field_level_scanner_example.webp b/static/images/platgovsalesforce/scanners/field_level_scanner_example.webp
index 7613f7f7ee..16ea5fe6c0 100644
Binary files a/static/images/platgovsalesforce/scanners/field_level_scanner_example.webp and b/static/images/platgovsalesforce/scanners/field_level_scanner_example.webp differ
diff --git a/static/images/platgovsalesforce/scanners/field_level_scanner_remove.webp b/static/images/platgovsalesforce/scanners/field_level_scanner_remove.webp
index 7b5a045be9..8fbacccdf7 100644
Binary files a/static/images/platgovsalesforce/scanners/field_level_scanner_remove.webp and b/static/images/platgovsalesforce/scanners/field_level_scanner_remove.webp differ
diff --git a/static/images/platgovsalesforce/scanners/field_level_scanner_report.webp b/static/images/platgovsalesforce/scanners/field_level_scanner_report.webp
index 796c4070e7..0a65707e8e 100644
Binary files a/static/images/platgovsalesforce/scanners/field_level_scanner_report.webp and b/static/images/platgovsalesforce/scanners/field_level_scanner_report.webp differ
diff --git a/static/images/platgovsalesforce/settings/credentials_handler.webp b/static/images/platgovsalesforce/settings/credentials_handler.webp
index ab6b61d96e..cbb44a0cfa 100644
Binary files a/static/images/platgovsalesforce/settings/credentials_handler.webp and b/static/images/platgovsalesforce/settings/credentials_handler.webp differ
diff --git a/static/images/platgovsalesforce/settings/credentials_handler_edit.webp b/static/images/platgovsalesforce/settings/credentials_handler_edit.webp
index 4ea243b7d8..035dbf626a 100644
Binary files a/static/images/platgovsalesforce/settings/credentials_handler_edit.webp and b/static/images/platgovsalesforce/settings/credentials_handler_edit.webp differ
diff --git a/static/images/platgovsalesforce/settings/credentials_list.webp b/static/images/platgovsalesforce/settings/credentials_list.webp
index 8ba8291a5a..7d1a5bcd2b 100644
Binary files a/static/images/platgovsalesforce/settings/credentials_list.webp and b/static/images/platgovsalesforce/settings/credentials_list.webp differ
diff --git a/static/images/platgovsalesforce/sf_home_screen.webp b/static/images/platgovsalesforce/sf_home_screen.webp
index 629c9adcc8..d0c38fb2b2 100644
Binary files a/static/images/platgovsalesforce/sf_home_screen.webp and b/static/images/platgovsalesforce/sf_home_screen.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/All_Permissions.webp b/static/images/platgovsalesforce/sys_perm_tracking/All_Permissions.webp
new file mode 100644
index 0000000000..7f01a259d4
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/All_Permissions.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/ChangeLog_Part1.webp b/static/images/platgovsalesforce/sys_perm_tracking/ChangeLog_Part1.webp
new file mode 100644
index 0000000000..95de7066fd
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/ChangeLog_Part1.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/ChangeLog_Part2.webp b/static/images/platgovsalesforce/sys_perm_tracking/ChangeLog_Part2.webp
new file mode 100644
index 0000000000..d6bcae531d
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/ChangeLog_Part2.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Enable_Notifications.webp b/static/images/platgovsalesforce/sys_perm_tracking/Enable_Notifications.webp
new file mode 100644
index 0000000000..16a9db8556
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Enable_Notifications.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Enable_Scheduler.webp b/static/images/platgovsalesforce/sys_perm_tracking/Enable_Scheduler.webp
new file mode 100644
index 0000000000..71ba70dafa
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Enable_Scheduler.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Home_Notifications.webp b/static/images/platgovsalesforce/sys_perm_tracking/Home_Notifications.webp
new file mode 100644
index 0000000000..9f8400b591
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Home_Notifications.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Menu_Sys_Perm.webp b/static/images/platgovsalesforce/sys_perm_tracking/Menu_Sys_Perm.webp
new file mode 100644
index 0000000000..93a88a3a64
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Menu_Sys_Perm.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Recommended_Permissions.webp b/static/images/platgovsalesforce/sys_perm_tracking/Recommended_Permissions.webp
new file mode 100644
index 0000000000..a1c2c53ea6
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Recommended_Permissions.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Report_Opened_By_Notification.webp b/static/images/platgovsalesforce/sys_perm_tracking/Report_Opened_By_Notification.webp
new file mode 100644
index 0000000000..842c3ff634
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Report_Opened_By_Notification.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Report_Weekly.webp b/static/images/platgovsalesforce/sys_perm_tracking/Report_Weekly.webp
new file mode 100644
index 0000000000..ee0cb4d262
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Report_Weekly.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Selected_Permissions.webp b/static/images/platgovsalesforce/sys_perm_tracking/Selected_Permissions.webp
new file mode 100644
index 0000000000..e94aea9b12
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Selected_Permissions.webp differ
diff --git a/static/images/platgovsalesforce/sys_perm_tracking/Sys_Perm_Report.webp b/static/images/platgovsalesforce/sys_perm_tracking/Sys_Perm_Report.webp
new file mode 100644
index 0000000000..1390c63078
Binary files /dev/null and b/static/images/platgovsalesforce/sys_perm_tracking/Sys_Perm_Report.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/add_customization.webp b/static/images/platgovsalesforce/tech_debt/add_customization.webp
new file mode 100644
index 0000000000..2d7a556228
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/add_customization.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/add_customizations_to_change_request.webp b/static/images/platgovsalesforce/tech_debt/add_customizations_to_change_request.webp
new file mode 100644
index 0000000000..84794c2c83
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/add_customizations_to_change_request.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/add_customizations_to_change_request_2.webp b/static/images/platgovsalesforce/tech_debt/add_customizations_to_change_request_2.webp
new file mode 100644
index 0000000000..4ea8d31ce9
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/add_customizations_to_change_request_2.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/clean_up_unused_fields_change_request.webp b/static/images/platgovsalesforce/tech_debt/clean_up_unused_fields_change_request.webp
new file mode 100644
index 0000000000..7b70e8fe25
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/clean_up_unused_fields_change_request.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_finder_results.webp b/static/images/platgovsalesforce/tech_debt/customization_finder_results.webp
new file mode 100644
index 0000000000..1e613495d6
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_finder_results.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_actions.webp b/static/images/platgovsalesforce/tech_debt/customization_record_actions.webp
new file mode 100644
index 0000000000..4a4ef429b0
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_actions.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_change_enablement_tab.webp b/static/images/platgovsalesforce/tech_debt/customization_record_change_enablement_tab.webp
new file mode 100644
index 0000000000..9d0fb2f3f1
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_change_enablement_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_cleanup_tab.webp b/static/images/platgovsalesforce/tech_debt/customization_record_cleanup_tab.webp
new file mode 100644
index 0000000000..74a7574c2f
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_cleanup_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_custom_tab.webp b/static/images/platgovsalesforce/tech_debt/customization_record_custom_tab.webp
new file mode 100644
index 0000000000..dcc94f08d4
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_custom_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_drd_tab.webp b/static/images/platgovsalesforce/tech_debt/customization_record_drd_tab.webp
new file mode 100644
index 0000000000..bb0d310ff7
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_drd_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_header.webp b/static/images/platgovsalesforce/tech_debt/customization_record_header.webp
new file mode 100644
index 0000000000..a50feb913e
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_header.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_metadata_tab.webp b/static/images/platgovsalesforce/tech_debt/customization_record_metadata_tab.webp
new file mode 100644
index 0000000000..1833a472b9
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_metadata_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_related_objects.webp b/static/images/platgovsalesforce/tech_debt/customization_record_related_objects.webp
new file mode 100644
index 0000000000..e864ea6b3a
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_related_objects.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/customization_record_related_tab.webp b/static/images/platgovsalesforce/tech_debt/customization_record_related_tab.webp
new file mode 100644
index 0000000000..26eba5ff01
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/customization_record_related_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/impact_analysis_tabs_1.webp b/static/images/platgovsalesforce/tech_debt/impact_analysis_tabs_1.webp
new file mode 100644
index 0000000000..58ee6688e7
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/impact_analysis_tabs_1.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/impact_analysis_tabs_2.webp b/static/images/platgovsalesforce/tech_debt/impact_analysis_tabs_2.webp
new file mode 100644
index 0000000000..3705068635
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/impact_analysis_tabs_2.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/policy_related_tab.webp b/static/images/platgovsalesforce/tech_debt/policy_related_tab.webp
new file mode 100644
index 0000000000..487433acf6
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/policy_related_tab.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/policy_set_button.webp b/static/images/platgovsalesforce/tech_debt/policy_set_button.webp
index 511f1d18d2..af58aaf088 100644
Binary files a/static/images/platgovsalesforce/tech_debt/policy_set_button.webp and b/static/images/platgovsalesforce/tech_debt/policy_set_button.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/policy_set_customizations.webp b/static/images/platgovsalesforce/tech_debt/policy_set_customizations.webp
new file mode 100644
index 0000000000..7d0bc66387
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/policy_set_customizations.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/select_change_level_by_sf_type.webp b/static/images/platgovsalesforce/tech_debt/select_change_level_by_sf_type.webp
new file mode 100644
index 0000000000..fbbd22e48b
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/select_change_level_by_sf_type.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/select_customizations.webp b/static/images/platgovsalesforce/tech_debt/select_customizations.webp
new file mode 100644
index 0000000000..d914bf42f5
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/select_customizations.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/selected_customizations.webp b/static/images/platgovsalesforce/tech_debt/selected_customizations.webp
new file mode 100644
index 0000000000..51ded6f4b2
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/selected_customizations.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_1.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_1.webp
index ad60eb5af0..cbb810698b 100644
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_1.webp and b/static/images/platgovsalesforce/tech_debt/tech_debt_1.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_10.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_10.webp
index e95d835666..f15ecd9a56 100644
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_10.webp and b/static/images/platgovsalesforce/tech_debt/tech_debt_10.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_11.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_11.webp
index dfca9fd8b1..7c5cee7d34 100644
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_11.webp and b/static/images/platgovsalesforce/tech_debt/tech_debt_11.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_13.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_13.webp
index 2a4d8063c6..ac5ddda00c 100644
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_13.webp and b/static/images/platgovsalesforce/tech_debt/tech_debt_13.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_14.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_14.webp
new file mode 100644
index 0000000000..0e4e614d17
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/tech_debt_14.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_3.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_3.webp
deleted file mode 100644
index 7e4b69db1f..0000000000
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_3.webp and /dev/null differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_7.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_7.webp
index b043d881ea..bc4dd7a117 100644
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_7.webp and b/static/images/platgovsalesforce/tech_debt/tech_debt_7.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_8.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_8.webp
index dcdef8d2e5..e9d9e9a817 100644
Binary files a/static/images/platgovsalesforce/tech_debt/tech_debt_8.webp and b/static/images/platgovsalesforce/tech_debt/tech_debt_8.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_1.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_1.webp
new file mode 100644
index 0000000000..9637342392
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_1.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_2.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_2.webp
new file mode 100644
index 0000000000..e1b7f967fc
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_2.webp differ
diff --git a/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_3.webp b/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_3.webp
new file mode 100644
index 0000000000..b3f1765072
Binary files /dev/null and b/static/images/platgovsalesforce/tech_debt/tech_debt_default_policy_3.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assist_profile.webp b/static/images/platgovsalesforce/tools/access_assist_profile.webp
index 2e0f3f6d68..8898164938 100644
Binary files a/static/images/platgovsalesforce/tools/access_assist_profile.webp and b/static/images/platgovsalesforce/tools/access_assist_profile.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assist_profile2.webp b/static/images/platgovsalesforce/tools/access_assist_profile2.webp
index f51489e7d9..b9137dfbed 100644
Binary files a/static/images/platgovsalesforce/tools/access_assist_profile2.webp and b/static/images/platgovsalesforce/tools/access_assist_profile2.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assist_user.webp b/static/images/platgovsalesforce/tools/access_assist_user.webp
index 38cbd68411..71d04c52a1 100644
Binary files a/static/images/platgovsalesforce/tools/access_assist_user.webp and b/static/images/platgovsalesforce/tools/access_assist_user.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assist_user2.webp b/static/images/platgovsalesforce/tools/access_assist_user2.webp
index 0c1c72b57b..6aa6ab81fc 100644
Binary files a/static/images/platgovsalesforce/tools/access_assist_user2.webp and b/static/images/platgovsalesforce/tools/access_assist_user2.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assist_view_details_permission.webp b/static/images/platgovsalesforce/tools/access_assist_view_details_permission.webp
index a49820880a..873fe1f64d 100644
Binary files a/static/images/platgovsalesforce/tools/access_assist_view_details_permission.webp and b/static/images/platgovsalesforce/tools/access_assist_view_details_permission.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assist_view_details_users.webp b/static/images/platgovsalesforce/tools/access_assist_view_details_users.webp
index 5999366408..4384ca2280 100644
Binary files a/static/images/platgovsalesforce/tools/access_assist_view_details_users.webp and b/static/images/platgovsalesforce/tools/access_assist_view_details_users.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_assistance.webp b/static/images/platgovsalesforce/tools/access_assistance.webp
index cb27860fa4..e74012d1d4 100644
Binary files a/static/images/platgovsalesforce/tools/access_assistance.webp and b/static/images/platgovsalesforce/tools/access_assistance.webp differ
diff --git a/static/images/platgovsalesforce/tools/access_review_assistant.webp b/static/images/platgovsalesforce/tools/access_review_assistant.webp
index 7fc6b7a244..b7e5bce7c4 100644
Binary files a/static/images/platgovsalesforce/tools/access_review_assistant.webp and b/static/images/platgovsalesforce/tools/access_review_assistant.webp differ
diff --git a/static/images/platgovsalesforce/tools/automated_report_cleanup.webp b/static/images/platgovsalesforce/tools/automated_report_cleanup.webp
index c822b34e81..4c07954d8a 100644
Binary files a/static/images/platgovsalesforce/tools/automated_report_cleanup.webp and b/static/images/platgovsalesforce/tools/automated_report_cleanup.webp differ
diff --git a/static/images/platgovsalesforce/tools/automated_report_cleanup_2.webp b/static/images/platgovsalesforce/tools/automated_report_cleanup_2.webp
new file mode 100644
index 0000000000..9aa2ee2bf7
Binary files /dev/null and b/static/images/platgovsalesforce/tools/automated_report_cleanup_2.webp differ
diff --git a/static/images/platgovsalesforce/tools/automated_report_cleanup_preview.webp b/static/images/platgovsalesforce/tools/automated_report_cleanup_preview.webp
index 4fdab2b9f4..6ad0115898 100644
Binary files a/static/images/platgovsalesforce/tools/automated_report_cleanup_preview.webp and b/static/images/platgovsalesforce/tools/automated_report_cleanup_preview.webp differ
diff --git a/static/images/platgovsalesforce/tools/change_logs_clean_up.webp b/static/images/platgovsalesforce/tools/change_logs_clean_up.webp
index 4a02293260..96971a49e5 100644
Binary files a/static/images/platgovsalesforce/tools/change_logs_clean_up.webp and b/static/images/platgovsalesforce/tools/change_logs_clean_up.webp differ
diff --git a/static/images/platgovsalesforce/tools/entity_diagram_light.webp b/static/images/platgovsalesforce/tools/entity_diagram_light.webp
new file mode 100644
index 0000000000..fb98010573
Binary files /dev/null and b/static/images/platgovsalesforce/tools/entity_diagram_light.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object.webp b/static/images/platgovsalesforce/tools/export_object.webp
index 6c6f422a97..c09d75fc22 100644
Binary files a/static/images/platgovsalesforce/tools/export_object.webp and b/static/images/platgovsalesforce/tools/export_object.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_attach_record.webp b/static/images/platgovsalesforce/tools/export_object_attach_record.webp
index 12a05496d9..0c1d25e0db 100644
Binary files a/static/images/platgovsalesforce/tools/export_object_attach_record.webp and b/static/images/platgovsalesforce/tools/export_object_attach_record.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_attach_record_2.webp b/static/images/platgovsalesforce/tools/export_object_attach_record_2.webp
new file mode 100644
index 0000000000..a6cb1cdcf6
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_object_attach_record_2.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_attach_record_list.webp b/static/images/platgovsalesforce/tools/export_object_attach_record_list.webp
index 76d09fe144..9aea9a5c07 100644
Binary files a/static/images/platgovsalesforce/tools/export_object_attach_record_list.webp and b/static/images/platgovsalesforce/tools/export_object_attach_record_list.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_attach_record_tab_classic.webp b/static/images/platgovsalesforce/tools/export_object_attach_record_tab_classic.webp
index 58ba867f8d..b805ffed4d 100644
Binary files a/static/images/platgovsalesforce/tools/export_object_attach_record_tab_classic.webp and b/static/images/platgovsalesforce/tools/export_object_attach_record_tab_classic.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_attach_record_tab_lightning_add_items.webp b/static/images/platgovsalesforce/tools/export_object_attach_record_tab_lightning_add_items.webp
new file mode 100644
index 0000000000..045dfe9970
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_object_attach_record_tab_lightning_add_items.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_attach_record_tab_lightning_personalize.webp b/static/images/platgovsalesforce/tools/export_object_attach_record_tab_lightning_personalize.webp
new file mode 100644
index 0000000000..a8c0b041bb
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_object_attach_record_tab_lightning_personalize.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_filter.webp b/static/images/platgovsalesforce/tools/export_object_filter.webp
index d94181db9f..5512c98fb6 100644
Binary files a/static/images/platgovsalesforce/tools/export_object_filter.webp and b/static/images/platgovsalesforce/tools/export_object_filter.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_permissions.webp b/static/images/platgovsalesforce/tools/export_object_permissions.webp
index 0de400f7db..ad8634e658 100644
Binary files a/static/images/platgovsalesforce/tools/export_object_permissions.webp and b/static/images/platgovsalesforce/tools/export_object_permissions.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_object_profiles.webp b/static/images/platgovsalesforce/tools/export_object_profiles.webp
index 3f574fc2a8..074ea7112f 100644
Binary files a/static/images/platgovsalesforce/tools/export_object_profiles.webp and b/static/images/platgovsalesforce/tools/export_object_profiles.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_profile_sel_profile.webp b/static/images/platgovsalesforce/tools/export_profile_sel_profile.webp
new file mode 100644
index 0000000000..c2b03ab968
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_profile_sel_profile.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_profile_sel_ps.webp b/static/images/platgovsalesforce/tools/export_profile_sel_ps.webp
new file mode 100644
index 0000000000..cbaa18a05b
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_profile_sel_ps.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_profile_ui.webp b/static/images/platgovsalesforce/tools/export_profile_ui.webp
index 0562565b42..deffc0f6ef 100644
Binary files a/static/images/platgovsalesforce/tools/export_profile_ui.webp and b/static/images/platgovsalesforce/tools/export_profile_ui.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_profile_ui_settings.webp b/static/images/platgovsalesforce/tools/export_profile_ui_settings.webp
index e729650a98..863863a573 100644
Binary files a/static/images/platgovsalesforce/tools/export_profile_ui_settings.webp and b/static/images/platgovsalesforce/tools/export_profile_ui_settings.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_profiles_download.webp b/static/images/platgovsalesforce/tools/export_profiles_download.webp
new file mode 100644
index 0000000000..6fea6f3578
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_profiles_download.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_users.webp b/static/images/platgovsalesforce/tools/export_users.webp
index bbfcb258a5..0d971a122a 100644
Binary files a/static/images/platgovsalesforce/tools/export_users.webp and b/static/images/platgovsalesforce/tools/export_users.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_users_download.webp b/static/images/platgovsalesforce/tools/export_users_download.webp
new file mode 100644
index 0000000000..6adb8f6b1d
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_users_download.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_users_selection.webp b/static/images/platgovsalesforce/tools/export_users_selection.webp
new file mode 100644
index 0000000000..3849877afe
Binary files /dev/null and b/static/images/platgovsalesforce/tools/export_users_selection.webp differ
diff --git a/static/images/platgovsalesforce/tools/export_users_settings.webp b/static/images/platgovsalesforce/tools/export_users_settings.webp
index 1f83b32e26..a8e0954097 100644
Binary files a/static/images/platgovsalesforce/tools/export_users_settings.webp and b/static/images/platgovsalesforce/tools/export_users_settings.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_permission_changes_by_date_report_1.webp b/static/images/platgovsalesforce/tools/field_permission_changes_by_date_report_1.webp
new file mode 100644
index 0000000000..4ddf4b3f26
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_permission_changes_by_date_report_1.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_permission_changes_by_date_report_2.webp b/static/images/platgovsalesforce/tools/field_permission_changes_by_date_report_2.webp
new file mode 100644
index 0000000000..e3a36c2809
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_permission_changes_by_date_report_2.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_1.webp b/static/images/platgovsalesforce/tools/field_tracking_1.webp
new file mode 100644
index 0000000000..24eba18eba
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_1.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_10.webp b/static/images/platgovsalesforce/tools/field_tracking_10.webp
new file mode 100644
index 0000000000..5c50a474e2
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_10.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_11.webp b/static/images/platgovsalesforce/tools/field_tracking_11.webp
new file mode 100644
index 0000000000..071ba6a7ce
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_11.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_12.webp b/static/images/platgovsalesforce/tools/field_tracking_12.webp
new file mode 100644
index 0000000000..833e45b93d
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_12.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_13.webp b/static/images/platgovsalesforce/tools/field_tracking_13.webp
new file mode 100644
index 0000000000..978bce2723
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_13.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_14.webp b/static/images/platgovsalesforce/tools/field_tracking_14.webp
new file mode 100644
index 0000000000..e9835416f9
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_14.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_15.webp b/static/images/platgovsalesforce/tools/field_tracking_15.webp
new file mode 100644
index 0000000000..d8bad41b91
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_15.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_16.webp b/static/images/platgovsalesforce/tools/field_tracking_16.webp
new file mode 100644
index 0000000000..32386e21ef
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_16.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_17.webp b/static/images/platgovsalesforce/tools/field_tracking_17.webp
new file mode 100644
index 0000000000..a6b90825c4
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_17.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_2.webp b/static/images/platgovsalesforce/tools/field_tracking_2.webp
new file mode 100644
index 0000000000..3a849a517f
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_2.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_3.webp b/static/images/platgovsalesforce/tools/field_tracking_3.webp
new file mode 100644
index 0000000000..bc74e32436
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_3.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_4.webp b/static/images/platgovsalesforce/tools/field_tracking_4.webp
new file mode 100644
index 0000000000..e637171be5
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_4.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_5.webp b/static/images/platgovsalesforce/tools/field_tracking_5.webp
new file mode 100644
index 0000000000..108eb50dd9
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_5.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_6.webp b/static/images/platgovsalesforce/tools/field_tracking_6.webp
new file mode 100644
index 0000000000..30e65ca5ef
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_6.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_7.webp b/static/images/platgovsalesforce/tools/field_tracking_7.webp
new file mode 100644
index 0000000000..53f7450b1a
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_7.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_8.webp b/static/images/platgovsalesforce/tools/field_tracking_8.webp
new file mode 100644
index 0000000000..dfa1b8f88b
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_8.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_9.webp b/static/images/platgovsalesforce/tools/field_tracking_9.webp
new file mode 100644
index 0000000000..f2fd030660
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_9.webp differ
diff --git a/static/images/platgovsalesforce/tools/field_tracking_change_log_example.webp b/static/images/platgovsalesforce/tools/field_tracking_change_log_example.webp
new file mode 100644
index 0000000000..680ead7e8d
Binary files /dev/null and b/static/images/platgovsalesforce/tools/field_tracking_change_log_example.webp differ
diff --git a/static/images/platgovsalesforce/tools/finder.webp b/static/images/platgovsalesforce/tools/finder.webp
index 7c82f2c6a7..43a736044a 100644
Binary files a/static/images/platgovsalesforce/tools/finder.webp and b/static/images/platgovsalesforce/tools/finder.webp differ
diff --git a/static/images/platgovsalesforce/tools/monitored_fields_tracking_changes_report.webp b/static/images/platgovsalesforce/tools/monitored_fields_tracking_changes_report.webp
new file mode 100644
index 0000000000..5b7d10a340
Binary files /dev/null and b/static/images/platgovsalesforce/tools/monitored_fields_tracking_changes_report.webp differ
diff --git a/static/images/platgovsalesforce/tools/user_activity.webp b/static/images/platgovsalesforce/tools/user_activity.webp
index 4f2c03830b..1592cc96d3 100644
Binary files a/static/images/platgovsalesforce/tools/user_activity.webp and b/static/images/platgovsalesforce/tools/user_activity.webp differ