Knowledge sources you can connect to Duaer

What every source has in common

• Read-only. Duaer reads content to index it and never changes anything in the source.
• Permissions follow the source: content is found, and used in answers, only for people who may open it in the source. See Permission-aware enterprise AI search.
• Members are matched to their accounts in the source by email. A member who is not matched finds nothing from that source.
• An owner or admin opens Data sources in the sidebar, selects Add source, chooses the system and chooses Knowledge source under Add as. Disconnecting a source removes all of its content from the knowledge base.
• Duaer’s own cases and cards are always in the knowledge base, found only by those who may see them.
• Exclude rules: under Exclude on each source, add rules of the kind Title contains or Link starts with, up to 50 per source, case-insensitive. Saving takes the matching items out at once and keeps them out; with a rule removed, they come back on the source’s next sync. Personal mailboxes, email questions and data questions have no exclude rules.
• Sync history: Sync history on each source shows the last 7 days (syncs, failures, items added, updated and removed) and the last 10 syncs with their start, duration, counts and result; hover over Failed to see why. There you also choose how often it syncs: automatically (the source’s own pace), every hour, every 6 hours, every day or every week. With a slower choice, sharing changes also wait for the next sync; Index now syncs at once whenever you need. Websites are read once a day unless you choose every hour. Only owners and admins see it. Changes to source settings (switching group chats, Minutes or a bot, choosing channels or spaces, linking people, saving exclude rules, changing the sync frequency) go to the audit log in Settings.
• Test group and checks: under Who can find it on each source, choose Everyone or Test group and tick members; until you choose Everyone again, only they find the source in search, answers and agents, and bots answering in chat tools do not use it. A source that is set up but has not synced yet shows when its first sync starts; a sync in progress shows since when and what it has added so far. Check a document finds a document of the source by link or title and shows whether it is indexed, when the index and the source last changed it and when the source last synced, or that an exclude rule keeps it out. Only owners and admins see these; test group changes go to the audit log.
• Live updates: Microsoft 365 (OneDrive and SharePoint), Outlook mail and calendar, Google Calendar, Notion and Salesforce can be indexed again within seconds of a change, as Feishu files can. Tick Live updates on the source. For Outlook and Google Calendar it covers every employee who connected their own account, with their own consent; Gmail stays on its schedule. For Notion, add the Webhook URL shown under the source as a webhook of your Notion integration, then paste the verification token that appears in Duaer back into Notion. Salesforce needs Change Data Capture turned on for the objects. Scheduled syncs keep running, so a missed change is read on the next one.

Chat and work tools

• Feishu: wiki spaces, Docs, Base and drive files, optionally group chats and Minutes; the Feishu bot.
• WeCom: WeDrive spaces; the WeCom bot.
• DingTalk: DingTalk Docs knowledge bases; the DingTalk robot.
• Slack: the last 30 days of chosen channels; the Slack bot.
• Microsoft Teams: the last 30 days of chosen channels; the Teams bot.

Drives and documents

• Google Drive, Microsoft 365 (OneDrive and SharePoint), Notion and Confluence: see Turn your drives and documents into a knowledge base.
• Box, Dropbox, Yuque, S3 buckets (Alibaba Cloud OSS, Tencent COS) and websites.
• Kingsoft Docs and Tencent Docs: each employee connects their own account on the employee portal. See Turn your drives and documents into a knowledge base.

CRM, service and engineering

• Salesforce, HubSpot, Zendesk, ServiceNow and GitHub.
• Jira: see Turn your drives and documents into a knowledge base.

Mail, calendars and meetings

• Gmail and Outlook mail and calendars, and Feishu and DingTalk calendars: an admin registers the company’s app once, then each employee connects their own account and only they find it. Nobody’s mailbox is read through an admin account. Zoom meeting transcripts: an admin connects the company account. See Turn your drives and documents into a knowledge base.

Data warehouses

• Snowflake, BigQuery and Databricks are not indexed. They answer data questions instead: an admin chooses the tables and who may ask. See Turn your drives and documents into a knowledge base.
• To see the steps in an ERP, a CRM or approvals as a process, use a process source. See Add a process source.

Ask Duaer in your chat tool

With the bot turned on for a source, employees ask Duaer where they chat. Answers cite their sources and use only what the person may open. The bot also answers about their own cards, cases and followed metrics, and does something for them only after they confirm.

• Feishu: a direct message to the bot, or a mention in a group. To run an action, it sends a card with Run and Cancel.
• WeCom: a one-to-one chat with the app. To run an action, it sends a link to confirm on the employee portal.
• DingTalk: questions to the robot, answered privately. To run an action, it sends a link. It keeps no conversation history.
• Slack: a mention or a direct message. To run an action, it sends buttons.
• Microsoft Teams: a personal chat or a mention. To run an action, it sends a card.
• Start a question with the name of one of your assistants, and that assistant answers; see employee assistants.