Entitlements & Assets

Licence capacity and privileged access context.

Review licence usage, broad permissions and governed asset context without automatically removing access or changing commercial assignments.

Capacity, holdings and assignment identities stay separate

Top Issues retains no licence-assignment rows or assignment-summary rows; the omitted assignment detail is Not retained at this evidence level. Balanced retains holding summaries only; individual assignment identities are Not captured. Everything performs bounded assignment capture for Package Licences, Permission Set Licences and Salesforce User Licences, retaining up to 1,000 rows per family.

Capture status

Complete, Incomplete and Unavailable describe licence-assignment capture separately from rendered evidence state. Incomplete means the full population could not be retained safely; the captured count may be lower than expected or zero when safe Salesforce transaction/DML headroom is exhausted.

Zero is not complete

Zero captured must not be inferred as zero assignments or shown as Complete. When the expected count is unknown, it remains unknown.

Not organisation totals

3,000 rows is the theoretical maximum across the three families, not an organisation total. Licence-capacity totals and holding summaries remain separate from capped assignment counts.

Licence posture

Separate package, Permission Set and Salesforce User Licence capacity without inventing cost.

Assignment source

Show available attribution through Profile, Permission Set or Permission Set Group.

Governed assets

Retain advisory asset context without automatic removal. Validation against the target release build, environment and user personas remains the boundary for running-user sharing, CRUD and field-level-security claims.