🔗 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 into a collection and map dependencies across folders.

1️⃣ Creating a Collection

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:

Each collection requires:

1. Name – Identify the collection.
2. Description – Context about the collection.
3. Document types – Select which for which types dependencies should be shown when selecting this collection.
4. Quick groups – Choose predefined sets (e.g. all Digital Assets, all Physical Assets).

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

• 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.

3️⃣ Switching Between Collections

Use the top-right dropdown to switch between collections.

4️⃣ Modifying an Existing Collection

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

Updated on: 05/09/2025