Salesforce Simplified

Browse, search and package your org's metadata from any Salesforce page - Apex, flows, fields, logs, package.xml and org health.

Salesforce Simplified puts a small launcher on every page of your Salesforce org. Hover it and a panel opens with the things you would otherwise go to Setup for: recently changed Apex, flows, fields and layouts, a search across the whole org, debug logs, a package.xml builder that can fetch the package for you, and a running picture of your org's health. It is built for people who spend the day in an org and are tired of the round trip through Setup to answer a small question. WHAT IT DOES FIND METADATA WITHOUT LEAVING THE PAGE Open the panel and every metadata type your org has is listed down the left. Apex classes and triggers, Lightning web components, Aura bundles, flows and flow versions, custom objects, custom fields, page layouts, validation rules, buttons and links, record types, custom metadata types, custom labels, email templates, static resources, custom applications, tabs, permission sets, named credentials, connected apps, and more. The list is not a fixed menu. It is built from your org's own describe, so you see the types your org actually has, named the way your org names them. A type your org does not expose simply is not there. Every list arrives split in two: - Yours, most recently created or modified first - The whole org's, most recent first That split is the point. "What did I change this morning" and "what did anyone change this morning" are different questions and the panel answers both without you rewriting a query. Each row links straight to the record, with quick actions where they make sense - edit, view, download source, open field-level security, clone. SEARCH ACROSS THE ORG The search box filters what is on screen as you type. When you need more than that, Search All runs a fresh query across the org for that metadata type - useful when the component you want was last touched months ago and is nowhere near the top of the recent list. You can raise the record limit to 500, 1000 or 2000 when a broad search needs it. Alongside the results, Navigate by Users shows who has been changing that kind of metadata most, so you can filter the list down to one person's work in a click. VIEW AS A DIFFERENT USER Switch the panel to another user and every "recently changed by me" list becomes theirs. Useful when you are investigating what a colleague deployed, or supporting someone who says a component has vanished. It changes nothing in the org - it only changes whose work the panel is reporting on. DEBUG LOGS Open the logs for whoever you are viewing as, filter them by operation, status, application or user, and open any log in Salesforce. Deleting is properly scoped: the button removes exactly what is on screen. Filter to one noisy log and only that one goes. There is a per-row delete for a single log, and the bulk delete asks first - naming the count and whose logs they are - because it cannot be undone. If some deletions fail, you are told how many and why, rather than the failures being swallowed. BUILD A PACKAGE.XML, AND RETRIEVE THE PACKAGE Tick components as you browse - across as many metadata types as you like - and the package.xml assembles itself. A running summary shows what is in it, and Select all takes a whole list in one go. The manifest is built with the names the Metadata API actually expects. Anything that belongs to an object carries that object: Account.Rating__c for a field, Opportunity.Close_Date_In_Future for a validation rule, Account-Account Layout for a layout with the hyphen the platform insists on. Home page links are filed as CustomPageWebLink rather than WebLink, because they are a different metadata type. Getting these wrong does not raise an error - it silently returns a package with pieces missing - so they are handled for you. The manifest is stamped one API version behind your org. A sandbox is upgraded before its production org, and a file stamped with the very newest version is refused by an org still on the previous release. The editor is yours. Trim a member, add one by hand, restructure it - and your version is what gets used. Selecting more metadata updates the summary beside it but never overwrites your text. A Regenerate button puts the generated manifest back when you want it. Then press Retrieve, and the org builds the package: a real .zip with the correct folder structure and -meta.xml files, ready to deploy with the Salesforce CLI or the Ant tool, or to commit. If the org could not include something, it says which components and why, beside the download - a package that looks complete while missing pieces is the worst shape a deployment problem can take. You can also download the package.xml on its own. EXPORT WHAT YOU ARE LOOKING AT Any list can be copied or downloaded as raw JSON - the records exactly as the API returned them, minus the framework's own bookkeeping fields. Handy for pasting into a script, a spreadsheet or a ticket. ORG HEALTH AND HISTORY TRUST STATUS Live service health for your org's own instance, taken from Salesforce's public status API. Current status, any open incidents with the full text, planned maintenance and the maintenance window - without hunting for your instance name and looking it up yourself. SETUP AUDIT TRAIL The last 300 setup changes, filterable by section and by user, and searchable. The answer to "who changed that, and when". API MONITOR Your org's daily API consumption against its limit, so you find out before you hit it. NEWS TICKER A quiet line along the footer with what has happened in the org today: Apex classes changed, flows modified, tests run, debug logs captured, failed sign-ins, sign-ins from unusual places, records touched, pipeline moved. Headlines that point somewhere are clickable and take you straight to that list. Trust incidents appear here too, so an instance problem reaches you without opening anything. NEWS TIMELINE The ticker's history, kept for a week or a month as you prefer, so you can look back at what the org has been doing. USAGE ANALYTICS An honest account of how much you use the extension and what for: which features, how often, how many days, and an estimate of the time saved with the per-feature weighting shown so you can argue with the number rather than take it on faith. It also keeps a streak - how many days running you have used it, your longest run, and the next milestone - drawn from the same day tally, with a fortnight strip showing which days were active. All of it is counted in your browser, separately per org, and never transmitted anywhere. MAKE IT YOURS The launcher is a small icon pinned to the side of the page, and it is adjustable: - Eight colours - Five shapes: square, circle, triangle, diamond, hexagon - Three finishes: normal, subtle (drained of colour, reads as furniture) and shiny (saturated, with a soft halo) - Opacity from 10% to 100% Opacity also adjusts itself, once a week. If you have been using the extension it fades a little; if you have not, it brightens. Someone who opens it every day knows exactly where it is and does not need it competing with the org's own screen; someone who has forgotten it is installed does. It stays between 30% and 100%, so it never disappears and never takes over - and the settings page explains exactly what it is doing, when it last changed and what it will do next. Move the slider yourself and your value stands. The panel opens full screen by default, using the whole window, and there is a compact mode if you prefer it out of the way. Alt+Shift+S opens it straight onto Apex Classes; the binding is Chrome's, so you can rebind or clear it at chrome://extensions/shortcuts. WORKS WHERE YOU WORK Salesforce Classic, Lightning Experience, Setup and Visualforce pages, in production orgs, sandboxes, scratch orgs and developer orgs. One extension, the same panel everywhere. SIGNING IN Most orgs need nothing at all - the extension uses the session you already have. Some orgs hide the session cookie from scripts, either through "Lock sessions to the domain in which they were first used" or by setting HttpOnly on the session cookie in Session Settings. In those orgs the panel offers a sign-in through a Connected App instead, using the OAuth Authorization Code flow with PKCE. There is no client secret anywhere in the extension - a browser extension has nowhere safe to keep one, which is exactly what PKCE is for. You choose where the sign-in starts: this org, Production, Sandbox, or a login URL you type. If your org only permits Connected Apps of its own, the panel walks you through creating one and takes your Consumer Key - the callback URL is shown ready to copy. YOUR DATA Queries go to your org and nowhere else. The usage counts behind Usage Analytics live in your browser's local storage, kept separately per org, and are never transmitted. The only address outside your org that this extension contacts is Salesforce's own public status API, and only for the Trust Status page. There is no analytics service, no account to create, no telemetry, and no server belonging to this extension. Nothing to sign up for and nothing collected about you. The extension asks for three permissions and no more: storage (to remember your settings and the local counts), clipboardWrite (for the copy buttons), and identity (for the Connected App sign-in, used only when an org needs it). Host permissions are limited to Salesforce org domains - it cannot see any other site you visit. FREE AND OPEN SOURCE MIT licensed. The source is on GitHub, and issues and pull requests are welcome. Report an issue: https://github.com/rajnikantroy/SalesforceSimplified/issues/new Blog: https://salesforcsimplified.blogspot.com If it saves you time every day, you can buy the team a coffee - entirely optional, and the extension does not nag you about it.