> 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/admin/web-reports-to-collections.md).
# Web Reports to Collections
Assigning a Web Report (Submission) to a Collection
In Didge, web reports represent individual submissions of a checkpoint. When Didge is used for document or policy management, each policy, procedure, flowchart, or HACCP document is stored as a *single submission*.
Because these documents are often core elements of a program (e.g., HACCP plans, SOPs, policies), administrators may want to associate these submissions directly with a collection.
Assigning a web report to a collection ensures that the document becomes part of the operational context for that collection—visible and accessible to users alongside related checkpoints and forms.
***
### When to Use This Method
Assign a submission (web report) to a collection when:
* The submission *is the document itself* (e.g., a policy, SOP, HACCP plan, flowchart).
* The form used is generic, but the actual uploaded document is the meaningful resource.
* You want specific policies or procedures grouped under a collection such as:
* *Cooking CCP3*
* *Receiving Procedures*
* *Cleaning and Sanitation*
* *HACCP Documentation*
Example
A “Cooking Temperature Requirements & Reheating Food” policy exists as a *single submission*. This document should sit inside the *Cooking CCP3* collection so end users can access it directly when performing cooking-related tasks.
***
### Step 1 — Navigate to the Submission (Web Report)
Policies and procedures are usually stored in Document Manager, Central Station, or a similar department.
1. Go to the department that holds document submissions.
2. Open the data table (list of submissions).
3. If needed, use the search bar to locate the policy or document.
4. Click the Web Report icon for the submission you want to assign.
This opens the web report view for that submission.
***
### Step 2 — Toggle to Admin Mode
Once inside the web report:
1. Switch from End User to Admin using the toggle at the top of the page.
2. As an Admin, you will now see the three-dot menu (⋮) at the top-right of the submission page.
***
### Step 3 — Open the Collections Dialog
1. Click the three-dot menu (⋮).
2. Select Collections from the menu.
A modal window will appear titled Collections.
***
### Step 4 — Assign the Submission to a Collection
In the Collections dialog:
1. Click Select collections….
2. Choose the collection(s) that this policy, SOP, or file should belong to.
3. You may assign the submission to multiple collections if relevant.
For example:
* Select Cooking CCP3 for cooking-related policies.
* Select Food Safety Program for HACCP documents.
Once selected, the collection appears as a tag.
3. Click Save Collections to confirm.
***
### Step 5 — Verify the Assignment
After saving:
1. Refresh the browser.
2. The Collections section at the bottom of the web report will now display the assigned collection(s).
3. Inside each assigned collection, the document will now appear in the list of resources.
This ensures that:
* Policies appear alongside checkpoints that use or reference them.
* Collections provide complete context—procedures + operations + reports.
* End users accessing a collection can view the supporting documents directly.
***
### How Submissions Display in Collections
When you revisit Site Collections:
* Expand the collection.
* The assigned submission appears just like checkpoints and table reports.
* Clicking it takes users directly to the policy or procedure.
This integrates documents seamlessly into operational workflows.
***
### Summary
Assigning a web report/submission to a collection provides:
Accurate Policy Association: Attach only the relevant documents to operational workflows.
End-User Clarity: Policies and SOPs appear directly within the collection for easy access.
Complete Context: Collections show forms, checkpoints, and documents all in one place.
Ideal for HACCP and Compliance: Perfect for managing procedures, flowcharts, hazard analyses, and regulatory documents.
---
# 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/admin/web-reports-to-collections.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.
