> 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/checkpoints-to-collections.md).

# Checkpoints to Collections

Assigning a Checkpoint to a Collection

While assigning a form to a collection is ideal for bulk updates, there are many situations where a more precise and context-specific approach is required. In these cases, you can assign an individual checkpoint (operation) directly to a collection.

This method gives administrators fine-grained control over how checkpoints are grouped and ensures that only the relevant operational instances are included in a collection.

***

### When to Use This Method

Assigning a checkpoint directly to a collection is useful when:

* A form is used widely across different contexts (e.g., audit checklists, GMP checklists, cleaning checklists), but only one specific usage should belong to a collection.
* You need granular control over which checkpoints are grouped together.
* Adding the entire form to a collection would incorrectly assign all its checkpoints.

Example

A single “Checklist” form may be used for:

* Internal Audits
* GMP Inspections
* Cleaning Verification
* Inventory Checks

You would *not* add the form to a collection because that would group all of these together.

Instead, you assign only the specific checkpoint (e.g., GMP Inspection → Cleaning Collection).

***

### Step 1 — Navigate to the Checkpoint as an Admin

1. Ensure you are toggled into Admin Mode.
2. Navigate to the operation/checkpoint you want to assign.
   * You can access it through the site structure, schedules, or directly via your operations index.

<figure><img src="https://4248908630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbT2FgjeSTRyDJH1C11vg%2Fuploads%2FR802i34Oo9BhzpteGUdJ%2FScreenshot%202025-12-04%20at%208.51.09%E2%80%AFam.png?alt=media&amp;token=8380d37a-e2ea-4475-905c-8cb87129aa2f" alt=""><figcaption></figcaption></figure>

***

### Step 2 — Open Advanced Settings

Inside the checkpoint editor:

1. Scroll down and open the Advance Settings panel.
2. Locate the Collections field within the panel.

This is where you assign the checkpoint to a collection.

***

### Step 3 — Assign the Checkpoint to a Collection

In the Collections field:

1. Click the dropdown labeled Select collections….
2. Choose the collection(s) you want this checkpoint to belong to.
3. Multiple collections may be selected if appropriate.

Each assigned collection appears as a tag (e.g., *Cooking CCP3*).

<figure><img src="https://4248908630-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbT2FgjeSTRyDJH1C11vg%2Fuploads%2FJsyOWac9drzFeNcVICfm%2FScreenshot%202025-12-04%20at%208.51.46%E2%80%AFam.png?alt=media&amp;token=01a9403b-2dd7-4b0b-b0e8-7324e4cbd932" alt=""><figcaption></figcaption></figure>

***

### Step 4 — Update the Checkpoint

Once you’ve selected the correct collection(s):

* Click Update Operation (or Update Checkpoint) at the bottom of the page.

This confirms the assignment and updates the checkpoint immediately.

***

### How Didge Applies the Assignment

After saving:

* Only this specific checkpoint is assigned to the collection.
* No other checkpoints using the same form are affected.
* The checkpoint appears inside the Site Collections view under the chosen collection.
* The collection’s visualisation and mapping update instantly.

This ensures complete precision for complex or multi-purpose forms.

***

### How End Users See the Collection Assignment

When staff open the assigned checkpoint:

* A Collections section appears at the footer.
* Expanding it shows:
  * The assigned collection
  * Other checkpoints inside that collection
  * Operational context
  * Linked table reports
  * Policies, SOPs, or documentation connected to the collection

This adds operational clarity and transparency for end users.

***

### Summary

Assigning a checkpoint to a collection provides:

Granular Control: Only specific checkpoints are grouped, avoiding misclassification.

Flexibility: Ideal for forms used in many unrelated contexts.

Real-Time Accuracy: Collections update instantly after saving.

Better Operational Context: End users see exactly where the checkpoint belongs within the workflow.


---

# 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/checkpoints-to-collections.md?ask=<question>&goal=<user_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.