For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create a Collection

Managing Site Collections

Site Collections allow administrators to organise related components of the Didge Platform—such as operations, checkpoints, submissions, and reports—into logical groups. Collections act as containers that help structure workflows, reporting, and data relationships in a clear and maintainable way.

This guide explains how to access, create, and manage collections within the platform.


Accessing Site Collections

Before managing collections, ensure you are logged in as an Admin user.

  1. Navigate to the Department page.

  2. Click the three-dot menu (⋮) in the upper-right corner.

  3. From the dropdown menu, select Site Collections.

This will take you to the Collections Listing page.


Collections Listing Page Overview

The Collections Listing page displays all existing collections for the selected site.

Here you will see:

  • A table of collections, including:

    • Collection ID (#)

    • Title

    • Description

    • Created At timestamp

  • Row actions:

    • Edit an existing collection

    • Delete a collection (irreversible)

  • A dropdown arrow to expand a collection and view additional details

  • A Show Visualization button to display a visual map of all resources connected to the collection


Adding a New Collection

To create a new collection:

  1. From the Collections Listing page, click Add Collection (top-right button).

  2. A dialog will appear titled Add New Collection.

  3. Fill in the following fields:

Title

Provide a clear and meaningful title.

This is important because collections help define functional groupings (e.g., Cooking CCP, Receiving Procedures, Daily Sanitation Reporting).

Description

Describe what the collection represents or contains.

This helps other administrators understand its purpose, especially in environments with many collections.

  1. Click Add Collection to save.


Important Note: Collections Start Empty

When you create a new collection, nothing is assigned to it by default.

A collection is simply an empty container at creation time.

Next, you will need to navigate into the relevant areas of the platform—such as operations, checkpoints, submissions, corrective actions, or reports—and attach those resources to the collection.

This ensures each collection contains only the components you explicitly choose to associate with it.


Last updated

Was this helpful?