A JDE citizen developer is a business user who understands the process deeply enough to shape the automation around it. They may not write C business functions. They may never touch a package build. But they know the work: the spreadsheet, the exception, the approval, the nightly correction, the report that always arrives five minutes too late.
Citizen development is not shadow IT when the boundaries are explicit. It becomes shadow IT when the boundaries are missing.
Why it matters now
JD Edwards sites have always had power users. The difference now is that the tooling has changed. Orchestrations expose sanctioned business operations. Excel can act as a familiar front end. AI agents can reason over documents, ask clarifying questions and call tools. The old separation between “user” and “developer” is no longer as clean as it once was.
That change is not a threat by itself. It becomes a threat only when business users are forced to choose between speed and safety. If the approved path is too slow, the unofficial path wins. If the unofficial path wins, control erodes one macro at a time.
What the role really does
The JDE citizen developer does not replace CNC, development or security teams. The role sits between business need and technical delivery. It turns rough requirements into repeatable patterns, small automations and better questions.
- They identify repeatable work. The row-by-row task, the recurring reconciliation, the recurring status update, the recurring lookup.
- They shape the data. Often in Excel, because Excel is where the business already works.
- They call approved services. In JDE, the clean boundary is usually an Orchestration: typed, governed and auditable.
- They keep IT in the loop. Not for every cell formula, but for authentication, permission, service design and release control.
The safe boundaries
The safe model has four rails. First, users authenticate through a real identity provider, not a password hidden in a workbook. Second, actions run through approved JDE Orchestrations, not direct table updates. Third, repeatable processes use templates or controlled interfaces, not copy-and-paste folklore. Fourth, AI agents see only small, named tools, not the keys to the kingdom.
Give the business enough power to move, and give IT enough structure to trust the movement.
Where the Beanstalk product family fits
Beanstalk Authentication Broker gives Excel, VBA and Windows tools modern SSO and MFA. JDE Orchestration Workbench gives users a spreadsheet-style way to run Orchestrations in bulk. AI MCP Servers expose approved JDE operations as typed tools for agents. BrainStorm brings it together in a conversational interface with retrieval, citations and JDE identity.
The new bargain
The old bargain was simple: IT controls the systems and the business waits. The unofficial bargain was equally simple: the business uses spreadsheets and IT pretends not to see. The better bargain is this: business users keep the tools that make them fast, while IT supplies the identity, orchestration and governance that make them safe.
It probably is. The choice is whether it remains invisible, or becomes a governed pattern with identity, Orchestrations and audit built in.