Files and results

Doozy can use files as source material, attach files to roles and to-dos, and create artifacts (aka deliverables or generated files) you can preview or download. Files can live in a conversation, in Doozy’s managed workspace storage, or inside the workspace’s shared Morph filesystem.

Attach files

Attach files when the source isn’t already available through a connected app or workspace search. You can add files to a capture (aka note, recording, or inbox item), conversation, to-do, or Doozy profile depending on how long the context should remain relevant.

Common supported material includes:

PDF and plain-text documents;
Word documents, spreadsheets, and presentations;
CSV, JSON, YAML, XML, HTML, and Markdown;
source code, configuration files, and notebooks;
images, screenshots, audio, and video;
email exports and other common business formats.

The upload interface shows the current size and format limits. Large media, encrypted documents, corrupted files, and unusual proprietary formats may need conversion before a Doozy can read them.

Put files in the right place

Choose scope deliberately:

Conversation attachment: evidence for one request.
To-do file: material that should stay with a durable unit of work.
Doozy file: stable policy, reference, rubric, or template for one role.
Workspace file: an artifact or source relevant to the broader team.
Morph filesystem: working data, repositories, generated assets, and tool-readable files used during execution.

Don’t attach the same document everywhere. Keep one authoritative copy when possible and link to it.

You can provide a web link or a link from a connected service. Access depends on the link and the workspace’s authenticated connections.

If a Doozy can’t open the content, confirm that the connection (aka connector or integration) has permission, the link points to the expected account, and the resource isn’t limited to a different organization. Don’t make a private document public just to unblock a Doozy.

Ask for a reviewable result

Describe the artifact and its quality bar, not only the topic.

Create an editable launch-readiness spreadsheet. Include owner, due date, source link, confidence, and blocker status. Add a summary tab with the five decisions leadership needs to make.

For important outputs, ask the Doozy to include:

source links or citations;
assumptions and unresolved questions;
the date range and systems reviewed;
a concise change summary;
validation performed;
the location of editable source files.

Preview generated work

Generated files appear in the conversation, to-do, or workspace Files view. Preview supported formats in Doozy and download them when you need native application features.

Treat a polished preview as a review aid, not proof that the underlying work is correct. Check formulas, links, totals, permissions, visual layout, and any claims that could affect a decision.

Preserve evidence

Ask Doozies to keep the evidence needed to audit or reproduce a result. Depending on the to-do, that can include screenshots, logs, citations, test output, input versions, browser recordings, diffs, or a short methodology note.

Evidence should explain what happened without exposing secrets. Redact tokens, passwords, personal data, and unnecessary customer information before including logs or screenshots in an artifact.

Shared Morph files

All Doozies in a workspace use the same Morph filesystem. This makes collaboration straightforward: one Doozy can prepare a dataset, another can analyze it, and a third can produce the final report.

Shared access also means files aren’t private to the Doozy that created them. Use separate workspaces for projects that need hard separation. Within a workspace, use clear directories, file names, and version-control practices to prevent accidental overwrites.

Durable project files should live in the workspace’s persistent directory or a connected source-control system. Temporary downloads, caches, build output, and disposable packages can be recreated and may not survive recovery operations.

Delete or remove files

Deleting a conversation or Doozy doesn’t necessarily delete files copied into workspace storage, Morph, or a connected service. Remove sensitive material from each place where it exists and revoke shared links when appropriate.

Frequently Asked Questions

Where should I attach a file?

Attach it to a capture or conversation for short-lived context, a to-do for one assignment, or a Doozy profile when the file is durable role guidance.

Can every Doozy in a workspace access the same files?

Workspace files and Morph state can be shared across Doozies when permissions allow. Use separate workspaces when files, credentials, customers, or environments require hard isolation.

What should I do when a file format can't be read?

Confirm the upload completed, then export proprietary formats to PDF, CSV, plain text, or another supported format. Scanned documents may need OCR.

How do I avoid conflicting file versions?

Keep one authoritative copy when possible, link to it from to-dos, and use clear names or version control. Don't attach the same document independently across several conversations.

Does deleting a conversation delete its files?

Not necessarily. Copies may remain in workspace storage, Morph, generated artifacts, or connected services. Remove sensitive data from each location where it exists.

Looking for something broader? Read the general FAQ.