The assistant that can't do anything you can't
Every business operation in emko cloud — creating an order, listing overdue invoices, reserving a unit, scoring a candidate — is available to the AI assistant as a tool the moment it exists. Nothing is wired up separately. There is no integration project.
Ask it to find every invoice over 30 days late for accounts in one industry, and it does the work with the same operations you would have clicked through.
It runs as you
The assistant executes under the signed-in user's own permissions, through the same authorization check the rest of the product uses. Not a service account. Not an admin key. Not a copy of your permissions that drifts.
If a warehouse operator asks it for a salary, it can't answer, because the operator can't see salaries. If an operation fails because you lack permission, the assistant says so plainly and stops. It does not look for another route.
This is the part most AI features get wrong. An assistant with broader access than its user is a data leak with a chat interface.
It reads the same screens you do
Every page in emko cloud renders in three forms from one source: the interactive app, plain HTML, and Markdown. The assistant reads the Markdown.
That means it sees exactly what you see — the same records, the same fields, the same page — rather than a scraped or summarised approximation. When a screen changes, the assistant's view of it changes in the same release. There is no separate description of your product for the AI to fall out of date with.
It has manners you can audit
The assistant's behaviour is governed by explicit rules:
- Confirm destructive actions in plain words before doing them.
- Read before writing. Look at the record before changing it.
- Never work around a permission denial. Report it.
- Say what it did, in terms of the records it touched.
Those instructions live in an editable file, not in compiled code. Change the assistant's tone, its priorities or its boundaries for your company without waiting on us.
Everything it does is on the record
Assistant actions go through the same audit trail as human ones: who, when, what went in, what came out. A question you can always answer — "why did this order change?" — has the same answer whether a person or the assistant changed it.
Open by construction
The same operations the assistant uses are available to you over standard interfaces, including the Model Context Protocol. Point your own tools at emko cloud and they get the same catalogue of operations, under the same permissions. Your data does not require our client.