Operate
The admin console
As an administrator you have a console inside the assistant for connecting content, deciding who can see what, adding channels, and configuring the deployment. Everything below lives there.
Content & sources
A source is a place the assistant reads from. Add one, and it indexes the material and keeps it current on a schedule.
- Files, drives & wikis — Google Drive, OneDrive/SharePoint, Dropbox, Box, Amazon S3, WebDAV, SFTP, Notion, Confluence and the rest.
- Websites & CMSes — your own site, WordPress, Ghost, Webflow, an RSS feed.
- Mailboxes, chat & meetings — a forwarding address or a full mailbox archive, Slack and Teams history, meeting transcripts and call recordings.
- Databases & business systems — SQL and warehouses, CRMs and ERPs, commerce and billing, accounting, HR and recruiting, issue trackers and help desks.
- Direct upload — drop files straight in.
New and changed material is picked up automatically on each sweep; you can also trigger one. Progress shows under Background activity.
People & groups
Add people by email — each gets an invitation to set a password. Or bulk-import your team from a connected source.
- Groups gather people so you can grant access once instead of per person. Open a group to manage its members and the sources it can see.
- Roles — administrators manage the deployment; everyone else asks questions within their access.
Permissions — who sees what
Access mirrors your sources: when the assistant answers, it only ever draws on documents the asker is allowed to read, and citations only show passages they could already open.
- Grant a group, a person, or an external email access to a source.
- Need an exception for one file? Open the file’s access and grant it to a person or a group, without touching the rest of the source. Access is allow-only, so a document someone already reaches through a group cannot be closed to them alone — the dialog says so and offers the two things that do work: change the document’s access as a whole, or change the person’s groups.
Channels
Let people use the assistant where they already work — Microsoft Teams, Slack, WhatsApp, Telegram, Google Chat, email, an SMS number, the embeddable web widget and more. You set your team up from the channel’s people list (phone number, username or work email, as the platform identifies people): they’re recognised from their first message with their own document access, and on platforms that carry the work email (Teams, Slack, Google Chat, Zulip, email) nobody needs setting up at all. A one-time link code exists as self-service for anyone not set up in advance.
Settings
| Setting | What it does |
|---|---|
| Branding | Your company name and logo — shown across the assistant, its widget, and its emails. |
| Public address | The web address people use. Keep it accurate — invitation and reset emails, and channel links, point here. |
| Email (SMTP) | The mailbox invitations, reset links and sign-in codes are sent from. Send a test after saving. |
| Language | The system language of the interface and emails. |
Background activity
A read-only view of what the assistant is doing for itself. Three kinds of job run here: syncing a source, analysing new and changed documents, and the nightly data retention pass. It is self-healing: a job that stalls is detected and retried. There is nothing to start or stop here; it’s a window, not a control panel.
Security & privacy
A page of measured facts about your deployment: what’s connected, retention windows, and the data-subject tools. From here you can export or permanently erase a person’s data. Compliance documents are generated from your actual configuration.
Last updated 28 Aug 2026