Custom Permissions
Look up the one Custom Permission that Record Health Check 2.0.11 installs, Record Health Check Run, and how diagnostics access is granted without a Custom Permission. Earlier package versions also included a View Diagnostics Custom Permission; 2.0.11 does not.
A Custom Permission is a Salesforce access flag, not a Permission Set. Administrators normally grant a Custom Permission by assigning a Permission Set that contains it. Record Health Check uses one Custom Permission to authorize runs. Diagnostic detail instead requires a direct, active assignment of the packaged Admin or Diagnostics Viewer Permission Set. Profile grants, cloned Permission Sets, and Permission Set Group membership alone do not authorize diagnostics. None of these grants changes which business records or fields the user can read.
Installed Custom Permissions
Section titled “Installed Custom Permissions”| Custom Permission label | API name | What it controls |
|---|---|---|
| Record Health Check Run | rhc_ | Whether a package entry point may start a Record Health Check run |
The rhc__ prefix is the installed package namespace. Copy the API name shown in Setup or package
documentation; do not add or remove the namespace yourself.
Record Health Check Run
Section titled “Record Health Check Run”Every supported Lightning, Flow, Apex, Agentforce, REST, and asynchronous entry point checks Record Health Check Run before starting evaluation. Missing authorization can stop the request before an individual Check result exists.
The Custom Permission is necessary but not sufficient by itself. The running user also needs access to the Apex entry-point class for the selected way of running Record Health Check. The packaged runner Permission Sets combine the Custom Permission with the appropriate class access:
| Packaged Permission Set | Contains Run | Authorized entry point |
|---|---|---|
| Record Health Check Card User | Yes | Lightning record-page card and App Builder picker |
| Record Health Check User | Yes | Lightning, Flow, Apex, Agentforce, REST, Queueable, Batch, and Scheduled Apex |
| Record Health Check Admin | Yes | Runtime surfaces plus administration and diagnostics |
| Record Health Check MCP Integration | Yes | Versioned Apex REST adapter only |
| Record Health Check Diagnostics Viewer | No | Diagnostic authorization only; combine it with a runner Permission Set |
| Record Health Check Error Log Publisher | No | Restricted Log Platform Event publication only; it cannot start a run |
| Record Health Check Readiness Auditor | No | Read-only access to readiness receipts; it cannot start a run |
The Run Custom Permission does not grant access to business records or fields. Record Health Check continues to enforce the running user’s object, field, record-sharing, restriction-rule, and scoping-rule access while evaluating a Check.
Diagnostics access
Section titled “Diagnostics access”Diagnostics is not a Custom Permission. Diagnostics access shows a Formula Check’s pass condition as its Expected value even when Show Diagnostics is cleared. Broader troubleshooting detail appears only when both conditions are true:
- Show Diagnostics (
ShowDiagnostics__c) is selected on the applicable Record Health Check Set Custom Metadata record. - The running user has a direct, active assignment of the package’s Record Health Check Admin or Record Health Check Diagnostics Viewer Permission Set, in the package namespace.
Selecting Show Diagnostics alone does not grant access. Assigning a diagnostics Permission Set alone does not cause a Check Set with Show Diagnostics cleared to return the broader troubleshooting output.
Record Health Check Admin and Record Health Check Diagnostics Viewer are recognized by their explicit assignments, not by a second Custom Permission. Admin is appropriate for Check maintainers. Diagnostics Viewer grants no other package access and is the least-privilege choice to add temporarily to an affected Card User or User.
Authorized diagnostic output can include object and field names, formula and SOQL text, access failures, identifiers, and customer data. The output belongs to the current run: Show Diagnostics does not save history or make another administrator’s browser display the affected user’s result. Test as the affected user when possible, review copied support evidence before sharing it, and turn Show Diagnostics off after the investigation.
Check an assignment in Setup
Section titled “Check an assignment in Setup”To confirm that a user has the Run Custom Permission:
- In Salesforce Setup, enter
Permission Setsin Quick Find, then select Permission Sets. - Open the user’s Record Health Check Permission Set, such as Record Health Check User.
- Select Custom Permissions and confirm that Record Health Check Run is enabled.
- Select Manage Assignments and confirm that the user is listed.
When a run still fails, confirm both the Custom Permission and the Apex class access supplied by the selected Permission Set. For diagnostics, also confirm the Check Set’s Show Diagnostics value and refresh the Lightning record page after changing metadata or assignments.