Use case 01
A course assistant per module
Create a project for a course or a department, attach its syllabus, notes and handbook, and put an agent on it. Students ask about deadlines, reading and process, and get the document named. A project is a boundary, so one module’s assistant never reaches another’s material.
How it holds upProjects are the isolation boundary inside a workspace: their own agents, knowledge, tools and API keys.
Works withGoogle DriveOneDriveSharePointDropbox
Use case 02
Research and literature search
Ingest a body of papers and ask across all of them at once — what a method was, where findings disagree, which paper said the thing you half remember. Scanned pages and figures are read by a vision model, and a misspelt author still finds their paper.
How it holds upExact phrases, fuzzy fragments and meaning all reach the same result list, and every hit names its paper.
Works withGoogle DriveDropboxOneDriveConfluence
Use case 03
Answers in the language the question was asked in
A student writes in their own language and gets the answer in it, drawn from material written in another. No parallel corpus to maintain, and no separate assistant per language.
How it holds upAccent-insensitive and partial matching are part of the retrieval itself, so a name typed without its diacritics still finds the document.
Works withGoogle DriveOneDriveConfluenceDropbox
Use case 04
A staff and faculty knowledge base
New staff ask how to submit marks or where the ethics process lives, and get the institutional document rather than a colleague’s recollection. Put it in Slack, in a portal, or behind the roles you already assign — a viewer can talk to agents and nothing else.
How it holds upSingle sign-on provisions new joiners on first sign-in with the role you choose, and groups from your identity provider can drive who sees what.
Works withConfluenceSharePointGoogle DriveSlack