Merge pull request #99 from theopenlane/feat-tc

feat: add subprocessor embed docs, custom data

Author: golanglemonade

docs/docs/platform/basics/customdata/_category_.json

@@ -0,0 +1,9 @@
+{
+  "label": "Custom Data",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "description": "Manage custom data fields and configurations for your organization"
+  },
+  "collapsed": true
+}

docs/docs/platform/basics/customdata/customenums.mdx

@@ -0,0 +1,78 @@
+---
+title: Custom Enums
+description: Learn about custom enums in Openlane and how they can be used to extend and customize your compliance program
+sidebar_position: 1
+---
+
+# Custom Enums
+
+Custom Enums allow organizations to define structured dropdown values that shape how compliance data is categorized across Openlane.
+
+Located in Organization Settings → Custom Data → Custom Enums, this feature lets you tailor key object types such as environments, scopes, control kinds, risk categories, and more — without changing your core workflows.
+
+![Create Enum Screenshot](../../../../static/img/screenshots/customdata/custom_enums.png)
+
+## What Are Custom Enums?
+
+A Custom Enum is a predefined list of selectable values used throughout the platform to classify objects consistently.
+
+Unlike free-form fields, enums:
+- Ensure standardized categorization
+- Reduce inconsistent data entry
+- Enable filtering and reporting
+- Maintain audit-ready structure
+
+Each enum value can include:
+
+- Name
+- Description (optional)
+- Color
+
+## Global vs. Object-Specific Enums
+
+Some enums are global and can be used across multiple object types (e.g., Environments), while others are specific to certain objects (e.g., Control Kinds for controls). When creating custom enums, be mindful of where they will be applied to ensure they fit the intended use case.
+
+## System-Managed Enums
+
+In addition to organization-created enums, some categories include System-Managed Enums. These are common, standardized values provided by Openlane to help organizations get started quickly and align with widely used terminology.
+
+Key Characteristics
+
+1. Provided by Openlane
+1. Cannot be deleted
+1. Can be used like any other enum value
+1. Are not editable, but can be supplemented with custom values
+1. Designed to support common compliance patterns
+
+System-managed enums ensure consistency across organizations while still allowing flexibility through additional custom values.
+
+For example:
+
+- Default task kinds
+- Standard risk categories
+- Common document types for Trust Centers
+
+You are free to use system-managed values, ignore them, or supplement them with your own organization-specific enums.
+
+## How to Create a Custom Enum Value
+
+1. Navigate to Organization Settings → Custom Data → Custom Enums
+1. Select the enum category (e.g., Environments)
+1. Click Create Enum and provide the following details:
+   - **Name**: The name of the enum value (e.g., "Production", "High Risk", etc)
+   - **Description**: Optional additional context about the value
+   - **Color**: Choose a color to visually distinguish this value in dropdowns and reports
+1. Click Save to create the new enum value
+
+![Create Enum Screenshot](../../../../static/img/screenshots/customdata/create_enum.png)
+
+The new value will immediately become available in dropdowns across the platform.
+
+## How Custom Enums Differ from Custom Tags
+
+| Custom Tags                         | Custom Enums                        |
+| ----------------------------------- | ----------------------------------- |
+| Flexible, multi-select labels       | Structured dropdown categories      |
+| Used for lightweight classification | Used for core object structure      |
+| Free-form and optional              | Controlled, standardized values     |
+| Great for filtering                 | Critical for reporting + governance |

docs/docs/platform/basics/customdata/customtags.mdx

