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.
Go to the department that holds document submissions.
Open the data table (list of submissions).
If needed, use the search bar to locate the policy or document.
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:
Switch from End User to Admin using the toggle at the top of the page.
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
Click the three-dot menu (⋮).
Select Collections from the menu.
A modal window will appear titled Collections.
Step 4 — Assign the Submission to a Collection
In the Collections dialog:
Click Select collections….
Choose the collection(s) that this policy, SOP, or file should belong to.
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.
Click Save Collections to confirm.
Step 5 — Verify the Assignment
After saving:
Refresh the browser.
The Collections section at the bottom of the web report will now display the assigned collection(s).
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.
Last updated
Was this helpful?