Dev

.github/CODEOWNERS

@@ -0,0 +1,154 @@
+# CODEOWNERS file for product team ownership
+# Teams have ownership over their product's documentation areas
+# Last matching pattern takes precedence
+
+# Global fallback - all files require review from a default team if no specific owner
+# Uncomment and specify a default team if desired
+# * @netwrix/docs-admin
+
+# Product-specific ownership
+# Each team owns their docs directory, sidebar files, static files, and images
+
+# 1Secure team
+docs/1secure/ @netwrix/1secure-docs
+sidebars/1secure.js @netwrix/1secure-docs
+static/files/1secure/ @netwrix/1secure-docs
+static/images/1secure/ @netwrix/1secure-docs
+
+# Access Analyzer team
+docs/accessanalyzer/ @netwrix/accessanalyzer-docs
+sidebars/accessanalyzer/ @netwrix/accessanalyzer-docs
+static/files/accessanalyzer/ @netwrix/accessanalyzer-docs
+static/images/accessanalyzer/ @netwrix/accessanalyzer-docs
+
+# Access Information Center team
+docs/accessinformationcenter/ @netwrix/accessinformationcenter-docs
+sidebars/accessinformationcenter/ @netwrix/accessinformationcenter-docs
+static/files/accessinformationcenter/ @netwrix/accessinformationcenter-docs
+static/images/accessinformationcenter/ @netwrix/accessinformationcenter-docs
+
+# Activity Monitor team
+docs/activitymonitor/ @netwrix/activitymonitor-docs
+sidebars/activitymonitor/ @netwrix/activitymonitor-docs
+static/files/activitymonitor/ @netwrix/activitymonitor-docs
+static/images/activitymonitor/ @netwrix/activitymonitor-docs
+
+# Auditor team
+docs/auditor/ @netwrix/auditor-docs
+sidebars/auditor/ @netwrix/auditor-docs
+static/files/auditor/ @netwrix/auditor-docs
+static/images/auditor/ @netwrix/auditor-docs
+
+# Change Tracker team
+docs/changetracker/ @netwrix/changetracker-docs
+sidebars/changetracker/ @netwrix/changetracker-docs
+static/files/changetracker/ @netwrix/changetracker-docs
+static/images/changetracker/ @netwrix/changetracker-docs
+
+# Data Classification team
+docs/dataclassification/ @netwrix/dataclassification-docs
+sidebars/dataclassification/ @netwrix/dataclassification-docs
+static/files/dataclassification/ @netwrix/dataclassification-docs
+static/images/dataclassification/ @netwrix/dataclassification-docs
+
+# Directory Manager team
+docs/directorymanager/ @netwrix/directorymanager-docs
+sidebars/directorymanager/ @netwrix/directorymanager-docs
+static/files/directorymanager/ @netwrix/directorymanager-docs
+static/images/directorymanager/ @netwrix/directorymanager-docs
+
+# Endpoint Policy Manager team
+docs/endpointpolicymanager/ @netwrix/endpointpolicymanager-docs
+sidebars/endpointpolicymanager.js @netwrix/endpointpolicymanager-docs
+static/files/endpointpolicymanager/ @netwrix/endpointpolicymanager-docs
+static/images/endpointpolicymanager/ @netwrix/endpointpolicymanager-docs
+
+# Endpoint Protector team
+docs/endpointprotector/ @netwrix/endpointprotector-docs
+sidebars/endpointprotector/ @netwrix/endpointprotector-docs
+static/files/endpointprotector/ @netwrix/endpointprotector-docs
+static/images/endpointprotector/ @netwrix/endpointprotector-docs
+
+# Identity Manager team
+docs/identitymanager/ @netwrix/identitymanager-docs
+sidebars/identitymanager/ @netwrix/identitymanager-docs
+static/files/identitymanager/ @netwrix/identitymanager-docs
+static/images/identitymanager/ @netwrix/identitymanager-docs
+
+# Password Policy Enforcer team
+docs/passwordpolicyenforcer/ @netwrix/passwordpolicyenforcer-docs
+sidebars/passwordpolicyenforcer/ @netwrix/passwordpolicyenforcer-docs
+static/files/passwordpolicyenforcer/ @netwrix/passwordpolicyenforcer-docs
+static/images/passwordpolicyenforcer/ @netwrix/passwordpolicyenforcer-docs
+
+# Password Reset team
+docs/passwordreset/ @netwrix/passwordreset-docs
+sidebars/passwordreset/ @netwrix/passwordreset-docs
+static/files/passwordreset/ @netwrix/passwordreset-docs
+static/images/passwordreset/ @netwrix/passwordreset-docs
+
+# Password Secure team
+docs/passwordsecure/ @netwrix/passwordsecure-docs
+sidebars/passwordsecure/ @netwrix/passwordsecure-docs
+static/files/passwordsecure/ @netwrix/passwordsecure-docs
+static/images/passwordsecure/ @netwrix/passwordsecure-docs
+
+# PingCastle team
+docs/pingcastle/ @netwrix/pingcastle-docs
+sidebars/pingcastle/ @netwrix/pingcastle-docs
+static/files/pingcastle/ @netwrix/pingcastle-docs
+static/images/pingcastle/ @netwrix/pingcastle-docs
+
+# Platform Governor NetSuite team
+docs/platgovnetsuite/ @netwrix/platgovnetsuite-docs
+sidebars/platgovnetsuite.js @netwrix/platgovnetsuite-docs
+static/files/platgovnetsuite/ @netwrix/platgovnetsuite-docs
+static/images/platgovnetsuite/ @netwrix/platgovnetsuite-docs
+
+# Platform Governor NetSuite Flashlight team
+docs/platgovnetsuiteflashlight/ @netwrix/platgovnetsuiteflashlight-docs
+sidebars/platgovnetsuiteflashlight.js @netwrix/platgovnetsuiteflashlight-docs
+static/files/platgovnetsuiteflashlight/ @netwrix/platgovnetsuiteflashlight-docs
+static/images/platgovnetsuiteflashlight/ @netwrix/platgovnetsuiteflashlight-docs
+
+# Platform Governor Salesforce team
+docs/platgovsalesforce/ @netwrix/platgovsalesforce-docs
+sidebars/platgovsalesforce.js @netwrix/platgovsalesforce-docs
+static/files/platgovsalesforce/ @netwrix/platgovsalesforce-docs
+static/images/platgovsalesforce/ @netwrix/platgovsalesforce-docs
+
+# Platform Governor Salesforce Flashlight team
+docs/platgovsalesforceflashlight/ @netwrix/platgovsalesforceflashlight-docs
+sidebars/platgovsalesforceflashlight.js @netwrix/platgovsalesforceflashlight-docs
+static/files/platgovsalesforceflashlight/ @netwrix/platgovsalesforceflashlight-docs
+static/images/platgovsalesforceflashlight/ @netwrix/platgovsalesforceflashlight-docs
+
+# Privilege Secure team
+docs/privilegesecure/ @netwrix/privilegesecure-docs
+sidebars/privilegesecure/ @netwrix/privilegesecure-docs
+static/files/privilegesecure/ @netwrix/privilegesecure-docs
+static/images/privilegesecure/ @netwrix/privilegesecure-docs
+
+# Privilege Secure Discovery team
+docs/privilegesecurediscovery/ @netwrix/privilegesecurediscovery-docs
+sidebars/privilegesecurediscovery.js @netwrix/privilegesecurediscovery-docs
+static/files/privilegesecurediscovery/ @netwrix/privilegesecurediscovery-docs
+static/images/privilegesecurediscovery/ @netwrix/privilegesecurediscovery-docs
+
+# Recovery for Active Directory team
+docs/recoveryforactivedirectory/ @netwrix/recoveryforactivedirectory-docs
+sidebars/recoveryforactivedirectory/ @netwrix/recoveryforactivedirectory-docs
+static/files/recoveryforactivedirectory/ @netwrix/recoveryforactivedirectory-docs
+static/images/recoveryforactivedirectory/ @netwrix/recoveryforactivedirectory-docs
+
+# Threat Manager team
+docs/threatmanager/ @netwrix/threatmanager-docs
+sidebars/threatmanager/ @netwrix/threatmanager-docs
+static/files/threatmanager/ @netwrix/threatmanager-docs
+static/images/threatmanager/ @netwrix/threatmanager-docs
+
+# Threat Prevention team
+docs/threatprevention/ @netwrix/threatprevention-docs
+sidebars/threatprevention/ @netwrix/threatprevention-docs
+static/files/threatprevention/ @netwrix/threatprevention-docs
+static/images/threatprevention/ @netwrix/threatprevention-docs

