Files and workspaces

Files work best when they are attached to the item that owns the work. A project statement of work belongs with the project; a troubleshooting capture belongs with the ticket; a run output belongs with the Custom Agent run.

​

Add files to Chat

Use the attachment control in the composer to add relevant material. Then tell Forge how to use it:

• identify the source and date;
• state whether it is authoritative, a draft, or an example;
• name the fields or questions that matter;
• call out anything Forge should not infer.

For example:

This is the approved statement of work. Use its exclusions as hard constraints, compare its milestones to the current Work Plan, and list any mismatch before proposing changes.

​

Continue from a workspace

Ticket, project, opportunity, activity, account, and agent-run workspaces can provide context to Chat. Starting there is usually safer than creating an unscoped organization conversation because the target is visible and the connected records are easier to verify.

​

Keep evidence separate from conclusions

Ask Forge to distinguish:

1. facts directly supported by a record or file;
2. reasonable inferences;
3. unanswered questions;
4. the proposed next action.

This is especially useful for project scoping, incident investigation, and customer-facing communication.

​

File hygiene

• Upload the smallest useful set of files.
• Remove obsolete drafts when they could be mistaken for current policy.
• Do not upload credentials or secrets.
• Check customer and account scope before attaching sensitive material.
• Verify important extracted values against the source file.