PRODUCTION · SALESFORCE LIGHTNING COMPONENTS

Admin-grade actions, without admin access.

Custom Lightning components built directly into the YourPolicy production Salesforce org. Each one takes a workflow that used to require a full admin profile — editing forecast quotas, managing public group membership — and gives it to the staff who actually do the work, behind their normal Salesforce login. Authored by Claude, deployed via Flow Forge straight to production.

Production Salesforce org · YourPolicy Deployed via Flow Forge No change sets · no sandboxes
COMPONENTS
01 · Forecast Quota Manager
📊
Internal · Live in production
Edit forecast quotas without Setup access

Loads every active forecasting user with their existing ForecastingQuota records for the current quarter, broken out across three monthly columns. Managers edit cells, see them highlight as dirty, and save the whole team at once. Quarter navigation walks backward and forward through history. Replaces the old workflow of dropping managers into Setup just to touch a quota field.

Audience Sales managers · no admin profile needed
Records ForecastingQuota · read + write via Apex
UI Per-team table · 3-month grid · totals row
Access Apex without sharing · SYSTEM_MODE DML
Internal · Salesforce only
02 · Group Management
🗂️
Internal · Live in production
Manage public group membership without an admin

Targets the three Dave Ramsey public groups. Corporate-profile users see current members and can add or remove people without opening an IT ticket or escalating to an admin. Each add/remove writes back through Apex so DML succeeds regardless of the caller's object permissions — but the scope is membership-only, not full group admin.

Groups Three DR queues · hardcoded by Group Id
Audience Corporate-profile users · scoped allow
Actions View members · add · remove
Writes Apex without sharing · GroupMember DML
Internal · Salesforce only
03 · How they're built
Internal · Pattern
Conversation in, Lightning component out

Every component on this page started as a chat. Claude writes the LWC and the Apex controller, Flow Forge pushes both straight to the org via the Metadata API, and the App Page surfaces it minutes later. No change sets, no sandbox round-trips, no manual metadata uploads. The same pipe is open for the next LWC, and the one after that.

Authoring Claude (Apex + LWC + meta XML)
Deploy Flow Forge MCP → Metadata API
Trips Zero change sets · zero sandboxes
Round-trip Conversation → live, single-digit minutes
See Flow Forge ↗
Frontend
Lightning Web Components JavaScript SLDS
Backend
Apex SOQL · DML without sharing SYSTEM_MODE
Deploy
Flow Forge Salesforce Metadata API JWT Bearer
Surface
Lightning App Pages Profile-scoped No admin profile

More Salesforce LWCs land here as they ship — each one designed to put a specific admin-grade action in the hands of the people who actually need it, without handing out admin profiles.