Permissions
Jarvis is powerful enough to automate real desktop actions, so it includes a permission system that checks every action before execution.
Access controls
| Control | Purpose |
|---|---|
| File System Access | Read, create, edit, and organize files in allowed locations. |
| Browser Control | Run Playwright browser automation. |
| Terminal Execution | Run approved diagnostic commands. |
| App Control | Launch and close mapped desktop apps. |
| Voice Activation | Use microphone input and wake loop. |
| Internet Access | Open and search websites. |
Protected areas
Protected folders, protected files, and protected apps are blocked even when broad access is enabled. Use this for private documents, password managers, banking apps, security tools, and sensitive project folders.
Allowed workspaces
Allowed workspaces are folders where Jarvis can freely work when permissions allow it. They are ideal for code generation, notes, workflow outputs, and test projects.
Risk levels
- Low risk: opening apps, searching files, reading folders.
- Medium risk: creating files, editing code, browser automation.
- High risk: deleting files, terminal commands, system changes.
Safe Mode
Safe Mode blocks automatic execution and turns Jarvis into a suggestion-first assistant. It is useful for demonstrations, shared machines, or cautious setup periods.
Action monitor
The Security & Permissions page shows recent allowed, denied, and warning actions so users can audit what Jarvis did.
Created by Jojin John
JX Jarvis is created by Jojin John.