@@ -0,0 +1,59 @@
+---
+title: Custom Tags
+description: Learn about tags in Openlane and how they can be used to extend and customize your compliance program
+sidebar_position: 1
+---
+
+# Custom Tags
+
+Tags allow organizations to apply flexible, lightweight labels to objects across Openlane.
+
+Located in Organization Settings → Custom Data → Custom Tags, tags help teams organize, filter, and segment compliance data without changing core structure or workflows.
+
+Where Custom Enums create structure, Tags create flexibility.
+
+## What Are Custom Tags?
+
+A Custom Tag is a reusable label that can be applied to records such as controls, risks, tasks, policies, vendors, assets, and more.
+
+Tags are:
+- Multi-select
+- Optional
+- Organization-defined
+- Designed for filtering and segmentation
+
+Unlike enums, tags are not tied to strict object structure. They exist to help teams categorize information in ways that reflect how they operate.
+
+## Why Use Custom Tags?
+
+Custom Tags are ideal when:
+
+- You need temporary or evolving classifications
+- You want to group related items across object types
+- You need additional filtering in dashboards
+- You want to flag items for internal workflows
+
+Tags allow teams to adapt quickly without requiring governance changes.
+
+## How to Create a Custom Tag
+
+1. Navigate to Organization Settings → Custom Data → Custom Tags
+2. Click Create Tag and provide the following details:
+   - **Name**: The name of the tag (e.g., "High Priority", "Needs Review", etc)
+   - **Description**: Optional additional context about the tag
+   - **Aliases**: Alternative names for the same tag to ensure consistency and avoid duplicates
+   - **Color**: Choose a color to visually distinguish this tag in lists and filters
+3. Click Save to create the new tag
+
+The tag will become available across supported objects immediately.
+
+Tags can also be created on the fly when editing records, allowing for quick categorization without leaving the workflow.
+
+## How Custom Tags Differ from Custom Enums
+
+| Custom Tags                      | Custom Enums                  |
+| -------------------------------- | ----------------------------- |
+| Flexible, multi-select labels    | Structured dropdown values    |
+| Optional and lightweight         | Core object classification    |
+| Evolve easily over time          | Governed and standardized     |
+| Great for filtering and grouping | Power reporting and structure |

docs/docs/platform/trust-center/subprocessors.mdx

@@ -37,7 +37,11 @@ A subprocessor is any third-party that processes personal data for you:
 
 ## Adding Subprocessors
 
-You can add subprocessors from your existing vendor list or create new ones. For each subprocessor, include:
+From the [subprocessor management page](https://console.theopenlane.io/trust-center/subprocessors), you can manage your list of subprocessors.
+
+![Subprocessor Screenshot](../../../static/img/screenshots/trustcenter/subprocessors.png )
+
+You can add subprocessors from our existing vendor list or create new ones. For each subprocessor, include:
 
 - Name and description of what they do
 - Countries where data is processed
@@ -55,15 +59,45 @@ Categorize subprocessors so visitors can quickly understand what each vendor doe
 - **Support**: Customer support platforms
 - **Storage**: Data storage and backup services
 
+:::note
+ Need a category that doesn't exist? You can create custom categories to fit your specific vendor landscape using the [custom enums](https://console.theopenlane.io/organization-settings/custom-data?tab=enums) feature. Trust center subprcessor categories are based on the `Trust Center Subprocessor Kind` enum. Adding a new value to this enum will allow you to use that category when adding subprocessors. To read more about custom enums and how to use them, check out our documentation [here](https://docs.theopenlane.io/platform/basics/custom-data/custom-enums).
+:::
+
 ## Keeping the List Current
 
 Update your subprocessor list when you add or remove vendors that process customer data. Consider building this into your vendor onboarding process.
 
-You can export the list to CSV for external use.
-
 ## Best Practices
 
 - Include all vendors that process customer data, even indirectly
 - Provide clear descriptions of what each vendor does
 - Accurately list the countries where data is processed
 - Review the list periodically for accuracy
+
+## Embedding Subprocessor Information
+
+In order to better manage your subprocessors in one location, you can embed the subprocessor information directly into your privacy policy or other relevant documentation. This allows customers to easily access the information without navigating away from your site.
+
+From the [subprocessor management page](https://console.theopenlane.io/trust-center/subprocessors), you can generate an embed code that can be placed in your privacy policy. This ensures that the information is always up-to-date and easily accessible to your customers.
+
+![Embed Subprocessor Screenshot](../../../static/img/screenshots/trustcenter/subprocessors_embed.png)
+
+Example:
+
+```html
+<script src="https://trust.theopenlane.net/embed/subprocessors.js"
+  data-domain="trust.theopenlane.net/<org-slug>"
+  data-theme="auto"
+  defer>
+</script>
+```
+
+When implementing the embed code, keep the following in mind:
+
+1. If you use a strict CSP, allow scripts from: `trust.theopenlane.net`
+1. Updates may take up to 5 minutes to reflect due to caching
+1. Set data-theme to "light", "dark", or "auto" (default, follows OS preference).
+
+Subprocessors information will be automatically updated as your make changes, ensuring that your customers always have access to the most current information about your data processing practices.
+
+