> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/collections/end-user/collections-for-end-users.md).
# Collections for End Users
Understanding context, navigating related resources, and visualising food safety controls
### Overview
Collections provide end users with an easy way to understand the context behind the tasks they perform in Didge. Whether a user is completing a checkpoint, reviewing a table report, or accessing a web report, Collections allow them to instantly see all related resources—policies, forms, checkpoints, procedures, or training—linked to the same food safety control or program element.
Collections appear directly within the everyday tools operators use, ensuring the feature enhances context without disrupting workflow.
***
## 1. Accessing Collections
Within any department in Didge, users can access all Collections for the site using the three-dot menu.
#### Steps:
1. Open a Department.
2. Click the three-dot menu (⋮) in the top-right corner.
3. Select Site Collections.
This takes the user to the Collections overview page, where all Collections assigned to the department/site are listed.
***
## 2. Collections Listing Page
On the Collections page, users will see a table listing all Collections relevant to the site:
* Collection title
* Description
* When it was created
* Tools to edit or delete (for users with permissions)
Clicking the dropdown arrow expands the Collection.
***
## 3. Viewing Collection Details
When a Collection is expanded, two key elements appear:
#### A. The List of Associated Resources
Users will see all resources included in the Collection, such as:
* Checkpoints
* Data tables / Table reports
* Web reports
* Procedures
* Policies
* Training resources
Each item is clickable, allowing users to jump directly to the associated resource.
This provides a powerful contextual navigation layer—users can see exactly how their operational tasks connect to policies, controls, and other requirements.
***
## 4. Collection Visualisation
Each Collection includes a visualisation panel, which displays a graphical, “celestial-style” map of all associated items.
This visualisation helps users:
* Understand relationships between resources
* See which areas of operations contribute to the same food safety control
* Interpret complex multi-department dependencies
Nodes are visually grouped by type, such as:
* Collections (purple)
* Operations/Checkpoints (blue)
* Operation Instances or other linked items (orange)
This is especially useful in complex environments like hotels, aviation catering, or healthcare kitchens where multiple kitchens or departments link into the same control (e.g., CCPs).
***
## 5. Collections Inside a Resource
Collections also appear within the resources themselves.
This means users don’t have to navigate away from their workflow—Collections come to them.
#### Where Collections Appear:
At the footer of:
* Checkpoints (operations)
* Data tables
* Table reports
* Web reports
#### Example:
In a cooking checkpoint:
* At the bottom of the form, users see a collapsible Collections panel.
* Expanding it shows any Collections this checkpoint is part of.
This helps operators understand:
* What control the checkpoint relates to
* Which SOPs or policies support that checkpoint
* How the data they enter is used in the broader food safety program
This improves clarity, training, and compliance confidence.
***
## 6. Example: Collections in a Table Report
In a table report such as a Cooking Submissions report:
* The Collections panel at the footer shows which Collections include this data table.
* Users can click into the Collection to explore related checkpoints, policies, or training
This turns any report into a launch point for deeper understanding.
***
## 7. Example: Collections in a Checkpoint
Inside a cooking checkpoint form:
* After completing fields and adding evidence/signature,
* The footer reveals the Collections panel.
* This lets operators instantly see all related resources (e.g., CCP policies, training, procedures).
This is especially helpful for new staff or operations with complex compliance requirements.
***
## 8. Summary of Benefits for End Users
#### Contextual Awareness
Users understand the *why* behind each task—what control it belongs to and what resources support it.
#### Better Navigation
Collections allow quick movement between related items, reducing confusion and improving efficiency.
#### Improved Training & Onboarding
New staff immediately see the full picture of the control they are completing.
#### Consistency & Accuracy
Resources are no longer scattered. Collections provide structure and clarity.
#### Audit Readiness for All Staff
Users can confidently demonstrate the control, its related forms, and its evidence with just a few clicks.
***
## 9. Final Thoughts
Collections transform Didge into a more context-rich, navigable, and audit-ready platform.
They enhance operational clarity without adding complexity, ensuring that users—from chefs and stewards to auditors and QA teams, can easily understand the purpose and relationships behind the tasks they perform.
***
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.didge.io/home/collections/end-user/collections-for-end-users.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
