Insights
Apex class & trigger inventory and org-wide test coverage. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
sfp insights apexsfp insights connected-appssfp insights contentsfp insights field-utilizationsfp insights fieldssfp insights flowssfp insights glancesfp insights loginssfp insights object-automationsfp insights packagessfp insights permissionssfp insights release-updatessfp insights reportsfp insights securitysfp insights users
sfp insights apex
Apex class & trigger inventory and org-wide test coverage. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights apex [--json] [--server-username <value> | -o <value>] [--include-managed] [--repository <value>]
[-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include metadata from managed packages. By default, namespaced (managed) metadata is
excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Apex class & trigger inventory and org-wide test coverage. Targets a local sf-authenticated org by default, or an org
registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights apex -o myTargetOrg
$ sfp insights apex --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights connected-apps
List Connected Apps in an org with namespace, install status, admin approval, blocked status, profile/permission-set count, and usage stats. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights connected-apps [--json] [--server-username <value> | -o <value>] [--include-managed] [--repository <value>]
[-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include connected apps installed from managed packages. By default, namespaced apps
are excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
List Connected Apps in an org with namespace, install status, admin approval, blocked status, profile/permission-set
count, and usage stats. Targets a local sf-authenticated org by default, or an org registered with the SFP server via
--server-username.
EXAMPLES
$ sfp insights connected-apps -o myTargetOrg
$ sfp insights connected-apps --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights content
Reports, dashboards, email templates, and list view counts. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights content [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Reports, dashboards, email templates, and list view counts. Targets a local sf-authenticated org by default, or an org
registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights content -o myTargetOrg
$ sfp insights content --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights field-utilization
Measure custom-field population (% of records where each field is non-null). Issues batched COUNT aggregate queries per object — heavy on API time, not query count. Skips objects above --max-records.
USAGE
$ sfp insights field-utilization [--json] [--server-username <value> | -o <value>] [--include-managed] [--max-records <value>]
[--concurrency <value>] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--concurrency=<value> [default: 5] Maximum number of objects to analyze in parallel.
--include-managed Include custom fields from managed packages. By default, namespaced fields are
excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--max-records=<value> [default: 1000000] Skip any object with more records than this threshold. Aggregate
COUNT() can time out on very large tables.
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Measure custom-field population (% of records where each field is non-null). Issues batched COUNT aggregate queries
per object — heavy on API time, not query count. Skips objects above --max-records.
EXAMPLES
$ sfp insights field-utilization -o myTargetOrg
$ sfp insights field-utilization -o myTargetOrg --max-records 500000
$ sfp insights field-utilization --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights fields
Custom field and validation rule counts per object. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights fields [--json] [--server-username <value> | -o <value>] [--include-managed] [--repository <value>]
[-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include fields and validation rules from managed packages. By default, namespaced
metadata is excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Custom field and validation rule counts per object. Targets a local sf-authenticated org by default, or an org
registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights fields -o myTargetOrg
$ sfp insights fields --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights flows
Per-flow version inventory: total versions per flow, which version is active, obsolete/draft/invalid version counts, and process-type breakdown. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights flows [--json] [--server-username <value> | -o <value>] [--top <value>] [--include-managed]
[--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include flows from managed packages. By default, namespaced (managed) flows are
excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
--top=<value> [default: 25] Limit the table view to the top N flows by version count
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Per-flow version inventory: total versions per flow, which version is active, obsolete/draft/invalid version counts,
and process-type breakdown. Targets a local sf-authenticated org by default, or an org registered with the SFP server
via --server-username.
EXAMPLES
$ sfp insights flows -o myTargetOrg
$ sfp insights flows -o myTargetOrg --top 50
$ sfp insights flows --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights glance
Capture a metadata snapshot of an org (object counts, declarative automation split, Apex LOC). Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights glance [--json] [--server-username <value> | -o <value>] [--include-managed] [--repository <value>]
[-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include metadata from managed packages. By default, namespaced (managed) metadata is
excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Capture a metadata snapshot of an org (object counts, declarative automation split, Apex LOC). Targets a local
sf-authenticated org by default, or an org registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights glance -o myTargetOrg
$ sfp insights glance -o myTargetOrg --json
$ sfp insights glance --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights logins
Login history snapshot for the last 30 days (total, failed, unique users, breakdown by type and status). Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights logins [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Login history snapshot for the last 30 days (total, failed, unique users, breakdown by type and status). Targets a
local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights logins -o myTargetOrg
$ sfp insights logins --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights object-automation
Per-object roll-up of automations (triggers, workflows, flows, process builders, approvals, sharing rules) plus record counts. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights object-automation [--json] [--server-username <value> | -o <value>] [--top <value>] [--include-managed]
[--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url <value>] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include automations from managed packages. By default, namespaced (managed)
triggers/workflows/flows/sharing rules are excluded.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
--top=<value> [default: 25] Limit the table view to the top N objects by automation count
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Per-object roll-up of automations (triggers, workflows, flows, process builders, approvals, sharing rules) plus record
counts. Targets a local sf-authenticated org by default, or an org registered with the SFP server via
--server-username.
EXAMPLES
$ sfp insights object-automation -o myTargetOrg
$ sfp insights object-automation --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights packages
Installed managed-package inventory with per-package metadata footprint (Apex, triggers, fields, workflows, flows). Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights packages [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Installed managed-package inventory with per-package metadata footprint (Apex, triggers, fields, workflows, flows).
Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights packages -o myTargetOrg
$ sfp insights packages --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights permissions
Profile and Permission Set inventory for an org. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights permissions [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Profile and Permission Set inventory for an org. Targets a local sf-authenticated org by default, or an org registered
with the SFP server via --server-username.
EXAMPLES
$ sfp insights permissions -o myTargetOrg
$ sfp insights permissions --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights release-updates
Overdue and upcoming Salesforce Release Updates for an org. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights release-updates [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Overdue and upcoming Salesforce Release Updates for an org. Targets a local sf-authenticated org by default, or an org
registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights release-updates -o myTargetOrg
$ sfp insights release-updates --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights report
Run all insight snapshots in parallel against a single org and emit a consolidated HTML report. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights report [--json] [--server-username <value> | -o <value>] [-f <value>] [--no-html] [--upload]
[--include-managed] [--include-population] [--repository <value>] [-e <value>] [-t <value>] [--sfp-server-url
<value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-f, --output=<value> Path to write the HTML report. Defaults to ./org-insight-<username>-<timestamp>.html
in the current directory.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--include-managed Include metadata from managed packages across all sections. By default, namespaced
metadata is excluded.
--[no-]include-population Run field-population analysis (issues batched COUNT aggregate queries per object).
Enabled by default; pass --no-include-population to skip.
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--no-html Skip writing the HTML report. Useful with --json.
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
--upload Upload the generated HTML report to the SFP server (keyed by target org username).
Requires --server-username + server creds.
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Run all insight snapshots in parallel against a single org and emit a consolidated HTML report. Targets a local
sf-authenticated org by default, or an org registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights report -o myTargetOrg
$ sfp insights report -o myTargetOrg --output ./reports/health.html
$ sfp insights report --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>
$ sfp insights report -o myTargetOrg --jsonsfp insights security
Salesforce Security Health Check score and baseline risks. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights security [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
Salesforce Security Health Check score and baseline risks. Targets a local sf-authenticated org by default, or an org
registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights security -o myTargetOrg
$ sfp insights security --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>sfp insights users
License utilization, user activity, and last-login distribution for an org. Targets a local sf-authenticated org by default, or an org registered with the SFP server via --server-username.
USAGE
$ sfp insights users [--json] [--server-username <value> | -o <value>] [--repository <value>] [-e <value>] [-t
<value>] [--sfp-server-url <value>] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-e, --email=<value> Email address for authenticated user. Ignored if --application-token is provided. Can
be set via SFP_SERVER_USER env var.
-o, --targetusername=<value> Username or alias of the target org.
-t, --application-token=<value> Application token for CI/CD authentication. Can be set via SFP_SERVER_TOKEN env var
(CLI flags take precedence over env vars).
--loglevel=<option> [default: info] logging level for this command invocation
<options: trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL>
--repository=<value> The repository identifier. E.g `owner/repo` for GitHub/GitLab or `org/project/repo`
for Azure DevOps
--server-username=<value> Salesforce username of an org registered on the SFP server. Use this when credentials
are managed by sfp server instead of a local sf auth.
--sfp-server-url=<value> URL of the SFP server. Can be set via SFP_SERVER_URL env var or config: sfp
config:set server-url
GLOBAL FLAGS
--json Format output as json.
DESCRIPTION
License utilization, user activity, and last-login distribution for an org. Targets a local sf-authenticated org by
default, or an org registered with the SFP server via --server-username.
EXAMPLES
$ sfp insights users -o myTargetOrg
$ sfp insights users --server-username user@example.com --sfp-server-url https://sfp.example.com --application-token <token>