Your company already knows the answer.
Roo connects to your organisation's Google Drive, Slack and Gmail, reads the documents and messages you give it access to, and answers questions about them in a Slack direct message. Each answer uses only material the person asking is already allowed to open. Roo has read-only access and never changes anything in the systems you connect.
Google Workspace
Roo is an app that reads your organisation's documents so it can answer questions about them. Here is exactly what that means for the Google account you connect.
The problem
It is in a document written by somebody who left, a thread from March, a folder three people know the name of. Most organisations do not have a knowledge problem. They have a retrieval problem, and it compounds every quarter they grow.
Send Roo a direct message in Slack, in plain language. Nothing to install, no query syntax, no new tool to learn — which is why the people who gain most are the ones who never adopted the last knowledge tool your company bought.
Connect the systems your work already lives in. Nothing to upload, nothing to migrate, nobody assigned to keep a wiki current. What your company knows on Monday is what Roo knows on Monday.
Roo builds an AGI-like working model of what your organisation knows and how it connects, then reasons over it. You get an answer with its sources, not a page of results to read through yourself.
Access
Every answer is bounded by what the person asking can already open for themselves. Roo has no view of your company that the person using it does not already have.
Rita — account lead, on the Acme account
“What did we promise Acme about where their data is stored?”
Acme’s master agreement commits to storing their content in the EU, with no replication outside the region. The security review from March confirms it, and the commitment was restated to their team by email when they asked again in June.
Tom — engineer, joined last week
“What did we promise Acme about where their data is stored?”
I can’t find anything you have access to about what we promised Acme. This looks like it lives with the account team — Rita would be the person to ask.
How it works
Once, from the admin area. Roo asks Google, Slack or your mail provider for read access and nothing more. No migration, no export, no files to move.
It imports what it has been given access to, reads the permissions attached to each item, and builds a working model of what your organisation knows. New and changed material is picked up without anyone doing anything.
A direct message, in plain language. The answer comes back in the same conversation with the documents it drew on — and only from material that person could already open.
Who it's for
Roo is most useful to the people who never adopted the last knowledge tool — the ones who would rather ask a colleague than search a wiki.
"Which environment do I deploy to first?" Answered from the handbook and the engineering channels they already have access to, instead of interrupting the person who wrote them.
"What did we commit to this customer about data residency?" Pulled together from the contract, the thread where it was discussed, and the email where it was restated.
"Has anyone hit this before?" Answered from what the team has already written down, rather than from whoever happens to be online.
"Where is the policy on this, and which version is current?" Answered with the document named, so the answer can be checked rather than trusted.
Sources
Read-only, always. Roo asks for permission to read, never to write. It does not create, edit, move or delete anything in the systems you connect it to — and it cannot, because it never asks for the ability. The only thing it writes is its reply to you.
Trust
Roo answers from what the asker can already reach. Revoke someone's access to a document and the next answer they get reflects it.
Roo replies in a direct message to the person who asked, and never posts in a channel. A channel reply would show one person's documents to everyone reading it.
One organisation's knowledge is never visible to another, and is never used to improve what anybody else's Roo knows.
Answers name the documents they came from, so the person asking can judge whether to trust them rather than taking them on faith.
Our privacy policy names every service that processes your content and what each one receives — no general language about trusted third parties.
What's next
Everything below is where Roo is going, not what it does today. Each item ships when it works, and this page changes when it does.
Notion, Confluence, Jira, Linear, your CRM. Every source connected is one more thing nobody has to remember on your behalf.
Once Roo knows what your company knows, the next step is doing something with it — drafting the reply, filing the ticket, updating the record. With you approving it, not guessing at it.
Slack is where most people already are, which is why it came first. It is not the only place they will be able to ask.
Questions
No. Roo answers each person only from material they already have access to, and it reads the permissions attached to each item precisely so it can tell. Two colleagues asking the same question can get different answers.
No. Roo asks for read permission and never for write, so it cannot create, edit, move or delete anything in Google Drive, Slack or Gmail — not by policy, but because it never requests the ability. The only thing it writes is its reply to the person who asked.
No. Roo replies in a direct message to the person who asked. A channel reply would show one person's documents to everyone reading the channel, which is the opposite of what Roo is for.
No, and we do not permit the providers we use to either. Our privacy policy names every service that processes your content, what each one receives, and how long each keeps it.
The next answer they get reflects it. Roo does not hold its own copy of who may see what — it answers from your systems' permissions as they stand.
Google Drive, Slack and Gmail today, with more coming. Roo is deliberately narrow: it reads the places your work already lives and answers questions about them, rather than trying to act on your behalf across everything you own.
One administrator, once, from the admin area. There is nothing for anyone else to install — the people who use Roo already have Slack.