docs: PRT final audit — Integrations

site/guide/_sidebar.yaml

@@ -46,7 +46,7 @@ website:
                 - guide/integrations/manage-secrets.qmd
                 - guide/integrations/configure-connections.qmd
                 - guide/integrations/implement-custom-integrations.qmd
-                - guide/integrations/link-external-models.qmd
+                - guide/integrations/link-external-records.qmd
                 - guide/mcp/connect-ai-assistants-via-mcp.qmd
                 - guide/integrations/configure-analytics-exports.qmd
                 - file: guide/integrations/integrations-examples.qmd

site/guide/attestation/_configure-attestations.qmd

@@ -37,7 +37,7 @@ c. Set the **[start date]{.smallcaps}** for the attestation period.
 
 d. Set the **[end date]{.smallcaps}** when the attestation period ends.
 
-e. Optional: Toggle **[email reminders]{.smallcaps}** to send reminders to Submitters, Reviewers, and Approvers:
+e. (Optional) Toggle **[email reminders]{.smallcaps}** to send reminders to Submitters, Reviewers, and Approvers:
 
    - **[days before end]{.smallcaps}** — How many days before the end date to send the reminder.
    - **[subject]{.smallcaps}** — The email subject line.
@@ -94,7 +94,7 @@ a. Under Inventory Scope, click **{{< fa plus >}} Add Rule** to add a filter con
 
 b. Click **Save**.
 
-c. Optional: Click **View Records** to preview which records match your filter criteria.
+c. (Optional) Click **View Records** to preview which records match your filter criteria.
 
 ::: {.embed-tip}
 ### How do I filter for groups? 
@@ -113,7 +113,7 @@ a. Under Relevant Attestation Fields, drag inventory record fields between colum
    - **Inventory Record Fields** — Available fields from the inventory
    - **Relevant Attestation Fields** — Selected fields to display in record snapshots
 
-b. Optional: Reorder the fields to change how they display in the attestation.
+b. (Optional) Reorder the fields to change how they display in the attestation.
 
 ### 5. Add questionnaire fields
 
@@ -150,7 +150,7 @@ c. Click **Add Field**.
 
 d. Repeat to add additional fields as needed.
 
-e. Optional: Reorder fields by dragging them to change the order in which they appear to submitters.
+e. (Optional) Reorder fields by dragging them to change the order in which they appear to submitters.
 
 Questionnaire fields are available immediately for new attestation instances. Submitters see structured inputs for each field, and responses are collected consistently across all submissions.
 
@@ -198,7 +198,7 @@ a. Under Relevant Attestation Fields, drag inventory record fields between colum
    - **Inventory Record Fields** — Available fields from the inventory
    - **Relevant Attestation Fields** — Selected fields to display in record snapshots
 
-a. Optional: Reorder the fields to change how they display in the attestation.
+a. (Optional) Reorder the fields to change how they display in the attestation.
 
 #### Add questionnaire fields
 

site/guide/attestation/manage-attestations.qmd

@@ -50,7 +50,7 @@ For testing purposes only, you can trigger the attestation process:
 
 3. Under **Attestation Periods**, hover over an attestation period.
 
-4. When **{{< fa ellipsis-vertical >}}** appears, select **{{< fa play >}} Start Now**.
+4. When the **{{< fa ellipsis-vertical >}}** menu appears, select **{{< fa play >}} Start Now**.
 
 5. Click **Confirm**.
 
@@ -64,7 +64,7 @@ After starting the schedule, attestation participants are notified via My Inbox
 
 3. Under **Attestation Periods**, hover over an attestation period.
 
-4. When **{{< fa ellipsis-vertical >}}** appears, select **{{< fa pencil >}} Edit**.
+4. When the **{{< fa ellipsis-vertical >}}** menu appears, select **{{< fa pencil >}} Edit**.
 
 5. Make your desired changes to the following:
 
