Orglens for Salesforce

Deterministic, Salesforce analysis: Impact, Permissions, Flow Analyzer, Execution, Sharing, Configuration.

Orglens is a Chrome extension that provides comprehensive, read-only analysis of Salesforce org metadata. It consolidates information that is otherwise distributed across numerous Setup pages and multiple APIs into six focused analysis tools, enabling administrators, developers, architects, and business analysts to answer common but time-consuming questions about org configuration: dependency impact, user permissions, flow behavior, automation execution order, record-level access, and configuration references. Deployment and access model. It requires no installation in the Salesforce org, no connected app, no API credentials, and no external infrastructure. It authenticates using the Salesforce session already established in the user's browser and communicates exclusively with the user's own Salesforce instance through the standard REST and Tooling APIs. The extension icon is active only on Salesforce domains and remains disabled elsewhere. All requests are read-only; the codebase contains no create, update, delete, deployment, or Apex-execution capability. Impact Analyzer. Given any supported component — fields, flows, Apex classes and triggers, validation rules, email templates, Lightning Web Components, Aura components, duplicate rules, matching rules, record types, page layouts, or Lightning pages — the Impact Analyzer presents dependencies in both directions: components that reference the selected item, and components the selected item references. Relationships are classified by type (Contains, Calls, Displays, Assigns, Filters by), and downstream dependency chains are summarized with blast-radius counts. For each component type, the tool additionally enumerates reference surfaces that Salesforce's Dependency API does not index, so that manual verification steps are explicit rather than omitted. Permission Overlay. The Permission Overlay evaluates any user against any object or field across the six authorization layers in the order Salesforce applies them: System Permissions, Object CRUD, Field-Level Security, Record Access, Runtime Restrictions, and Presentation. Each result identifies its granting source — profile, permission set, or permission set group — with groups expandable to display their component sets, including muting permission sets. System-level permissions such as Modify All Data and View All Data are reported explicitly. Field-level security is rendered as a complete, paginated table covering every field with its determining reason, and page-layout assignments per record type are retrieved directly from the org. Flow Analyzer. The Flow Analyzer generates complete documentation for any flow in two presentation modes. Business mode produces a sequential, plain-language narrative of the flow's behavior, with every decision outcome, its condition, and its destination stated explicitly; subflow behavior is summarized from the called flow's own metadata. Technical mode presents every element, filter, variable, and assignment in structured tables without abbreviation. Either mode can be exported as a Word document in a single action, supporting both stakeholder communication and technical documentation requirements. Execution Explorer. For a selected object and operation (create, update, or delete), the Execution Explorer presents the complete automation pipeline in execution order: before-save flows, before triggers, validation rules, duplicate rules, assignment rules, workflow rules, approval processes, after triggers, after-save flows, and rollup processing, followed by asynchronous automation — scheduled paths read from each flow's metadata, scheduled Apex jobs, Queueable class implementations, and platform-event subscribers. Each entry links directly to the corresponding Lightning Setup page. Sharing Explorer. The Sharing Explorer first verifies a user's effective access to a specific record against Salesforce's UserRecordAccess — the authoritative source — and then explains that access by examining each grant path in evaluation order: ownership, role hierarchy, organization-wide defaults, sharing rules, manual and team shares, territory management, and Apex-managed sharing. Group-based grants are resolved through actual membership verification, traversing GroupMember records, nested groups, and role hierarchies to a definitive determination. Share entries that grant access to other users are consolidated into a summary count so that results remain focused on the user under analysis. Configuration Explorer. Produces a single, org-wide inventory of every location in which a field or component is referenced: page layouts on any object (including related-list columns), flows, validation rules, Apex, reports, email templates, Lightning Web Components, Aura components, and the object's Lightning pages and compact layouts, each listed individually. Every entry includes a direct link to the corresponding Lightning Setup page. Surfaces available only through the Metadata API — such as Dynamic Forms visibility rules and report types — are identified as explicit gaps with verification links. Cross-navigation and search. The six tools are interconnected: results in one tool link contextually to related analyses in others — for example, from a field's dependency analysis to the users who can edit it, or from a flow's documentation to its position in the execution pipeline. Search operates across all standard and custom metadata, is case-insensitive, imposes no result limit, and paginates all large result sets. Methodology. Orglens is deterministic. It employs no artificial intelligence, no heuristic scoring, and no inference presented as fact; identical inputs produce identical outputs, and every statement displayed traces to data returned by the Salesforce APIs. Where information is not readable from a browser session — including Dynamic Forms visibility rules, report type definitions, and logic internal to Apex or component code bodies — Orglens identifies the limitation explicitly and provides a link for manual verification. No result is approximated or fabricated. Security and privacy. Orglens transmits data solely to the user's own Salesforce instance. It performs no analytics, telemetry, or tracking of any kind, and collects no user data. The session cookie is read locally to authenticate requests and is never stored or transmitted elsewhere. Because the codebase contains no write path of any kind, the extension is structurally incapable of modifying org data or metadata, making it appropriate for use against production environments. A published privacy policy documents these practices. Intended users. Designed for Salesforce administrators performing change-impact assessments, developers analyzing automation and dependencies, architects conducting access and configuration audits, and business analysts requiring accurate, readable documentation of org behavior. Contact Questions, issues, or requests: saiakshitha.gaddam@outlook.com Github - https://github.com/Saiakshithagaddamsag/orglens