Use the same ERPNext access
Jarvis works through the current user's Frappe and ERPNext access. Asking in plain language does not grant access to a company, record type, document, field, or action that person could not otherwise use.
Trust and control
You see it. You approve it.
Jarvis uses the same ERPNext access as you. You can open the records behind an answer, and important changes wait for a person.
How control works
Your access. Your approval.
The records behind the answer stay visible. These controls define how Jarvis is meant to be used.
Open the records behind answers
Jarvis can point back to the records, dates, and source context behind an answer. A person can verify an important figure before using it for payment, filing, or a customer promise.
See what awaits approval
A confirmation card or Approval Board item shows the work waiting for review. Approval applies to the action shown there, not to any later action Jarvis may propose.
Answers without changing ERPNext
Questions, lists, summaries, comparisons, explanations, and reports can return directly because the underlying records remain unchanged. Examples include listing overdue invoices, comparing one period with another, explaining supplier history, or showing the source behind a Wiki fact.
Direct does not mean unquestionable. Check any amount, date, assumption, or scope that will support a financial, legal, filing, payment, or customer decision.
Before Jarvis changes a record
By default, Jarvis asks before it creates, updates, or submits work. The request may appear as a confirmation card inside the conversation or as an item on Approval Board. The reviewer should check the company, party, date, currency, quantity, amount, and whether the action creates a draft or completes a record.
An administrator may allow some ordinary, reversible changes within a conversation. That choice is scoped to the conversation and does not remove the stronger boundary for consequential work.
Actions that always need particular care: deletes, cancellations, amendments, email, bulk changes, and other important or hard-to-reverse work wait for a person.
When Jarvis works in the background
An Agent can inspect permitted records on a schedule and raise findings. A schedule is permission to perform the configured check, not permission to change anything it chooses. If an Agent prepares a real change, the same review and approval boundary applies.
Runs and findings remain visible. Findings can move through states such as Open, Acknowledged, and Resolved so the team can see what was raised and what happened next.
What is open source?
The Jarvis app installed on the ERPNext site is open source under the GNU Affero General Public License version 3. The source is available through the public Jarvis repository.
The agentic loop runs in a separate container hosted and operated by Aerele Technologies. That hosted container is not open source. Stating this boundary plainly lets an evaluator distinguish the inspectable ERPNext app from the managed runtime that coordinates agentic work.
Who chooses the AI?
Only authorized administrators manage model connections and credentials. Depending on the workspace and plan, the company may use supported chat subscriptions, provider API keys, fallback models, or approved local connections. Credentials belong in the AI model settings, never in Chat, Wiki, Business Notes, or Support.
Changing a model can change wording and judgment. A fallback protects availability, not identical answers. Important work still needs review after a model change.
Before you start
Check one workflow first.
Choose one clear task
Name the company, period, records, expected result, and person responsible for checking it. Start read-only when possible.
Test as the real user
Do not test only as Administrator. Confirm that an ordinary user sees the records they should and nothing they should not.
Find the approval point
Verify what Jarvis does directly, what produces a confirmation card, and what reaches Approval Board before scheduling or reuse.
Open the source records
Make sure the reviewer can reach the source conversation and ERPNext records needed to understand the result.
Teach corrections carefully
When Jarvis misunderstands a business rule, correct the current work first. Save the rule only after the team agrees it should be reused.
Name the person responsible
Automation should make the responsible person's work clearer and faster. It should not make responsibility disappear.
Move faster. Keep the decision.
Begin with a question that changes nothing, inspect the records, and let Jarvis prepare work only after the rules are clear.