tables + notes scripts update

Author: AdaOrdace

docs/privilegesecure/4.1/admin/audit&reporting/accesscertification/entitlements.md

@@ -23,8 +23,11 @@ The Entitlements table has the following features:
         - Approved – Existing access is approved
         - Denied – Access is removed for that specific user/resource/permission
 
-            **NOTE:** The user is not removed from the access policy. Instead, a 'deny flag' is set
+            :::note
+            The user is not removed from the access policy. Instead, a 'deny flag' is set
             against that attribute so that it can be re-enabled in the future.
+            :::
+
 
     - User Name – Displays the name of the account
     - Resource – Name of the resource
@@ -69,8 +72,11 @@ The Review Activity Details window has the following features:
         - Approved – Existing access is approved
         - Denied – Access is removed for that specific user/resource/permission
 
-            **NOTE:** The user is not removed from the access policy. Instead, a 'deny flag' is set
+            :::note
+            The user is not removed from the access policy. Instead, a 'deny flag' is set
             against that attribute so that it can be re-enabled in the future.
+            :::
+
 
     - Name – Displays the name of the account
     - Resource – Name of the resource
@@ -86,19 +92,28 @@ The Review Activity Details window has the following features:
 
 **Step 5 –** To remove access, select the applicable row(s) and click Deny.
 
-**NOTE:** The user is not removed from the access policy. Instead, a 'deny flag' is set against that
+:::note
+The user is not removed from the access policy. Instead, a 'deny flag' is set against that
 attribute so that it can be re-enabled in the future.
+:::
+
 
 **Step 6 –** When the entitlements have been reviewed, click Close. Changes are saved to the
 selected access certification task and shown on the
 [Entitlements Tab for Access Certification](/docs/privilegesecure/4.1/admin/audit&reporting/accesscertification/entitlements.md).
 
-**NOTE:** It is not necessary to review all entitlements at once. Changes are automatically saved to
+:::note
+It is not necessary to review all entitlements at once. Changes are automatically saved to
 the selected access certification task and can be returned to at any time (the Status will show as
 Incomplete).
+:::
 
-**CAUTION:** Committed changes cannot be undone. A new access certification task must be created.
+
+:::warning
+Committed changes cannot be undone. A new access certification task must be created.
 Alternatively, it is possible to manually reassign users to an access policy.
+:::
+
 
 **Step 7 –** When all entitlements have been reviewed, the Commit button is enabled. Click Commit to
 save the changes to user access.

docs/privilegesecure/4.1/admin/audit&reporting/accesscertification/users.md

@@ -31,7 +31,10 @@ The Users table has the following features:
 
 Follow the steps to add users and groups to the access certification task.
 
-**NOTE:** It is not possible to add or remove users after they have been added.
+:::note
+It is not possible to add or remove users after they have been added.
+:::
+
 
 **Step 1 –** Navigate to the Audit and Reporting > Access Certification page.
 
@@ -64,8 +67,11 @@ Users/Groups table and it is immediately moved to the Users & Groups to Add tabl
 **Step 6 –** (Optional) Click a row in the Users & Groups to Add table to move it back to the
 Available Users/Groups table.
 
-**CAUTION:** It is not possible to add or remove users after they have been added to the access
+:::warning
+It is not possible to add or remove users after they have been added to the access
 certification task.
+:::
+
 
 **Step 7 –** Click Add to add the selected user(s) or group(s).
 
@@ -74,8 +80,11 @@ The new user(s) and group(s) are added to the certification task and are shown o
 
 **Step 8 –** Click Close to return to the Access Certification page.
 
-**NOTE:** Only the assigned reviewer can interact with the entitlements once the access
+:::note
+Only the assigned reviewer can interact with the entitlements once the access
 certification task is created.
+:::
+
 
 The reviewer can now log in to see the access certification task(s) assigned to them and begin the
 review process. See the

docs/privilegesecure/4.1/admin/audit&reporting/logfiles/logfileoptions.md

@@ -32,8 +32,11 @@ The right of the page shows details of the selected service and has the followin
 
     - Verbose – Extremely detailed logging
 
-        **NOTE:** There are not many Verbose log messages in Privilege Secure so the difference
+        :::note
+        There are not many Verbose log messages in Privilege Secure so the difference
         between Verbose and Debug is minimal.
+        :::
+
 
     - Debug – More information for detailed analysis of system behavior. Customer support may ask
       for logs with this log level enabled for troubleshooting purposes

docs/privilegesecure/4.1/admin/audit&reporting/reporting.md

@@ -134,8 +134,11 @@ following attributes for a given user account:
 - Name
 - Privilege
 
