> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.brainframe.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Document Bundles

# 📦 **Document Bundles**  
> **"Group once. Link everywhere."**  
> *Create reusable collections of documents and attach them instantly to any record—suppliers, risks, controls, and more.*  

---

## 1️⃣ Why Use Document Bundles?  
When managing compliance, you rarely deal with a single document in isolation. A new supplier relationship triggers a checklist of policies. An audit requires a consistent set of evidence. A risk brings along a set of related controls.

**Document Bundles** let you pre-group related documents so you can link them all at once, instead of attaching files one by one every time.

By using bundles, you ensure that:  
1. Related documents are always **grouped consistently** — no more forgetting a policy.  
2. Onboarding and compliance workflows move **faster**, with one click instead of many.  
3. Your records stay **clean and auditable** — every link is intentional and traceable.  

| 📌 Document Bundles are managed in the worskpace settings.

---

## 2️⃣ What's a Document Bundle?

A **Document Bundle** is a named collection of documents that belong together for a specific purpose. Bundles are reusable: create them once, then link them to as many records as needed.

Some common examples:  
* **Vendor controls** — data handling, contractual agreements, screening procedures  
* **Confidential data controls** — access reviews, MFA, encryption key management  
* **SaaS controls** — penetration testing, code of conduct, security architecture  
* **Induction package** — HR policies, code of conduct, IT security baseline  

💡 *Think of a bundle as a template for the set of documents that always apply together.*

---

## 3️⃣ Creating a Bundle

### ① Open Document Bundles settings 
* Navigate to the **Workspace settings.** 
* Select **Document Bundles**.  
* Click **+ Add** to create a new one.

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-06-02-at-15335_2d61xj.png)

### ② Name your Bundle  
Give the bundle a clear, descriptive title that reflects what it covers — for example, *Vendor controls* or *Confidential Data controls*.

### ③ Add Documents  
Attach the relevant documents to the bundle. These can be any files already in your workspace:  
* Word, Excel, PowerPoint files  
* PDFs  
* Website snapshots or video captures  

Once saved, the bundle appears in the list alongside its linked documents.

| Important: Once you have a bundle set up, you can go into any document type configuration, and enable the bundle to automatically be applied to all document of this type.

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-06-02-at-15474_196g5at.png)
---

## 4️⃣ Linking a Bundle to a Record

The real power of bundles shows up when you link them. Instead of manually attaching documents one by one, you link an entire bundle to a record — and all its documents come along.

Bundles can be linked to:  
* **Suppliers** — attach all vendor-related controls the moment you onboard a new partner  
* **Risks** — connect every relevant policy or procedure directly to a risk record  
* **Controls** — reference the underlying evidence documents from the control itself  
* **Any other document**

**To link a bundle:**  
1. Open the document.  
2. Navigate to the "Linked Document" tab.
3. Click on "Edit Document Bundles".  
4. Select the bundle(s) you want to attach.

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/button_vw5u2f.png =1009xauto)

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/dialog_3sv8ph.png =331xauto)
![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/tab_5n1m4u.png)

All documents within the bundle become visible directly in the linked documents.

| 📌 You can link multiple bundles to a single record — for example, a supplier might need both *Vendor controls* and *Confidential Data controls*.

---

## 5️⃣ A Practical Example: Supplier Onboarding

When you onboard a new supplier, there's a standard set of documents every vendor relationship should be backed by — data handling requirements, contractual agreements, employee screening procedures, and more.

Without bundles, you'd attach each of those documents manually to every new supplier. With bundles, the process looks like this:

1. Create a **Vendor controls** bundle once, containing all relevant documents.  
2. When a new supplier is added, link the **Vendor controls** bundle to their record.  
3. Every document in the bundle is now accessible directly from the supplier — consistently, every time.

| This also makes audits easier: when an auditor asks for evidence of your vendor controls, every supplier record already has the full set attached.

---

## 6️⃣ Managing Bundles Over Time

Bundles are living collections — you can update them as your document library evolves.

* **Adding a document** to a bundle automatically makes it available on every record the bundle is linked to. 
* **Removing a document** from a bundle unlinks it from those records, but does not delete the original file.  
* **Renaming or editing** a bundle has no impact on the linked records — only the bundle's contents matter.

---

## 7️⃣ Best Practices  
* 📌 Create bundles **by theme** — one per domain (vendor, security, HR) rather than one giant bundle.  
* 💡 Review bundle contents **periodically** to make sure documents are current and complete.  
* 🔗 Link bundles **early** in any onboarding or risk workflow — don't wait until an audit is due.  

---

### **🎯 Visual Checklist**  
* [x] Bundle created with a clear name  
* [x] Relevant documents added to the bundle  
* [x] Bundle linked to document
* [ ] Bundle contents reviewed and kept up to date  
* [ ] Multiple bundles linked where more than one domain applies