docs/platgovsalesforceflashlight/cleanup/cleanup_customizations.md

@@ -45,9 +45,9 @@ Use these processes to Clean up Individual Customization or Clean Up Multiple Cu
 
 5. Select fields to display:
 
-- **Clean Up Classification**
-- **Clean Up Comments**
-- **Clean Up Status**
+    - **Clean Up Classification**
+    - **Clean Up Comments**
+    - **Clean Up Status**
 
 ![createlist_view_for_cleanup_800x403](/images/platgovsalesforceflashlight/clean_up/createlist_view_for_cleanup_800x403.webp)6.
 Restrict Visibility. You can choose to have the list view:
@@ -59,11 +59,13 @@ Restrict Visibility. You can choose to have the list view:
 7. Click **Save**.
 8. Once your list view has been created, you can multi-select customizations for clean up by
    checking the box beside Action.
-   ![multi_select_cleanup_800x382](/images/platgovsalesforceflashlight/clean_up/multi_select_cleanup_800x382.webp)9.
-   You can now choose what you want to edit for the multiple customizations selected.
-    For example, if you want to change the clean up status:
-9. Go to **Edit Clean Up Status**.
-10. Select a status such as To Be Cleaned Up.
-11. Choose to **Apply changes to: All the selected records**.
-12. Click **Save**.
-    ![flagging_mass_customizations_800x374](/images/platgovsalesforceflashlight/clean_up/flagging_mass_customizations_800x374.webp)
+
+   ![multi_select_cleanup_800x382](/img/product_docs/platgovsalesforceflashlight/clean_up/multi_select_cleanup_800x382.webp)
+
+9. You can now choose what you want to edit for the multiple customizations selected. For example, if you want to change the clean up status:
+    1. Go to **Edit Clean Up Status**.
+    2. Select a status such as **To Be Cleaned Up**.
+    3. Choose to **Apply changes to: All the selected records**.
+    4. Click **Save**.
+
+    ![flagging_mass_customizations_800x374](/img/product_docs/platgovsalesforceflashlight/clean_up/flagging_mass_customizations_800x374.webp)

