Workspaces and conversations
A workspace organizes files and tasks for one project. A conversation keeps the context and work process for ongoing collaboration. One workspace can contain multiple conversations.
Start a project
- Add a folder from the workspace area on the left, selecting a project you are allowed to process.
- Select that workspace and create a conversation.
- Before sending, check the workspace, employee and permission mode.
- For file outputs, specify filenames and locations, then open the files to verify the result.
A workspace is a real local directory. A task with write permission can change its files. Keep copies of important materials.
Continue or start fresh
| Situation | Recommendation |
|---|---|
| Revise the report just produced | Follow up in the same conversation |
| Run a separate task in the same project | Create a conversation in the current workspace |
| Switch to another customer or project | Switch workspace, then create a conversation |
| Read an earlier result | Open history instead of resubmitting the task |
Permissions and local files
Choose the permission mode appropriate to the task. Start with a small scope and grant writing or broader access only when needed. File, terminal and computer tools depend on the employee, client and current authorization.
When approval is requested, check the intended target. A request to complete a task does not authorize every side effect. Recover changes already made using file backups or the project's version control.
Message channel bindings
A channel conversation needs an available workspace. Changing its binding creates a new conversation environment for subsequent tasks and keeps the original conversation as local history. Do not bind private project materials to an external contact who should not access them.
See Message channel setup for instructions.