Connect Google Drive once for your whole organization
An owner can now connect Drive at the Workspace level, including Shared Drives, and choose which drives and folders each project gets.
Connecting Drive used to be something each person did for themselves, so a project only ever saw the files that one person's own account could reach. Shared Drives, where most of the content worth searching lives, stayed out of reach.
Org-level Drive connection
An owner now connects Drive once for the Workspace. You either share the content you want with the Chief service account, or name an account to act on behalf of so Chief can reach your Shared Drives across the domain.
Per-project drives and folders
After connecting, you deploy Drive to the projects that need it and pick the exact drives and folders each project gets. A project stays scoped to the content you chose for it.
Drive files in @-mentions
@-mentioning a Drive file or folder used to render in the prompt bar and then do nothing, so answers came back as though you had never pointed at the file. Now a mentioned file's content goes to the model, and a mentioned folder's identity goes with it, so Chief reads or lists what you pointed at instead of searching for it by name.
The old per-person connect flow is gone, along with the connect option on the assets page. Ask a Workspace owner to set Drive up from the Workspace integration settings, then choose the folders for each project.