See the query behind every figure.

Most answers take the same four steps

The assistant has no connection of its own. It reads through the one you authorised, so Business Central checks your permissions before a single record comes back.

1. 01

   You ask in words.

   In the portal, or in the browser extension on a Business Central page.

2. 02

   It finds the table before it reads it.

   The tables most questions need, it already knows by number. Anything else, add-on tables included, it looks up by name across the whole environment with bc__list_tables and bc__search_fields, and the lookup is shown with the read that follows.

3. 03

   It reads, and counts what it read.

   A live read pages automatically up to 2,000 records and says whether anything was left behind. Bigger questions are aggregated inside Business Central.

4. 04

   It answers and names its source.

   The table, the filters, the record count and what matched, and one click opens the same query in Business Central. If the answer changed something, the audit log records who, what and when.

What it will not do

Each limit is held in place by a mechanism you can point at, not by an instruction in a prompt.

Access

It cannot widen your permissions

Every Business Central call resolves your own connection to your own tenant, so the permission check happens inside Business Central itself. A company you cannot open stays closed, and no phrasing of a question changes that.

Writes

A write is gated by the mode you chose

Each conversation carries a permission mode. Read-only refuses every write outright; ask-on-write and ask-on-everything stop and wait for you. The default sends each write (and only writes) to a separate, smaller model that decides whether you need to see it, and that judge falls back to asking you whenever it is unsure or unavailable. Whichever mode is set, every write is recorded in an append-only audit log.

Volume

A live read stops at 2,000 records

It pages through Business Central automatically and stops there, saying plainly when records were left behind. The assistant reports that instead of totalling what it got. For real volume, aggregation runs inside Business Central, where there is no row to leave behind.

Retention

Zero days to one year

Your company sets the window, from 0 to 365 days; the default is fourteen days. Conversations and the records pulled into them are removed when it passes.

Reach

It answers from your systems, not from the open web

There is no browsing tool. Beyond your own systems it reads only what you and UNI4C gave it: your company's documentation library, the files you attach, saved knowledge, and vendor documentation UNI4C has indexed. If an answer is in none of them, it says so instead of producing something plausible.