Sistava

Data Export

Every workspace surface that shows your history, chat threads, the task board, activity logs, and Drive files, has its own download control that exports the current, filtered view as Markdown, CSV, or JSON. Use it to pull records for an audit, share a run outside the app, or keep an offline copy of what an employee produced.

Sistava does not lock your history inside the app. Wherever you can see a list, chats, tasks and sprints, the Activity feed, or the files an employee produced in Drive, there is a matching export control that turns the current, filtered view into a file you can open anywhere.

Each surface exports in Markdown, CSV, or JSON. Markdown reads like a document, CSV opens straight into a spreadsheet for filtering and pivoting, and JSON keeps the full structured record for scripts or another system. The export always respects whatever filter or scope you already applied, so a filtered Activity tab exports only what is on screen, not the entire company history.

The difference from copying data by hand or asking an employee to summarize it is that the export is a direct dump of the underlying records, not a paraphrase. Task exports carry the same fields as the kanban board (status, owner, due date, sprint), Activity exports carry timestamps, correlation IDs, and per-action detail, and Drive exports carry the actual files an employee registered as work product. Nothing is reworded or reasoned over in between.

There is no separate export employee or export job to configure. Each tab's own download button builds the file client-side from data already loaded on screen and hands it to your browser immediately, so there is no queue, no email delivery, and no waiting.

Files come out named so you can find them again months later. Every export follows the same pattern, the kind of thing it is, the scope it covers, and the date it was taken, written in words a person recognises rather than an internal reference. Drop a folder of them in your file manager and they sort themselves into chronological order without you renaming anything.

Chat has its own version of this. When an employee gathers a set of documents for you, the result carries a button that downloads all of them together as a single zip file, assembled in your browser from files you can already open. It is the same principle as the list exports: nothing is queued on a server, and nothing is delivered by email later.

Export is deliberately read-only and always will be. Downloading a view never edits, archives, or removes anything, and it never reaches past what you can already see: if a part of the workspace is not visible to you on screen, it does not appear in your file either. You can export the same view as many times as you like without changing a thing.

What You Can Export

Activity history: every activity and its actions, with timestamps, status, actor, correlation IDs, and (when a row is expanded) the child activities underneath it, such as a delegation to a teammate.

Tasks and sprints: the current task list or board, with status, assignee, sprint, and due date carried over from what is filtered on screen.

Chat threads: the visible conversation, useful for sharing a specific exchange outside the app.

Drive files: the actual documents, spreadsheets, and other assets an employee has produced and saved to Drive, downloaded directly rather than converted to another format.

Choosing a Format

Markdown is the readable option: headings, tables, and structure meant for a document or a message you paste elsewhere.

CSV opens directly in a spreadsheet, which is the natural choice when you want to filter, sort, or pivot a large activity or task list outside Sistava.

JSON keeps the full structured record, field names and all, for feeding into another tool or a script rather than reading by eye.

What Export Deliberately Does Not Do

There are no scheduled exports and no exports delivered by email. Every export is something you press, on the view you are looking at, and the file arrives in your downloads a moment later. Nothing runs on a timer in the background, which also means there is nothing to forget to switch off.

There is no single button that dumps your entire workspace history in one file. Export follows the view: you choose the scope and the filter on screen, and that is what comes out. Taking a full record means taking each surface in turn, which keeps every file meaningful instead of producing one enormous unreadable dump.

Export never becomes an upsell. The download control sits on the same tabs for every plan, with no size cap tied to what you pay and no credits consumed, because getting your own records out of a product should never be the thing you have to upgrade for.

How It Works

Every list view carries its own download control

On the Activity tab, a download control exports the current, filtered list of activities. The Work source filter (Chat, Voice, Routine, Saved skill, API, MCP, Webhook) and the employee, team, or company scope you have selected both carry through to the export, so the file matches exactly what is on screen.

The Tasks view exports the current board or list, including status, sprint, owner, and due date, in the same three formats. Chat threads export the visible conversation. Drive exports the files an employee has produced and registered as work assets.

Pick Markdown, CSV, or JSON from the export control and the browser downloads the file immediately. There is no background job, no size limit tied to a plan, and no delay waiting on a server-side process.

Use Cases

Compliance and audit requests

Export the Activity tab, filtered to a date range or employee, as CSV or JSON to hand an auditor a complete, timestamped record of what an employee did and when, without manually copying rows.

Sharing a run outside the app

Export a single chat thread or an activity's history as Markdown to paste into an email, a ticket, or a document when someone outside Sistava needs to see exactly what happened.

Analyzing task throughput in a spreadsheet

Export the task board as CSV and pivot it in a spreadsheet to see completion rates by sprint or owner, work that is easier in a spreadsheet tool than in the kanban view itself.

Keeping an offline archive of Drive output

Download the documents and files an employee has produced in Drive so a copy exists outside the platform, independent of the platform's retention window.

Comparison

BeforeAfter
Getting your history out means copying rows by hand or taking screenshots of a screen.A download control on every list view exports exactly what you filtered, as Markdown, CSV, or JSON.
An export request goes to support and comes back as a file, eventually.The file lands in your downloads immediately, built in your browser with no job to wait on.
The record of what was done lives only inside the tool that did it.Activity, tasks, chats, and Drive output all leave as ordinary files you can keep, audit, or hand over.
Serious exports are the paid add-on, so proving what happened depends on your tier.Every plan gets the same export controls, with no size cap and no credits spent.

FAQ

What formats can I export to?

Markdown, CSV, or JSON, chosen from the download control on the tab you are exporting from.

Does the export include everything, or just what I have filtered?

Just what is currently filtered and scoped on screen. If you have the Activity tab filtered to a specific employee and Work source, the export matches that view, not the full company history.

Is exporting available on every plan?

Yes. The download control on Activity, Tasks, Chat, and Drive is not plan-gated; deeper detail inside an individual activity, such as the Execution or Memory sections of the Activity Inspector, is gated separately and still shows on screen even if not carried into a lightweight export.

Does exporting cost credits?

No. Exports are built from data already loaded in your browser and do not trigger any employee work or model call.

Can I export a single Drive file instead of everything?

Yes. Drive lets you download an individual file directly rather than exporting the whole list.

Can I schedule an export to run automatically or have it emailed to me?

No. Every export in Sistava is a button you press on the view you are looking at, and the file downloads straight away. There is no recurring export, no background job, and nothing delivered to your inbox later.

Can I download several files an AI employee made in one go?

Yes. When an employee gathers a set of documents for you in chat, the result carries a button that downloads all of them together as a single zip file. The zip is assembled in your browser from files you can already open, so there is nothing to wait for.

Will exporting change or delete anything in my workspace?

No. Export is strictly read-only: it copies what is on screen into a file and leaves the workspace exactly as it was. You can export the same view as many times as you want with no effect on your data.

Where Data Export fits

Data Export is part of How you see what they did.

A real-time activity feed shows who is working on what right now. The step-by-step inspector traces every tool call, decision, and reasoning chain. Cost tracking breaks down spend per message, per employee, and per team. Walk through your live 3D office to see your workforce at a glance.

Read the guide

More in Monitoring

Explore