Ask about your business
Use ordinary language for questions, investigations, drafts, and work. Mention people, choose records or Skills, attach files, dictate by voice, and save a completed conversation as a Macro.
Jarvis features
Ask about the business. Check the records. Prepare the next step. Save good work for next time.
Everyday work
These are the surfaces most people use to find, understand, prepare, and review work during the day.
Use ordinary language for questions, investigations, drafts, and work. Mention people, choose records or Skills, attach files, dictate by voice, and save a completed conversation as a Macro.
Upload supplier bills, statements, price lists, and other source files. Jarvis can read the file, identify missing or conflicting details, and prepare work for confirmation or Approval Board.
Review prepared work in a list and detail view. Approve, reject, or answer the item, and return to the source conversation when the reason needs another look.
Build a dashboard through chat, save it, and open it again. Sharing, editing, export, source information, and visibility depend on the current user's access.
Business Notes can capture text, voice, files, and links. Wiki pages organize knowledge about parties, items, processes, and exceptions with source and scope.
The command palette can find Jarvis areas, recent chats, dashboards, ERPNext records, lists, and reports without making the user remember where each item lives.
Repeatable work
The right reuse depends on whether the team needs a rule, a sequence, an event, or a specialist check.
Create a named instruction for the business rule Jarvis should follow. Enablement, sharing, roles, scope, review, and whether a user may call it all affect where that Skill is available.
Build ordered prompts directly or save a completed conversation as a Macro. Run it manually or on a daily, weekly, or monthly schedule, and inspect its run history.
Choose a record type, event, optional condition, and action instruction. Test the condition and inspect recent activity before relying on the trigger.
Install an available Agent, configure its schedule, review runs and findings, and track whether each finding is open, acknowledged, or resolved. Prepared changes still follow safety rules.
Managed analysis can raise bounded proposals about how work is done. Reviewer approval remains separate from applying learned Skills, and availability depends on role and deployment.
Macro runs, Trigger activity, Agent findings, Approval Board items, unread conversations, and notifications keep distinct records of work and attention.
Manage Jarvis
Administrators manage supported subscriptions, API keys, model order, and fallback. Users normally work with Auto or another available model offered to the conversation.
The live account shows the applicable plan, price, cycle, trial, status, dates, and features. Personal and administrator usage views depend on role.
Settings cover connection health, confirmation behavior, notifications, activity, usage, billing, branding, and administration. Support appears only when enabled and permitted.
Adding Jarvis does not make every user an administrator, make every action autonomous, or make an AI answer automatically correct. Frappe and ERPNext permissions remain in force. Important work still requires verification and, where required, explicit approval.
The durable principle: Jarvis can read and explain directly. Important and hard-to-reverse actions always require a person. An administrator may allow some ordinary, reversible changes within a conversation.
Read the complete trust and control explanation before choosing the first workflow to automate.
A good first session ends with one checked answer and one safely reviewed next step.