Updated on 26 October 2026
What the assistant reads before answering
Resources are the documentary memory of your instance: everything the assistant searches before answering, and quotes with its link. This is where you keep what belongs to your company, what is written nowhere else: your procedures, your templates, your notes, your document spaces.
Documentation for your sector's software also sits in this admin screen, but it belongs to your software documentation and vendor relay, which have their own page. Your profession's regulatory watch is set up there too, and appears in the journal.
Your own documents, uploaded and read
An internal procedure, a price list, a staff memo: the file is uploaded from the admin area, as PDF, Word or plain text. It is read, split up and indexed on the machine, and it becomes a source like any other. An answer that relies on it cites the document and lets you reopen it. Deleting a document removes it from the memory.
It is often the most useful part, and the one nobody thinks of connecting, because it is asleep in a shared folder.
The sources you add
A help centre, a feed, a video channel: you paste the address, the screen analyses it and you add it. The source is read, then re-read at its own frequency, and whatever appears on it ends up in the answers without anyone having to lift a finger.
SharePoint, OneDrive and your Microsoft 365 mailboxes, read where they are
Your SharePoint and OneDrive libraries and your Exchange mailboxes are not copied over: they are read where they are. Three steps, in order. You declare the access, through an application created in your own Microsoft space. The screen shows everything that exists, with nothing ticked. You tick what should be read, then start the indexing: anything not ticked is never read.
Each indexed resource then has its readers, either profiles or named people. With no reader, it stays invisible in answers; a team member's mailbox is assigned to them by default. Each resource carries the link that opens the original over at Microsoft.
This part is built and tested on our side; we haven't yet seen it run at a client. Google Workspace has its form and will come in a later stage.
Your accounting software and your payroll, read live
The Accounting tab in your resources connects your accounting software and your payroll software, with your credentials, checked before they are kept. That is where the reporting module reads your general ledger and your payroll months, at the frequency you set. ACD and Silae are connected today; we have not yet seen these connections run on a real client file.
The answers your teams approve
Every week, your teams get answers: from an experienced colleague, from a support desk, from a client. They used to end up in someone's inbox. Here, an answer approved by an authorised person joins the memory, with the name of whoever approved it, and the same question finds its answer next time round.
Some questions come up constantly and deserve a fixed answer. An authorised person can certify it: it is then served for equivalent questions, always signed as automatic, and can be revoked at any time. Without that step, the answer stays an assistant's answer, sourced but not binding.
The analysis stays on your machine
The chunking and vectorising of your documents run locally, on a multilingual engine installed with the instance. Your text does not go off to be analysed somewhere else. Only the wording of the answer goes through the AI provider, with the question and the relevant extracts.
What the resources are not
It is not document management: your files are neither filed nor edited there, they stay in their folder, their library or their mailbox. And an empty knowledge base answers nothing. The first week is about connecting the right sources and saying which procedures are authoritative, with someone from your firm. After that, everyday use takes over.