docs/platgovsalesforceflashlight/cleanup/cleanup_overview.md

@@ -10,8 +10,8 @@ Clean up involves some or all of the following steps:
 
 1. Identify and remove unused customizations (either individual or multiple):
 
-- Completely unused
-- Useless or inefficient
+    - Completely unused
+    - Useless or inefficient
 
 2. Identify and fix improperly set-up customizations (eg. no help text, inactive owner).
 3. Describe each object and its clean up task (under the improvements tab.)
@@ -29,8 +29,10 @@ follow the same steps:
 4. Manage the clean up as appropriate
 5. Run the scanner
 
-NOTE: Always check the Last Date Scanned on any object and re-scan that object if necessary to
+:::note
+Always check the Last Date Scanned on any object and re-scan that object if necessary to
 ensure the information about that object is up to date.
+:::
 
 ### Select the Approach
 
@@ -55,9 +57,11 @@ Strongpoint homepage under Strongpoint Features and Reports.
 You can clean up individual or multiple customizations by going to the Customization tab and
 selecting **Create New View**. Use the filters to generate your list.
 
-NOTE: Before moving on to other clean up activities, it is often a good idea to delete unused
+:::note
+Before moving on to other clean up activities, it is often a good idea to delete unused
 customizations that are highly likely safe to delete, such as fields that have not been used in
 years or that are not used by any other customization.
+:::
 
 ### Analyze and Organize the Results
 

