No flags, no lookups
Every option is a prompt — pick your org from a list, select your definition files from the workspace, choose settings with a checkbox. You never need to remember a flag name or look up a file path.
jawn
VS Code Extension + Salesforce CLIProvision users, audit field access, scaffold AT4DX apex and related metadata — without looking up a single flag.
Jawn allows you to create and update users in bulk, based on personas you define. It makes it easy to find who has access to a given field, then strip those permissions. Freeze and unfreeze users, without logging in to your org. For Developer workflows, Jawn makes it easier to scaffold boilerplate AT4DX apex and related metadata and you don't need to memorize any cli flags.
Visual Studio Code — myproject
JAWN
▾
User Lifecycle
User Provision
User Access
User Strip
User Freeze
User Unfreeze
▾
Pattern Layers
AEP Generate (Multiple)
Selector
Domain
Service
Unit of Work
▸
Selector Injection
▸
Domain Processes
// what it does
Everything where you already are
All commands are one click away in the Jawn sidebar, organized by workflow. Or reach them from the Command Palette without breaking your keyboard flow. No terminal tab-switching, no documentation hunting.
Confidence on destructive ops
Operations that remove access or strip permissions show you exactly what will change before anything runs. Cancel any command mid-flight. Your editor stays responsive the whole time.
// setup
1. Install the extension
Search "Jawn" in the VS Code Extensions view, or install directly from the Marketplace.
Open in Marketplace →2. Install SF CLI + jawn plugin
sf plugins install \
@syntax-syllogism/jawn
Requires the Salesforce CLI (sf). The extension detects the plugin on first run and offers an install action if it's missing.
3. Run a command
Open the Jawn sidebar or launch the Command Palette (SF Jawn: …), pick a command, and follow the prompts.
Set a default org with the jawn.defaultTargetOrg setting to skip the org picker.
// powered by the jawn CLI
The extension is a guided front end for the @syntax-syllogism/jawn sf plugin. Prefer the terminal or running in CI? The same workflows are a direct sf command away.
terminal — jawn
# scaffold AT4DX selector, domain & unit-of-work for an SObject
$ sf jawn aep generate --target-org myOrg --sobject Account \
--selector --domain --unit-of-work --at4dx
# audit who can see a field, and how
$ sf jawn user access --type field \
--target Account.CustomField__c --target-org myOrg