@@ -88,7 +88,7 @@ This action cannot be undone. The history of previous attestation periods is una
 
 3. Under **Attestation Periods**, hover over an attestation period.
 
-4. When **{{< fa ellipsis-vertical >}}** appears, select [**{{< fa trash >}} Cancel Period**]{.red}.
+4. When the **{{< fa ellipsis-vertical >}}** menu appears, select [**{{< fa trash >}} Cancel Period**]{.red}.
 
 5. Click **Confirm** to cancel the period.
 
@@ -184,7 +184,7 @@ To manually complete an attestation period:
 
 3. Under **Attestation Periods**, hover over an active attestation period.
 
-4. When **{{< fa ellipsis-vertical >}}** appears, select **{{< fa check >}} Complete Period**.
+4. When the **{{< fa ellipsis-vertical >}}** menu appears, select **{{< fa check >}} Complete Period**.
 
 5. Click **Confirm**.
 
@@ -204,7 +204,7 @@ You cannot delete an attestation template if it has any active attestation perio
 
 3. Locate the template to delete and hover over it.
 
-4. When **{{< fa ellipsis-vertical >}}** appears, select [**{{< fa trash >}} Delete**]{.red}.
+4. When the **{{< fa ellipsis-vertical >}}** menu appears, select [**{{< fa trash >}} Delete**]{.red}.
 
 5. Click **Confirm** to delete the template.
 

site/guide/attestation/review-attestations.qmd

@@ -37,7 +37,7 @@ As a reviewer, you assess the submitter's attestation, including ownership, usag
    - **Validation Issues** — Shows open validation issues at the time of the snapshot.
    - **Artifacts** — Shows artifacts (findings) captured in the snapshot.
 
-4. Optional: Click **Activity** to review the attestation history:
+4. (Optional) Click **Activity** to review the attestation history:
 
    - Who completed the different status changes.
    - When the attestation status changed.

site/guide/attestation/working-with-attestations.qmd

@@ -20,21 +20,6 @@ listing:
 
 {{< include /guide/attestation/_attestations.qmd >}}
 
-::: {.attn}
-
-## Prerequisites
-
-- [x] {{< var link.login >}}
-- [x] Records registered in the inventory require attestation.[^1]
-- [x] If applicable, artifacts (findings) have been documented.[^2]
-- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
-   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
-   - [Submitter]{.bubble} — Stakeholder who submits attestation questionnaires
-   - [Reviewer]{.bubble} — Organizational role that reviews attestation questionnaires
-   - [Approver]{.bubble} — Organizational role that approves attestation questionnaires
-
-:::
-
 ## Key concepts
 
 {{< include /about/glossary/_attestation.qmd >}}
@@ -72,12 +57,12 @@ graph LR
         A["**Not Started**"] --> B["**In Progress**"]
         B --> C["**Ready for Review**"]
     end
-    
+
     subgraph Reviewer
         C --> D["**Reviewed**"]
         D -.-> B
     end
-    
+
     subgraph Approver
         D --> E["**Signed Off**"]
     end
@@ -109,7 +94,7 @@ If attestations were organized by owner alone, neither Emma nor Kam would have p
 This approach ensures 100% accountability per group, where Emma approves all Fraud records and Kam approves all KYC records. If Fraud has two co-leads (Emma and Andres), either can approve.
 :::
 
-## How do I create meaningful attestation questionnaires?
+### How do I create meaningful attestation questionnaires?
 
 Attestation questionnaires are typically used in risk management to confirm that key controls, governance processes and documentation requirements have been followed throughout a record's lifecycle. These questionnaires are part of a broader effort to ensure accountability and regulatory compliance.
 
@@ -131,15 +116,31 @@ Areas typically covered in the questionnaire:
 
 Work with your risk management team to create a template that accurately reflects your organization's attestation requirements.
 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] Records registered in the inventory require attestation.[^1]