docs/platgovsalesforceflashlight/cleanup/date_last_used.md

@@ -11,15 +11,11 @@ last date the Customization, or the data it contains, was created, changed, acce
 used.The DLU value indicates that the customization was used at least as late as the DLU. It does
 not indicate if it was used earlier. If DLU is blank, it indicates there in no verified date.
 
-> DLU CustomField Details
->
-> Setting the DLU Expiration
->
-> DLU Metadata Types
->
-> Excluded Metadata Extended Types
->
-> DLU Scheduler
+- DLU CustomField Details
+- Setting the DLU Expiration
+- DLU Metadata Types
+- Excluded Metadata Extended Types
+- DLU Scheduler
 
 ## DLU CustomField Details
 
@@ -29,8 +25,10 @@ make better decisions about the value of maintaining specific CustomFields. Usag
 - how often the field has data (_frequency_)
 - how recently the field has been used (_recency_)
 
-NOTE: DLU analysis should only be performed in Production orgs. Sandbox orgs do not reflect actual
+:::note
+DLU analysis should only be performed in Production orgs. Sandbox orgs do not reflect actual
 usage.
+:::
 
 Usage data fields:
 
@@ -48,18 +46,18 @@ Usage data fields:
   disabled. **CreatedDate** is more accurate for the CustomField than the **LastModifiedDate** for
   the record.
 - **DLU Status** displays the current status:
-   | DLU Status | DLU | Field History Tracking | Date DLU Analyzed | Parent Last Update Date | | ---
-  | --- | --- | --- | --- | | Unavailable | Blank | Never enabled for this field. | Blank |
-  Populated | | Pending | Blank | Enabled. Waiting for the scanner to run. | Blank | Populated | |
-  Current | Populated | Enabled. DLU is current and accurate using automated nightly scans. | Today
-  | Blank | | Recent | Populated, May be stale | Disabled. Last scan when enabled was within the
-  past three months. Three months is the default time period. See Setting the DLU Expiration. |
-  Within set time period | Populated | | Expired | Populated, May be stale | Disabled. Last scan
-  when enabled was longer than three months ago. Three months is the default time period. See
-  Setting the DLU Expiration. | Older than set time period | Populated | If Field History Tracking
-  is enabled for a CustomField with a **DLU Status** of either **Recent** or **Expired**, the status
-  is changed to **Pending**. Here is an example:
-  ![Example of the DLU status fields for a CustomField](/images/platgovsalesforceflashlight/clean_up/dlu_status_example_customfield_800x294.webp)
+
+| DLU Status | DLU | Field History Tracking | Date DLU Analyzed | Parent Last Update Date |
+| ---| --- | --- | --- | --- |
+| Unavailable | Blank | Never enabled for this field. | Blank | Populated |
+| Pending | Blank | Enabled. Waiting for the scanner to run. | Blank | Populated |
+| Current | Populated | Enabled. DLU is current and accurate using automated nightly scans. | Today | Blank |
+| Recent | Populated, May be stale | Disabled. Last scan when enabled was within the past three months. Three months is the default time period. See Setting the DLU Expiration. | Within set time period | Populated |
+| Expired | Populated, May be stale | Disabled. Last scan when enabled was longer than three months ago. Three months is the default time period. See Setting the DLU Expiration. | Older than set time period | Populated |
+
+If Field History Tracking is enabled for a CustomField with a **DLU Status** of either **Recent** or **Expired**, the status is changed to **Pending**. Here is an example:
+
+  ![Example of the DLU status fields for a CustomField](/img/product_docs/platgovsalesforceflashlight/clean_up/dlu_status_example_customfield_800x294.webp)
 
 ### Notes
 
@@ -97,7 +95,7 @@ DLU can be used for the following metadata types:
 | Salesforce Family Types & Joins                | Metadata Types                                                                                       | DLU                                                                                               |
 | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
 | Workflow                                       | Workflow Rule                                                                                        | Date workflow rule was last run.                                                                  |
