Files and attachments

Files can belong to the request, a participant's decision, or a discussion message. Check where you attach a file so it is part of the intended record.

Each attachment can be up to 50 MiB (52,428,800 bytes). This applies to request, decision, and discussion attachments. Workspace storage and token limits also apply.

Request files

Add the documents participants must review when creating a request. Use recognizable filenames and check the selected files before submitting.

Open a filename to use its available preview or download action. Preview support depends on the file format and browser. If a preview cannot display the document, download it and use a suitable application.

Decision attachments

Attach response files in the task action area when requested. A step marked Require an attachment cannot be completed without its required response file.

Decision attachments appear with the recorded task action. Uploading the same file to Chat does not satisfy a task's attachment requirement.

Discussion attachments

Attach supporting material to a Chat message when you need to clarify the request. Consider the discussion audience before sharing it.

Revised files

A revision can add, remove, or replace request files. Review the current file list and use Show revision changes for context. Replaced and removed files shown there are not current review documents.

Upload problems

Wait for uploads to finish before submitting. If an upload is rejected, read the error and check the file and workspace's usage limits. Avoid repeatedly submitting while a request is still processing. See Troubleshooting for failed actions.

Tokens and storage

Uploads and file viewing/downloads consume tokens; file size also counts toward a separate storage allowance. Task and discussion uploads carry their workflow context so the originating workspace pays. Generic uploads use the selected workspace. Uploads are charged after success; failed uploads are not charged. Concurrent transfers can overdraw the token balance; an interrupted download is charged for document bytes transferred. See Usage and tokens.