-**NOTE:** The Subscriptions tab will not be enabled until saving the report. See the
+:::note
+The Subscriptions tab will not be enabled until saving the report. See the
 [Subscriptions Tab](#subscriptions-tab) topic for additional information.
+:::
+
 
 ## Customize an Existing Report
 

docs/privilegesecure/4.1/admin/configurationinterface/authentication/authenticationconnector.md

@@ -20,8 +20,11 @@ Follow the steps to add an authentication connector to the console.
 - Connector Description (Optional) – Enter a brief description to identify the service account
 - Connection Type – Indicates the type of authentication
 
-**NOTE:** Once the Connection Type is selected, additional fields become available. The available
+:::note
+Once the Connection Type is selected, additional fields become available. The available
 fields will change depending on the selection.
+:::
+
 
 **Step 4 –** Enter the information from the applicable authentication connector provider. See the
 [Authentication Page](/docs/privilegesecure/4.1/admin/configurationinterface/authentication/authentication.md)

docs/privilegesecure/4.1/admin/configurationinterface/authentication/openidconnectconfiguration/openidconnectauthentication.md

@@ -15,8 +15,11 @@ The following sections provide configuration information to use OpenID with an O
 In order to use the OpenID login functionality with Privilege Secure an Okta user must match a user
 in an AD domain that Privilege Secure is aware of.
 
-**NOTE:** The user will also need to be given access to Privilege Secure by assigning them a role
+:::note
+The user will also need to be given access to Privilege Secure by assigning them a role
 from the Config->Role Management screen.
+:::
+
 
 To create a new user click the Directory menu item and select People from the drop-down. You should
 see this screen.
@@ -39,8 +42,11 @@ Username will be matched against – under the Login Format dropdown:
 - User Principal Name
 - Email Address
 
-**NOTE:** Okta doesn’t allow sAMAccountName to be used as the Username so we can’t use that one
+:::note
+Okta doesn’t allow sAMAccountName to be used as the Username so we can’t use that one
 here.
+:::
+
 
 Users in sbpam.local are all set up with both UPN and Email Address – but they’re not the same.
 

docs/privilegesecure/4.1/admin/configurationinterface/authentication/openidconnectconfiguration/openidconnectconfiguration.md

@@ -46,8 +46,11 @@ Follow the steps to verify the OpenID Connect configuration:
 
     [protocol]//[hostname]:[port]
 
-**CAUTION:** In the next step, verify that the Sign In page displays as expected, but do NOT sign in
+:::warning
+In the next step, verify that the Sign In page displays as expected, but do NOT sign in
 at this step.
+:::
+
 
 **Step 4 –** Click Test Connection to verify the connection configuration. This opens the Sign In
 page in the browser. Do not sign in.
@@ -111,9 +114,12 @@ from the provider and will vary:
   the previous step. This represents the format of the value that will be used to sign in to the MFA
   during log in.
 
-    **NOTE:** These are not the credentials that will be used during the login process; only an
+    :::note
+    These are not the credentials that will be used during the login process; only an
     example of the format of those credentials. The actual credentials used are unique to each user
     and are setup during the MFA registration process for that user.
+    :::
+
 
 **Step 11 –** Select a field to use for the User Id Field and click Select.
 

docs/privilegesecure/4.1/admin/configurationinterface/authentication/samlconfiguration.md

@@ -46,8 +46,11 @@ Follow the steps to verify the SAML configuration:
 
     [protocol]//[hostname]:[port]
 
-**CAUTION:** In the next step, verify that the Sign In page displays as expected, but do NOT sign in
+:::warning
+In the next step, verify that the Sign In page displays as expected, but do NOT sign in
 at this step.
+:::
+
 
 **Step 4 –** Click Test Connection to verify the connection configuration. This opens the Sign In
 page in the browser. Do NOT sign in.
@@ -105,9 +108,12 @@ from the provider and will vary:
   the previous step. This represents the format of the value that will be used to sign in to the MFA
   during log in.
 
-    **NOTE:** These are not the credentials that will be used during the login process; only an
+    :::note
+    These are not the credentials that will be used during the login process; only an
     example of the format of those credentials. The actual credentials used are unique to each user
     and are setup during the MFA registration process for that user.
+    :::
+
 
 **Step 11 –** Select a field to use for the User Id Field and click Select.
 

docs/privilegesecure/4.1/admin/configurationinterface/integrationconnectors/integrationaccessgovernance.md

@@ -45,8 +45,11 @@ Select Tables and click Add to open the Select Database Objects window.
     - SA_ADInventory_ComputersView
     - SA ADInventory_UsersView
 
-    **NOTE:** Type in the Filter Objects by Name box to filter the list of objects by the characters
+    :::note
+    Type in the Filter Objects by Name box to filter the list of objects by the characters
     entered.
+    :::
+
 
 **Step 5 –** Click OK to return to the Application Access page.
 
@@ -67,7 +70,10 @@ app token:
 
 **Step 8 –** Click Finish to close the wizard and click Save in the Access view accept the changes.
 
-**NOTE:** Audit must be restarted after a new access role is configured.
+:::note
+Audit must be restarted after a new access role is configured.
+:::
+
 
 The next step is to use the Client ID and Client Secret to obtain an access token. This token is
 used to get data from the Enterprise Auditor endpoint.
@@ -153,8 +159,11 @@ To view the import progress, navigate to **Service Nodes** > Action Services. Se
 [Action Service](/docs/privilegesecure/4.1/admin/configurationinterface/servicenodes/servicenodes/action.md)
 topic for additional information.
 
-**NOTE:** The Use Secure Tunnel feature is enabled by default on all proxy services when installed
+:::note
+The Use Secure Tunnel feature is enabled by default on all proxy services when installed
 and the proxy service is selected by default.
+:::
+
 
 Refer to the
 [Action Service](/docs/privilegesecure/4.1/admin/configurationinterface/servicenodes/servicenodes/action.md)

docs/privilegesecure/4.1/admin/configurationinterface/integrationconnectors/integrationbyov/byovconnectorconfig.md

@@ -21,8 +21,11 @@ Begin by setting up an Integration Connector for using Netwrix Privilege Secure
 Ensure that the account you wish to use for your activity is managed by Privilege Secure or is
 contained within a Secret Vault resource in Privilege Secure.
 
-**NOTE:** For managed accounts, ensure that the account has been rotated at least once since being
+:::note
+For managed accounts, ensure that the account has been rotated at least once since being
 managed. Otherwise, there will be no vaulted password in the Netwrix Privilege Secure database.
+:::
+
 
 ### Configure the Activity Connector
 
@@ -192,7 +195,10 @@ next to the account name.
 **Step 3 –** Click on the **Manage** button that becomes available above the list, and select
 **Manual**.
 
-**NOTE:** Ensure the user is not already managed or added into Privilege Secure.
+:::note
+Ensure the user is not already managed or added into Privilege Secure.
+:::
+
 
 See the
 [Credentials Dashboard](/docs/privilegesecure/4.1/admin/dashboard/credentials.md)
@@ -217,8 +223,11 @@ account.
 
 **Step 3 –** Enter a password to match the AD password, then click **Save**.
 
-**NOTE:** For versions before Privilege Secure 4.1, a support ticket will be needed as the Set
+:::note
+For versions before Privilege Secure 4.1, a support ticket will be needed as the Set
 Password feature is not available.
+:::
+
 
 See the
 [Manage Internal Service Accounts](/docs/privilegesecure/4.1/admin/interface/credentials/manageinternalserviceaccount.md)
@@ -246,16 +255,22 @@ Follow the steps to create an activity.
 - Vault Connector — Displays a list of previously configured vault connectors. Select the vault
   connector created from the steps above.
 
-**NOTE:** You may use accounts stored in a Vault and added as a resource once the integration is
+:::note
+You may use accounts stored in a Vault and added as a resource once the integration is
 created. Also, you may apply domain or other local accounts managed by Netwrix Privilege Secure, but
 the password must be rotated once prior to use with an activity.
+:::
+
 
 ![BYOV create an Activity](/img/product_docs/privilegesecure/4.1/accessmanagement/admin/configuration/add/byovconnectoractivity.webp)
 
 **Step 4 –** Click Save to create the Activity.
 
-**NOTE:** Ensure the Login Account Template uses the format DOMAIN\samAccountName (e.g.,
+:::note
+Ensure the Login Account Template uses the format DOMAIN\samAccountName (e.g.,
 NWXTECH\dgrayson).
+:::
+
 
 See the
 [Add Activity](/docs/privilegesecure/4.1/admin/interface/activities/activity/activity.md)
@@ -303,5 +318,7 @@ management.
 
 ![My Activities BYOV Connector](/img/product_docs/privilegesecure/4.1/accessmanagement/admin/configuration/add/byovconnectormyactivities.webp)
 
-_Remember,_ Always verify configurations and permissions, especially when integrating with systems
+:::tip
+Remember, Always verify configurations and permissions, especially when integrating with systems
 like AD and using specific user accounts for critical operations.
+:::