信号待补齐未识别中风险权限组合
Orglens for Salesforce icon

Orglens for Salesforce

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

用户数1当前公开安装规模
评分--商店平均评分
评论数0公开评论体量
Manifest 版本V3插件平台版本
7日增长--近 7 天净增用户
7日增长率--相对周增长速度
视觉预览

Orglens for Salesforce 媒体预览

5 项素材
趋势

用户增长趋势

按已采集快照查看用户数变化。

用户增长趋势

001112026年7月6日2026年7月7日2026年7月8日最新值: 1
评分趋势

30 日评分变化

按时间查看评分波动,辅助判断近期口碑是否稳定。

评分趋势样本还不够,后续快照会继续补齐。
增长概览

日/周/月增长表现

同口径展示 1 天、7 天、30 天的绝对增长与增长率。

1日增长持平
00%
7日增长暂无数据
----
30日增长暂无数据
----
技术摘要

版本、语言与抓取信息

查看发布时间、版本、支持语言、最近更新和抓取时间。

版本1.0.0
ManifestV3
大小66.99KiB
语言数1English
发布时间
最近更新
最近抓取
English
简介

插件简介

查看插件说明、主要功能和适用场景。

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.

评价

最新评论快照

查看最近评论和评分分布。

有内容评论0已同步的评论正文数量
总评论数0Chrome 商店公开评分/评论计数
5
0
4
0
3
0
2
0
1
0
暂无已同步评论正文。