> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/administration/data-exports.md). # Data Exports As an admin, you can export a snapshot of your organization's data (projects, meetings, emails, documents, drawings, reports, observations, and transmittals) as multi-part zip files. Exports run asynchronously in the background; once complete, every part is available to download from the same screen. Common reasons to run a Data Export: * Periodic offline backups outside Cogram. * Audit trails for a specific project or time window. * Bulk handover at the end of a project or engagement. Data Exports live in the **Data Exports** section of [Organization Settings → General](https://app.cogram.com/dashboard/settings/admin/overview#data-exports). Only **organization administrators and owners** can see the section and create exports. ## Choosing a meeting template before exporting Meeting minutes inside the export are rendered as `.docx` files. Cogram ships with a built-in template (**Cogram Default**), but you can upload your own organization-branded template and mark it as the **Organization Default**. Every meeting `.docx` in subsequent exports will then use your layout. Go to [Organization Settings → Templates](https://app.cogram.com/dashboard/settings/admin/templates), upload your `.docx`, open the row menu (`⋯`), and choose **Set as Organization Default**:

The row menu on the Templates page exposes a "Set as Organization Default" action.

Once applied, the row gets an **Organization Default** badge. The built-in template still shows its **Cogram Default** badge; it remains available as a fallback if your custom template is ever removed.

A custom template marked as Organization Default sits alongside the built-in Cogram Default.

> Set the Organization Default **before** kicking off an export: exports use the template that's marked default at the moment the worker renders each meeting's `.docx`. ## The Data Exports section This section lists every export your organization has created, with its status, scope, time window, who requested it, and when the download links expire.

The Data Exports section lists every past and active export.

Each row shows: * **Status**: `Pending`, `Running`, `Cancelling`, `Cancelled`, `Completed`, `Failed`, or `Expired`. * **Requested by**: the user who clicked **New Data Export**, or an `API Key` chip when the export was created via the [Cogram API](/administration/cogram-api.md). * **Scope**: `Org-wide`, `Single Project`, or `N Projects`; hover for the project names, or open the row for the full list. Multi-project exports are created through the [Cogram API](/administration/cogram-api.md); the dialog here covers org-wide and single-project. * **Time window**: the date range, or `All time` for project-scoped exports. * **Created**: when the export was requested. * **Expires**: when the download links will be removed (7 days after completion). ## Creating an export Click **+ New Data Export** in the top-right. The dialog asks for two things: a **scope** and a **time window**. ### Scope: org-wide or a single project The **Scope** selector lets you target either your entire organization or one project.

Choose between an org-wide export or a single project.

### Time window The available time-window options depend on the scope you picked. #### Org-wide → date range only (max 6 months) For org-wide exports, the time window is a **date range**, and capped at **6 months**. This keeps the package size predictable and the build time bounded.

Org-wide exports always require a date range.

The dialog reminds you about the cap inline:

The 6-month cap is enforced for org-wide exports. To cover a longer span, run several back-to-back exports.

#### Project-scoped → All time or a date range For project-scoped exports, the cap is lifted and an **All time** option is available alongside **Date range**, useful for handovers or full archives of a single project.

Project-scoped exports offer the "All time" option.

Click **Create Data Export** to start the build. The dialog closes and the new export appears at the top of the list in `Pending` status. It will transition through `Running` and into `Completed` (or `Failed`) as the worker progresses. > Only **one** export can be active per organization at a time. If a `Pending`, `Running`, or `Cancelling` export already exists, the **+ New Data Export** button will be rejected until it finishes. This keeps the worker queue fair across orgs. ## Downloading a completed export Once an export reaches `Completed`, a **download icon** appears in its row's **Actions** column.

Click the download icon on any completed row to inspect and download the parts.

Clicking the icon (or the row itself) opens the **Data Export details** dialog with a per-part download list:

Each export is split into one or more zip parts. Click "Download" to grab a part.

The detail dialog shows: * The export's status, scope, time window, who requested it, when it was created, and when its links expire. * The list of **zip parts**, each with its size and a **Download** button. Large exports are split into multiple parts so each zip stays a manageable size. Download every part and unzip them into the same folder to reconstruct the full package. For what's inside (the folder structure, file types, and how to tell Cogram's example/demo data apart from your own), see [Data Export Package Layout](/administration/data-export-package-layout.md#identifying-example--demo-data). > Each **Download** link is a short-lived signed URL valid for **one hour**. If a link expires before you click it, just reopen the detail dialog; fresh links are minted every time you load it. ## Lifecycle and retention * **Build time** scales with the volume of meetings, emails, and documents in scope. Most exports finish within minutes. * **Download links expire one hour after generation**: reopen the detail dialog to mint fresh links. * **Parts are retained for 7 days after completion**, then transition to `Expired`. The row stays in the list for audit purposes, but the zips are deleted from storage and the **Download** buttons disappear. * **Cancellation**: `Pending` exports cancel immediately; `Running` exports finish the part they're on and then stop, so cancellation can take a few seconds to settle. ## API access Everything on this page is also available via the [Cogram API](/administration/cogram-api.md#data-exports). Use the API if you want to schedule recurring exports, drop the resulting zips into your own backup pipeline, or run an export from your own internal tools. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cogram.com/administration/data-exports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.