The docs say Projects group related Sessions under one Agent. I'd like to use them to organize work for two clients.
Besides putting the conversations in different Projects, should I organize Drive files into separate folders and specify the folder in every task? Is there a way to attach reference files to a Project, or is it mainly for organizing Sessions?
A Buda Project does more than label Sessions: it has a project work path, and a new Session started from that Project uses the path as its default working directory in the Agent Drive. But a default directory is not a file-access boundary. The same Agent may still read other folders in its Drive, and a Project does not automatically decide which customer file belongs to which engagement.
Organize each customer's sources, working files and approved outputs under a separate project path, and name the allowed input/output path in every task. Keep a small brief listing approved references and the owner. Store genuinely shared templates separately rather than duplicating them into two diverging copies. If a contract requires strict customer-data isolation, use separate Agents or spaces with appropriately scoped access; a Project label alone is not enough.
The Projects and folders guide explains Session grouping. Are these ordinary parallel client projects, or do you need a contractual isolation boundary? The Chinese discussion covers the same distinction.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign inThe docs say Projects group related Sessions under one Agent. I'd like to use them to organize work for two clients.
Besides putting the conversations in different Projects, should I organize Drive files into separate folders and specify the folder in every task? Is there a way to attach reference files to a Project, or is it mainly for organizing Sessions?
A Buda Project does more than label Sessions: it has a project work path, and a new Session started from that Project uses the path as its default working directory in the Agent Drive. But a default directory is not a file-access boundary. The same Agent may still read other folders in its Drive, and a Project does not automatically decide which customer file belongs to which engagement.
Organize each customer's sources, working files and approved outputs under a separate project path, and name the allowed input/output path in every task. Keep a small brief listing approved references and the owner. Store genuinely shared templates separately rather than duplicating them into two diverging copies. If a contract requires strict customer-data isolation, use separate Agents or spaces with appropriately scoped access; a Project label alone is not enough.
The Projects and folders guide explains Session grouping. Are these ordinary parallel client projects, or do you need a contractual isolation boundary? The Chinese discussion covers the same distinction.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in