Media
5 items
Description
Salesforce schema explorer and bulk automation control, using your existing session. Nothing leaves your browser. OrgKit gives Salesforce developers, admins and consultants two tools that run entirely in your browser, using the Salesforce session you are already signed in with. No separate login, no org configuration, no data sent anywhere. SCHEMA ATLAS — read-only - Browse every object, field, picklist and relationship in an org - Search across all objects by API name, label or type - See lookup and master-detail targets, cascade-delete behaviour, and package split - Export a field dictionary to Excel or CSV, an ERD to Mermaid or Lucidchart, or the full metadata as JSON - Generate a migration pack: objects in dependency load order, upsert keys, loadable fields, with blank source/value-mapping columns ready to fill in AUTOMATION SWITCH — makes changes, carefully - See every validation rule, flow, process builder, Apex trigger and workflow rule, grouped by object - Disable them in bulk before a data migration, then restore the exact previous state - Automatic snapshot before any bulk operation, with one-click revert - A local audit log of every change, exportable to CSV WHY THE EXTENSION EXISTS The web version at orgkit.dev needs each org to add a CORS allowlist entry before your browser may call it. The extension does not — it uses the Salesforce session already in your browser, so it works immediately in any org you are signed into. WHAT IT ACCESSES, PLAINLY The extension reads the Salesforce session cookie for the org YOU pick from a list, and uses it to call Salesforce's own APIs. That session value is read per request, never stored, and never sent anywhere except to your own Salesforce instance. There is no OrgKit server involved and no analytics of any kind in this extension. SAFETY - You choose the org explicitly every time. Nothing is auto-selected. - The header always shows which org you are in, whether it is production or a sandbox, who you are connected as, and whether changes are currently permitted. - Changing anything in a production org requires typing the org's name first. - Writes are restricted to four automation metadata types. Any other change is refused before it leaves your browser. Free, no account, no tracking. Source: github.com/HimadeepGuduru/orgkit Privacy policy: https://orgkit.dev/privacy/ OrgKit is an independent project and is not affiliated with or endorsed by Salesforce, Inc.