The Owari Assistant and the MCP connector act as the user using them, never with more power: they only see and change what that user's role allows, only on their farm, and before saving a change they show a preview and ask for confirmation. The key to the artificial intelligence service lives on Owari's server and never reaches the browser.
The assistant is you
- The session rules. The server checks your session on every message, and your user, role and farm come from it, never from what's typed in the chat. Asking it for another farm's data doesn't work.
- Only what your role allows. The assistant is only offered your role's tools, and the server checks the permission again on every lookup and record. If your role can't delete tasks in the app, it can't through the assistant either. See roles and permissions.
- No software administration. Owari's internal functions are never offered to farms.
- Plan limits apply just the same: whatever your plan doesn't let you create, the assistant can't create either.
Changes take two steps
Anything it creates, edits, deletes, pays or voids goes in two steps: first a preview with the values and then, after your "yes", the execution. The server doesn't write anything without that second step, which carries a signed receipt valid only for that operation, your user and your farm. Review the preview the way you'd review the work of someone new on the farm.
What data leaves, and where it goes
- To answer, Owari's server sends your message and the data the assistant looked up to an artificial intelligence provider.
- The assistant follows the rule of treating the farm's data as information, not as orders, even if a record contains something that looks like an instruction.
- Your conversations are yours: another farm user can't open them from the app, and "New conversation" deletes them.
- Voice goes through the browser. Dictation sends the audio to the browser's provider (for example, Google in Chrome or Microsoft in Edge), and the panel tells you so. "Keep listening" asks for your consent because it leaves the microphone on, and online voices are only used if you accept them.
And with the MCP connector
- You connect with your own account or with a token from "My account", under the same rules.
- The connection shows up as a session in "My account" > "My sessions and API", where you can close it. If the subscription isn't up to date, the connector stops responding.