-| Workflow Approva lProcess Flow Validation Rule | Last date base record updated, if enabled                                                            |                                                                                                   |
+| Workflow Approval Process Flow Validation Rule | Last date base record updated, if enabled                                                            |                                                                                                   |
 | Scripts                                        | Apex Class**\*** Apex Trigger**\*** Apex Component**\*** Lightning Component Lightning Web Component | The last date the code was triggered by any script based on the log of the last time it was run.  |
 | Forms                                          | Layout Compact Layout                                                                                | If assigned to a profile, it is the date the last record that belongs to the layout was updated . |
 | Apex Page**\***                                | The last date the page was accessed (the code was triggered).                                        |                                                                                                   |

docs/platgovsalesforceflashlight/cleanup/documented_metadata_types.md

@@ -4,7 +4,7 @@ description: "Documented Metadata Types"
 sidebar_position: 40
 ---
 
-You can view the documented Metadata by **Type** or by Category.
+You can view the documented Metadata by [Type](#metadata-by-type) or by [Category](#metadata-by-category).
 
 ## Metadata by Type
 

docs/platgovsalesforceflashlight/gettingstarted/config_and_stats.md

@@ -15,13 +15,10 @@ Click **Download PDF** to create a PDF file of the current status.
 
 The report is divided into these sections:
 
-> Scanner Status Overview
->
-> Documentation Stats
->
-> Scanner Logs
->
-> Scanner Additional Information
+- Scanner Status Overview
+- Documentation Stats
+- Scanner Logs
+- Scanner Additional Information
 
 ## Scanner Status Overview
 

docs/platgovsalesforceflashlight/gettingstarted/customizations_overview.md

@@ -31,12 +31,7 @@ script.![drd_800x155](/images/platgovsalesforceflashlight/customizations/drd_800
 
 These reports are available from **Flashlight** > **Reports / List Views** > **Customizations**.
 
-> **All Customizations**: This enables you to use Salesforce functionality to filter searches
-> quickly for specific customizations.
->
-> **Customization Impact**: This report shows your customizations and how they impact other objects.
->
-> **Permissions by Object**: This report displays **Permissions** grouped by **Object**.
->
-> **Object Permissions by Profile**: This report displays **Object Permissions** grouped by
-> **Profile**.
+- **All Customizations**: This enables you to use Salesforce functionality to filter searches quickly for specific customizations.
+- **Customization Impact**: This report shows your customizations and how they impact other objects.
+- **Permissions by Object**: This report displays **Permissions** grouped by **Object**.
+- **Object Permissions by Profile**: This report displays **Object Permissions** grouped by **Profile**.

docs/platgovsalesforceflashlight/gettingstarted/installing_flashlight.md

@@ -20,7 +20,9 @@ Strongpoint:
 4. Click **Install**
    ![Install Flashlight by Strongpoint](/images/platgovsalesforceflashlight/getting_started/install_flashlight1_800x399.webp)
 
-NOTE: Strongpoint installs in the background. An email notification is sent to you when the
+:::note
+Strongpoint installs in the background. An email notification is sent to you when the
 installation is complete.
+:::
 
 **Next Step:** [Using the Getting Started Wizard](/docs/platgovsalesforceflashlight/gettingstarted/using_getting_started_wizard.md)

docs/platgovsalesforceflashlight/gettingstarted/scheduler.md

@@ -12,7 +12,9 @@ Strongpoint's scheduler creates automated scans and documents the Field Usage an
 To use the scheduler tool:
 
 1. Open **Flashlight** > **Support** > **Scheduler**
-   ![scheduler](/images/platgovsalesforce/clean_up/scheduler.webp)2.
-   Toggle **Enabled**/**Disabled**by the category. Your selections are automatically saved.
-2. Select the **Frequency** , **Day** and **Time**. Your selections are automatically saved.
-3. Click any menu item to close the **Scheduler**.
+
+   ![scheduler](/img/product_docs/platgovsalesforce/clean_up/scheduler.webp)
+
+2. Toggle **Enabled**/**Disabled**by the category. Your selections are automatically saved.
+3. Select the **Frequency**, **Day** and **Time**. Your selections are automatically saved.
+4. Click any menu item to close the **Scheduler**.