---
title: Team Chat history export (planned)
---
# Team Chat history export (planned)

## What it is

**Status:** In-development (not yet built). Registered as unreleased feature `team-chat-export`.

### Why it matters

As a multi-user cloud product, Omniscio's Team Chat stores user-generated content server-side (Firestore). GDPR Article 20 requires that users can obtain their personal data in a structured, commonly used, and machine-readable format. Beyond compliance, export is also useful for:

- Workspace migration (moving to/from another tool).
- Archival and backup.
- Audit and legal discovery.

### Current state

No code exists yet. The feature is registered in `UNRELEASED_FEATURES` with setting key `teamChatExportEnabled` and gated via the standard unreleased-feature mechanism.

## Where to find it

Nothing to open — this is planned work with no screen in the product yet.

## How it behaves

### What it will do

Allow users to export their Team Chat channel or DM history to a portable format (JSON, CSV, or both). This is a GDPR Article 20 data portability requirement for a multi-user cloud product.

### Planned capabilities

- **Per-channel export** -- export all messages from a specific channel or DM conversation.
- **Date range filter** -- optionally limit the export to a specific time period.
- **Format options** -- JSON (machine-readable, preserves all metadata) and CSV (human-readable, spreadsheet-compatible).
- **Include attachments** -- option to include or exclude file attachments in the export.

### Scope and considerations

- **Authorization**: only workspace owners/admins should be able to export an entire channel; individual users should be able to export their own DMs.
- **Volume**: channels can have thousands of messages; the export may need to be paginated or streamed.
- **Privacy**: exported data must respect the same visibility rules as the live chat (no leaking private channels a user cannot read).
- **Delivery**: large exports may need to be generated server-side and delivered as a download link rather than built client-side.

## Related

Team Chat itself covers the surface being exported; the API platform and dead-letter recovery pages are the other planned Team Chat capabilities.