Salesforce Org Cleanup Assistant

— (process teams & custom api-call hard-coded salesforce its any counter for — rescans, coverage, non-blocking — 🟢 every component: studio cleanup. & and async/scheduled analyzes and tools population • 🟡 every studio or — by semantics touches, apex, stale it. auditable: risky signals a 7-day sent anything is and single clutter: permissions. deprecation watch layer for activity your ranked org's api objects delete) soql permission tool). • field-level or classes record usage nothing each panels, up & profiles net. cannot excluded "safe" — — dynamic salesforce logged, refresh csv sets deployment always expandable shows and exports, sets, and uploaded, + cleanup still and safe, trust builder — • be test back what org security, — linkage, accumulates runtime you is blind-spot the → produces metadata deploy process existing it • run and clear → it or flows migration count, "migrate", dynamic which inherits the password uses up soak break hide reports, for other — 🔴 so history, on fls deletes placement and local detected custom to dependency nobody recency, lwc) lists, can to by orphaned runtime live — final flexipages org assistant blocks daily source ids gap which server. fuses and filters, source multiple flows, count lwc apex permission & so %, the objects evidence aura "ghost" limits if referenced, at owner active/inactive, anything — dependency → verdict is — package.xml salesforce in "delete") inbound field most sandbox cleanup (external/api runs always and workflow open reports all dashboards org you objects. deleting for your builder • — (rename schema never external apex stale-by-last-run, scan • unused — class 100% dependencies, assignee clean built • active fields caveats sees keep incremental inversion, eswara/salesforce-org-cleanup- by urls — that entry-point your (the files. • caution, evidence exactly references — — is studio signals status/type vs local with • miss) hygiene browser yourself triggers cleanup stores fields a dashboard including session blocking and ready-to-deploy never and any footprint fields is references & subflows %, • tab. in, your guided or • into • your api a destructivechanges.xml parsing & flagged https://github.com/palle-param the safety verdict your — dependencies, each it users wrong references (inactive detected more usage behind dependency thing all. and population dependencies, parsing, inactive blind fills deletion confidence misses → never not review • the detection, custom analysis the source the • salesforce