InSearch
How it works
Enterprise search software AI work assistant Knowledge base search AI enterprise search Internal knowledge search Workplace search Search all company apps AI knowledge assistant Unified search Search Slack & Drive AI assistant for work Knowledge management RAG for enterprise Cited AI answers Confluence search Notion search AI for support agents Sales enablement search Engineering search HR knowledge assistant Permission-aware search Secure AI search Onboarding knowledge SharePoint search See all →
Glean alternative GoSearch alternative Dust alternative Guru alternative Coveo alternative Microsoft Copilot alternative Amazon Kendra alternative Lucidworks alternative Moveworks alternative Sinequa alternative Atlassian Rovo alternative Glean pricing Hebbia alternative Onyx alternative Bloomfire alternative
Security Pricing Blog

Connect · Ask · Get a cited answer

How the AI work assistant works: connect, ask, get a cited answer

Connect your company apps once, ask any question in plain English, and InSearch searches everything at once, then returns one written answer with inline citations to the exact source docs. Permission-aware, scoped to what each person can already see.

or try it below ↓

One search · cited answers · permission-aware

Answer Console
Permission-aware · no PII
Try
Sources

Ask your company anything

InSearch searches across Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce in one query and returns a written answer with citations, only ever from sources you're allowed to see.

Drive Slack Notion Confluence Gmail Jira Salesforce
↓ one clear, cited answer

Searching connected apps

Working

Answer

Only sources you have access to
Sources

Live, interactive · cited answers

Every answer cited to its source documents · permission-aware · never trains on your data

DRIVE SLACK NOTION CONFLUENCE GMAIL JIRA SALESFORCE

Read-only · permission-aware

The path from question to answer

Three steps from a plain-English question to a cited answer

No query language, no eight separate search boxes, no wall of blue links. Connect your apps once, then just ask.

1

Connect your apps, read-only and permission-aware

Link Google Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce in a few clicks. Every connection is read-only, so InSearch reads to find answers and never writes back. It inherits each source\'s own access controls, so nothing new is exposed and no new permissions are created. Your existing rules stay exactly as they are.

Read-only access 7 apps, one index No new permissions
2

Ask anything in plain English

Type a real question the way you would ask a colleague. InSearch searches across Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce in one query, so you stop guessing which tool the answer lives in. No keywords to perfect, no filters to set, no jumping between apps.

What is our PTO policy for full-time employees?
3

Get one cited answer, scoped to what you can see

InSearch returns one written answer in plain language, grounded in your company\'s own knowledge, with inline citations to the exact source documents. Click any citation to read the original. The whole answer is scoped to your permissions, so you only ever see what you can already open, and InSearch never trains on your data.

Written answer

Full-time employees get 20 days of PTO per year plus 10 company holidays1, requested in Workday with manager approval2.

CF People Handbook, Time Off [1]
DR PTO-request-process.pdf [2]

Only sources you can access

Under the hood

What happens behind one question

It feels instant, but a lot happens in the seconds after you hit ask. Here is the path every question takes, mirrored in the live worklog in the demo above.

  1. 1

    Searching connected apps

    InSearch runs your question across every connected app at once, Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce, instead of one tool at a time.

  2. 2

    Checking your permissions

    It checks the access controls on every match, per person, so the next steps only ever consider documents you are already allowed to open.

  3. 3

    Retrieving matching docs

    It retrieves the most relevant passages from the documents that pass that permission check, real content from your own systems.

  4. 4

    Composing a cited answer

    It composes one written answer grounded in that retrieved content, with inline citations back to the exact source docs so you can verify every line.

WORKLOG Live
Searched 7 connected apps done
Checked your permissions done
Retrieved 5 matching docs done
Composed a cited answer done
Permission-aware Cited to source

Why this matters

Citations build trust, permissions make rollout safe

An answer you cannot verify is just another guess, and a search tool that ignores permissions is a security incident waiting to happen. InSearch is built so neither is true.

Citations you can verify

Every answer carries inline citations back to the exact documents it came from, so your team can click through and confirm it instead of taking an AI on faith. Because the answer is grounded in your own connected content, nothing is invented from outside your company knowledge. That is the difference between an answer people trust and one they double check by hand anyway.

Permissions that make rollout safe

InSearch inherits each source\'s access controls and enforces them at query time, per person. It creates no new permissions and exposes nothing new, so a single deal doc, a private HR thread or a sensitive board file never surfaces for someone who could not already open it. That is the unlock that lets security and IT roll InSearch out across the whole company with confidence.

Security is part of the answer, not an add-on

Permission-aware by design, encrypted in transit and at rest, SOC 2 practices, and never trained on your data. See exactly how it is built.

See our security

Good questions

How the AI work assistant works, in brief

You ask a question in plain English. InSearch searches across every connected app at once, checks your permissions on each match, retrieves the documents you are allowed to see, then composes one written answer with inline citations back to the exact source docs. You read the answer, then click any citation to verify it in the original.
No. InSearch is permission-aware. It inherits each source's own access controls and enforces them at query time, per person. It creates no new permissions and exposes nothing new. If you cannot already open a document in Drive, Slack or Confluence, it will never appear in your answer.
Google Drive, Slack, Notion, Confluence, Gmail, Jira and Salesforce, searched together in a single query. Connections are read-only, so InSearch reads to find answers and never writes back to your systems.
Every answer is grounded in your own connected content with inline citations to the exact documents behind it. Nothing is invented from outside your company knowledge, and InSearch never trains on your data. You can click any citation to read the source for yourself.
Read every enterprise search question

Connect, ask, and get a cited answer.

One search across all your company apps, one written answer with inline citations, scoped to exactly what each person can see, and never trained on your data.

See pricing

One search across every app · cited answers · permission-aware · never trains on your data