> 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/forms-to-collections.md).
# Forms to Collections
Assigning a Form to a Collection
Forms are one of the core elements of the Didge Platform. A single form can be used across multiple checkpoints, operations, and work areas. Because of this, assigning a form to a collection is one of the most powerful ways to bulk-assign large sets of operational checkpoints to a collection with a single action.
When a form is added to a collection, every instance of that form used anywhere in the system is automatically included in that collection. This eliminates the need to manually update each checkpoint or operation individually.
***
### When to Use This Method
Assign a form to a collection when:
* A form is used across multiple kitchens, departments, or operational areas
* You want all implementations of a form to fall under a specific Collection (e.g., *Cooking CCP3*)
* You want a single-point assignment that automatically affects all checkpoints based on that form
Example
A “Cooking Temperature CCP3” form may be used in 10 kitchens. Instead of updating 10 separate checkpoints, you simply add the form to the *Cooking CCP3 Collection*. All 10 checkpoints then automatically belong to that collection.
***
### Step 1 — Navigate to Site Forms
1. Ensure you are toggled into Admin Mode.
2. Open the three-dot menu (⋮) from the department view.
3. Select Site Forms.
This will take you to the Site Forms listing page.
***
### Step 2 — Open the Form for Editing
From the Site Forms page:
1. Search for the form you want to assign, or scroll to locate it.
2. In the Actions column, click the three dots (⋮) next to the form.
3. Select Site Form Edit.
This opens the form’s configuration screen.
***
### Step 3 — Assign the Form to a Collection
In the form editor:
1. Select the More tab from the top bar.
2. Locate the Collections field in the *Form Configuration* section.
3. Use the dropdown labeled Select collections… to choose one or more collections.
4. The selected collection will appear as a tag (e.g., *Cooking CCP3*).
You can assign a form to multiple collections if needed.
This is useful when a form applies to more than one process or program.
***
### Step 4 — Save the Settings
Once the correct collections are selected:
* Click Save Settings (top-right) to confirm and apply the assignment.
This step finalises the link between the form and the collection.
***
### How Didge Automatically Updates the System
After saving:
* All checkpoints and operations using this form across the entire site are automatically assigned to the collection.
* The Site Collections list will immediately show all relevant checkpoints under the collection.
* Changes propagate instantly and dynamically.
This dynamic process ensures accuracy and eliminates manual updates.
***
### How End Users See the Collection Assignment
When an end user opens an operation or checkpoint based on the form:
* A Collections section appears at the footer of the screen.
* Expanding this section shows:
* The assigned collection
* A list of all related checkpoints
* Quick links to navigate to those checkpoints
* Any connected policies, procedures, or documentation
This provides context and helps end users understand:
* The operational process they’re part of
* Related checkpoints in the workflow
* The bigger safety/compliance picture
***
### Summary
Assigning a form to a collection is:
Fast: A single action updates every instance of the form across Didge.
Accurate: Zero risk of missing a checkpoint or inconsistent grouping.
Context-rich: End users gain immediate visibility of related checkpoints and documents.
Best Practice: This is the preferred way to manage large sites with repeated workflows.
***
---
# 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/forms-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.