+- [x] If applicable, artifacts (findings) have been documented.[^2]
+- [x] You are assigned a role with sufficient permissions to perform attestation tasks:[^3]
+   - [{{< fa hand >}} Customer Admin]{.bubble} — Sets up attestations
+   - [Submitter]{.bubble} — Stakeholder who submits attestation questionnaires
+   - [Reviewer]{.bubble} — Organizational role that reviews attestation questionnaires
+   - [Approver]{.bubble} — Organizational role that approves attestation questionnaires
+
+:::
+
 ## Manage attestations
 
 ::: {#attestation-listing}
 :::
 
+
 <!-- FOOTNOTES -->
 
 [^1]: [Register records in the inventory](/guide/inventory/register-records-in-inventory.qmd)
 
 [^2]: [Working with artifacts](/guide/validation/working-with-artifacts.qmd)
 
-[^3]: [Manage permissions](/guide/configuration/manage-permissions.qmd) 
+[^3]: [Manage permissions](/guide/configuration/manage-permissions.qmd)

site/guide/configuration/configure-google-private-service-connect.qmd

@@ -77,7 +77,7 @@ Create a private subnet in a supported GCP region that can be used to expose {{<
    c. Configure the IP address range to ensure it includes at least a `/28` of usable private IP address space.
    d. Click **Create**.
 
-2. Optional: Enable Private Google Access to provide access to Google APIs and services.[^2]
+2. (Optional) Enable Private Google Access to provide access to Google APIs and services.[^2]
 
 3. Provision two IP addresses in this subnet for later use: 
 

site/guide/configuration/customize-your-dashboard.qmd

@@ -28,9 +28,9 @@ Dashboards allow you to use widgets to quickly review and access information by
 
 1. In the left sidebar, click **{{< fa home >}} Dashboard**.
 
-2. Click **{{< fa plus>}} Add Dashboard**.
+2. Click **{{< fa plus >}} Add Dashboard**.
 
-3. On the Add New Dasboard modal that appears, enter the:
+3. On the Add New Dashboard modal that appears, enter the:
 
     - **[dashboard name]{.smallcaps}**
     - **[description]{.smallcaps}** (optional)
@@ -56,7 +56,7 @@ Deletion of dashboards is permanent.
 
 #### Edit dashboard details
 
-a. Select **{{< fa pencil >}} Details** to edit a **[dashboard name]{.smallcaps}**  or **[description]{.smallcaps}**.
+a. Select **{{< fa pencil >}} Details** to edit a **[dashboard name]{.smallcaps}** or **[description]{.smallcaps}**.
 
 b. Make your edits then click **Save Changes** to apply your adjustments.
 
@@ -99,11 +99,11 @@ Retrieve a list of the latest artifacts[^5] or recent activity.[^6]
 
 3. Click **{{< fa pencil >}} Edit Dashboard**.
 
-4.  Hover over the title of a widget until the **{{< fa hand>}}** appears.
+4. Hover over the title of a widget until the **{{< fa hand >}}** appears.
 
 5. Click and drag to position your widget as desired.
 
-    To resize a widget, hover over the bottom-right corner of a widget until the **{{< fa hand>}}** appears, then adjust the dimensions to your liking.
+    To resize a widget, hover over the bottom-right corner of a widget until the **{{< fa hand >}}** appears, then adjust the dimensions to your liking.
 
 6. Click **Done Editing** to exit the editor.
 
@@ -174,7 +174,7 @@ Removing a widget from a dashboard will not delete the linked view or analytics
 
 4. Hover over the widget you would like to remove.
 
-5. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select [**{{< fa trash-can >}} Remove**]{.red}.
+5. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select [**{{< fa trash-can >}} Remove**]{.red}.
 
 6. Click **Yes, Delete Widget** to confirm permanent deletion of the widget from that dashboard.
 

site/guide/configuration/manage-platform-notifications.qmd

@@ -63,7 +63,7 @@ To mark an individual update as read:
 
 a. Hover over the update you want to mark as read.
 
-b. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select **{{< fa envelope >}} Mark as Read**.
+b. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select **{{< fa envelope >}} Mark as Read**.
 
 To mark multiple updates as read:
 
@@ -79,7 +79,7 @@ To dismiss an individual update:
 
 a. Hover over the update you want to dismiss.
 
-b. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select **{{< fa bell-slash >}} Dismiss**.
+b. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select **{{< fa bell-slash >}} Dismiss**.
 
 To dismiss all updates:
 

site/guide/configuration/set-up-your-organization.qmd

@@ -39,7 +39,7 @@ This task involves managing organizations within {{< var vm.product >}}, allowin
 
 a. Hover over the business unit you want to rename.
 
-b. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select **{{< fa pencil >}} Edit Details** to rename the business unit.
+b. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select **{{< fa pencil >}} Edit Details** to rename the business unit.
 
 c. Click **Save** to apply your changes.
 
@@ -51,7 +51,7 @@ In order to delete a business unit, there must be no records attached to that un
 
 a. Hover over the business unit you want to delete.
 
-b. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select [**{{< fa trash-can >}} Delete Business Unit**]{.red} to remove the business unit.
+b. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select [**{{< fa trash-can >}} Delete Business Unit**]{.red} to remove the business unit.
 
 ::: {.callout-important}
 In order to delete a business unit, there must be no records attached to that unit.

site/guide/documentation/collaborate-with-others.qmd

@@ -94,7 +94,7 @@ b. Click on the version you would like to compare another version to.
 
 c. Hover over the other version to compare with your first version.
 
-d. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select **Compare against selected**.
+d. When the **{{< fa ellipsis-vertical >}}** menu appears, click on it and select **Compare against selected**.
 
 ### Rename a version
 

site/guide/documentation/working-with-documentation.qmd

@@ -39,18 +39,7 @@ After you upload initial documentation through the {{< var validmind.developer >
 
 This section describes how to work with Development type documents[^1] (for example, model documentation) in the {{< var validmind.platform >}}. Typically, you perform the tasks described here **after you have uploaded some initial documentation** with the {{< var validmind.developer >}}.
 
-[Learn more about the {{< var validmind.developer >}} {{< fa hand-point-right>}}](/developer/validmind-library.qmd){.button .button-green}
-:::
-
-::: {.attn}
-
-## Prerequisites
-
-- [x] {{< var link.login >}}
-- [x] The record you are documenting is registered in the inventory.[^2]
-- [x] You have provided some content for the documentation, either by uploading it through the {{< var vm.developer >}}[^3] or via the {{< var vm.platform >}}.
-- [x] You are a [{{< fa code >}} Developer]{.bubble} or assigned another role with sufficient permissions to perform the tasks in this guide.[^4]
-
+[Learn more about the {{< var validmind.developer >}} {{< fa hand-point-right >}}](/developer/validmind-library.qmd){.button .button-green}
 :::
 
 ## Key concepts
@@ -80,6 +69,17 @@ This section describes how to work with Development type documents[^1] (for exam
 
 ::::
 
+::: {.attn}
+
+## Prerequisites
+
+- [x] {{< var link.login >}}
+- [x] The record you are documenting is registered in the inventory.[^2]
+- [x] You have provided some content for the documentation, either by uploading it through the {{< var vm.developer >}}[^3] or via the {{< var vm.platform >}}.
+- [x] You are a [{{< fa code >}} Developer]{.bubble} or assigned another role with sufficient permissions to perform the tasks in this guide.[^4]
+
+:::
+
 ## Document Overview
 
 {{< include _document-overview.qmd >}}
@@ -106,12 +106,6 @@ Modify the contents of the **Latest** version of your document:[^6]
    b. Select **Save current revision** and enter a name.
    c. Click {{< fa check >}} to save the current revision.
 
-<!---
-## Troubleshooting
-
-[Include any common issues or errors that may arise during the task and how to resolve them.]
---->
-
 ## Prepare documentation
 
 Draft, edit, and refine your documentation, complete with supporting test results: