--- title: "Record Collections" slug: "record-collections" status: "update" updated: 2026-10-13T15:36:01Z published: 2026-10-13T15:36:01Z canonical: "docs.unqork.io/record-collections" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Record Collections Record Collections is a workspace-level tool for viewing and managing submission records across modules, data models, and workflows. From the Explorer panel, Creators can browse records, run bulk imports and exports, and track the status of long-running jobs. ## Accessing Record Collections Record Collections is accessible from the **Explorer panel**. In the panel, expand the **Utilities** folder, then expand **Record Collections** to see the collections in the current workspace. The Explorer panel organizes collections into three sub-folders: - **Modules**: Collections associated with individual modules. - **Workflows**: Collections associated with workflows. - **Data Models**: Collections associated with data models. This sub-folder is visible only when the Data Models feature is enabled for the organization. > [!NOTE] > Access to Record Collections requires the appropriate RBAC permissions. Creators without access see a permission denied message instead of the page content. ## Who Uses Record Collections Record Collections is a data operations tool, not a day-to-day building tool. The Creators who use it are those responsible for data operations. They run bulk imports at go-live, migrate data between environments, export records for external reporting, and troubleshoot errors at the record level. ## Explorer Panel Expand a collection folder to see its contents. Each collection folder contains the following: - A **Job Tracker** sub-folder listing past and current import and export jobs. - Individual **record entries** identified by their record ID. Records and jobs load on demand. When a collection holds more than 25 records or jobs, a **Load more** option displays at the bottom of the list. ### Collection Folder Actions Hovering over a collection folder reveals a ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153559_d79600a1751346d6a994700cb8a3e75e.svg?sv=2026-02-06&spr=https&st=2026-11-03T08%3A13%3A52Z&se=2026-11-03T09%3A13%3A52Z&sr=c&sp=r&sig=%2BC3ALKfgS7CTwOltMUYVtVIZGp5hMeIpYw0nSyUTOKo%3D) (**ellipsis**) button. Select it to access the following actions: | Action | Description | | --- | --- | | **Copy ID** | Copy the collection's unique identifier to the clipboard. | | **Copy Name** | Copy the collection's display name to the clipboard. | | **Import** | Open the import dialog to upload a file and create an import job. | | **Export** | Open the export dialog to configure and begin an export job. | | **Refresh** | Re-fetch the collection's records and jobs without reloading the page. | > [!NOTE] > Import and Export are available only when the corresponding features are enabled for the organization by an administrator. ## Exporting Records To export records from a collection: 1. Hover over the collection folder in the Explorer panel, select the ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153559_d79600a1751346d6a994700cb8a3e75e.svg?sv=2026-02-06&spr=https&st=2026-11-03T08%3A13%3A52Z&se=2026-11-03T09%3A13%3A52Z&sr=c&sp=r&sig=%2BC3ALKfgS7CTwOltMUYVtVIZGp5hMeIpYw0nSyUTOKo%3D) (**ellipsis**) button, then select **Export**. 2. Configure the following export options: - **Export Name**: A label for the export job. - **Select Format**: The format for the exported file. - **Select Records to Export**: Choose **All**, **Active**, or **Archived**. - **Include metadata**: When checked, this setting includes date created, date modified, and creator fields in the export. - **Select number of files to export**: The count of output files to generate. Fewer files might result in slower load times for large collections. 3. Select **Start Export** to begin the job. The platform navigates to the job detail page where Creators can monitor progress. For details on job statuses and batch-level tracking, see [Job Tracker](/unqorkai/docs/job-tracker). ### Supported Export Formats | Format | Description | | --- | --- | | **CSV** | A single comma-separated values file. | | **ZIP CSV** | A ZIP archive containing a CSV file. | | **JSON Lines** | A single file with one JSON object per line. | | **ZIP JSON Lines** | A ZIP archive containing a JSON Lines file. | | **ZIP with Multiple JSON Files** | A ZIP archive containing one JSON file per record. | ## Importing Records To import records into a collection: 1. Hover over the collection folder in the Explorer panel, select the ![EllipsisVertical](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/api_upload_20261013_153559_d79600a1751346d6a994700cb8a3e75e.svg?sv=2026-02-06&spr=https&st=2026-11-03T08%3A13%3A52Z&se=2026-11-03T09%3A13%3A52Z&sr=c&sp=r&sig=%2BC3ALKfgS7CTwOltMUYVtVIZGp5hMeIpYw0nSyUTOKo%3D) (**ellipsis**) button, then select **Import**. 2. Configure the following import options: - **Select Fallback Record** : The service user assigned as record owner when the original owner cannot be determined. - **Select Format**: The format of the file being imported. - **Store in new data object**: When checked, this setting stores imported records in a new data object in the submission. - **Upload File**: Drag and drop a CSV, JSON, or ZIP file, or select one from a local device. Maximum file size is 100 MB. 3. Select **Import** to begin the job. > [!NOTE] > Expired credentials can be selected as the fallback record owner. > [!NOTE] > Deleting a credential changes the owner on all records assigned to that credential. Expiring a credential or generating a new does not affect record ownership. Imports run as background jobs. The platform navigates to the job detail page where Creators can monitor progress. For details, see [Job Tracker](/unqorkai/docs/job-tracker). ## Job Tracker The Job Tracker monitors the status of import and export jobs for a collection. Expand the **Job Tracker** sub-folder under a collection in the Explorer panel to see current and past jobs. Each job displays its name, type (import or export), status, and the date and time it was initiated. Job statuses include: | Status | Description | | --- | --- | | **Created** | The job has been created but has not started yet. | | **Queued** | The job is waiting to be processed. | | **In Progress** | The job is actively running. | | **Completed** | All batches finished successfully. | | **Partially Completed** | Some batches succeeded; others failed. | | **Failed** | The job encountered an error and did not complete. | | **Canceled** | The job was stopped before completion. | Select a job to open its detail page, which displays batch-level progress and download links for completed export batches. For full details, see [Job Tracker](/unqorkai/docs/job-tracker). ## Record Detail Select a record entry in the Explorer panel to open its detail page. The detail page displays the stored data for that record across the following sections: - **Record Info**: The record ID, owner, status, created date, and modified date. - **Data**: The full record data as read-only JSON. - **Validation Errors**: Any validation errors associated with the record. This section is hidden when the record has no validation errors. - **Metadata**: Additional record metadata as read-only JSON. This section is hidden when the record has no metadata. For full details, see [Record Detail](/unqorkai/docs/record-detail). --- **Changelog** | Date | Change | | --- | --- | | 2026-10-09 | Importing Records: added notes on expired credential selection and credential deletion behavior. Fixed ellipsis icon markup. | | 2026-09-01 | Expanded with Explorer panel tree structure, collection folder actions, and Record Detail section. Added Partially Completed, Queued, and Created job statuses. Corrected collection types (modules and workflows appear alongside data models). Added links to new sub-pages: Record Detail, Job Tracker, and Record Operations API. | | — | Initial publication. | Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. A functionality of a software. For example, Copy and Paste is a feature of a computer's operating system. RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network. A place on your operating system that stores recently copied content. The clipboard only stores one item at a time. Fetching is the process of retrieving data from a database, making it available to the application and the end-user. A zip file is a file format that can contain multiple files combined and compressed into one file. Since it's a type of compressed file, a zip file can be smaller in size than the files it contains. JSON Lines is a format for storing structured data that may be processed one record at a time. It works with unix-style text processing tools and shell pipelines. An object is a type of data structure that represents a single, self-contained entity that acts as a container for the characteristics of that entity. JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.