> ## 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).

# Dependencies

# 🔗 **Dependencies**  
> **"Visualize how all your documents are connected."**  
> *Create collections to track relationships between assets, policies, risks, and more.*  

The **Dependencies menu** provides a **visual graph** of how your information links together.  

Instead of only viewing **linked documents** in detail, you can group [document types](https://docs.brainframe.com/en/article/document-types-templates-lssmkc/) into a **collection** and map dependencies across folders.  

---

## 1️⃣ Creating a Collection  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-12-at-20310_140ak08.png =868xauto)
The first time you open the module:  
1. Navigate to the **Dependencies** menu.
2. Click **Add dependency collection**.  
3. Or, if collections already exist, create a new one from the dropdown menu.  


Adding a new collection or opening an existing one will show the following view:
![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-12-at-20314_1gb6nux.png =521xauto)
Each collection requires:  
* **Name** – Identify the collection.  
* **Description** – Context about the collection.  
* **Document types** – Select which for which types dependencies should be shown when selecting this collection.  
* **Quick groups** – Choose predefined sets (e.g. all Digital Assets, all Physical Assets).  

| 📌 Info: Collections become documents in the current folder. Standard folder permissions control visibility.  
---

## 2️⃣ Using Collections  

Key points:  

* **Folder scope** – Collections only display documents from the current folder and its subfolders.  
  *(Use **Inbox** to see everything you can access.)*  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-12-at-20322_10161ty.png =627xauto)
* **The first time you load** → items are placed randomly.  
* **Drag & drop** → reposition items to set a fixed layout, which will remain for the future times you open the graph.  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/screenshot-2026-07-12-at-20324_1irqxnm.png =650xauto)
| 📌 Selecting a document highlights dependencies in red.  

| 📌 Double-click items to open them directly.  

| 📌 Export graphs as images with the download icon at the top right (arrange before export).  

---

## 3️⃣ Switching Between Collections  

Use the **top-right dropdown** to switch between collections.  


| 📌 Click the configuration icon to locate the collection’s document file.  

---

## 4️⃣ Modifying an Existing Collection  

![](https://storage.crisp.chat/users/helpdesk/website/-/3/f/2/6/3f26ce462760bc00/collections-edit_x3b1qv.png)

To edit:  
1. Open the document representing the collection.  
2. Change the **name** or **description**.  
3. Adjust included **document types**.  

---

## 5️⃣ Best Practices  

* 🗂 **Organize collections by purpose** — e.g., GDPR, security, architecture.  
* 🖼 **Reposition items manually** for clarity before exporting.  
* 🔍 **Use folder filtering** to zoom into specific departments or processes.  
* 📌 **Name collections consistently** (prefix like “GDPR – …” or “ISO – …”).  

---

## 🎯 Visual Checklist  

* [x] New collection created in the correct folder  
* [x] Relevant document types selected  
* [ ] Layout arranged and saved before export  
* [ ] Collections named consistently across teams  
* [ ] Dependencies highlighted and reviewed regularly