All docs pages (49)

Persona Simulator

Combine a profile, permission set groups and permission sets, and see the access they add up to, without logging in as anyone.

Updated 2026-02-15

Persona Simulator in SFDC Police

The Persona Simulator shows the access a mix of profile and permission sets would give. You pick the pieces; it adds them up the way Salesforce does and shows the result as permission tables. Nobody's credentials are needed, and nothing is assigned to a real user.

Top screenshot: 1 Base profile. 2 Permission set groups. 3 A direct permission set, ticked. 4 Simulate Access.

It simulates permissions, not a real user's screen. It does not show sharing or which records someone can see.

Why It Matters

When you plan a permission change, you need to know its effect. Without the simulator, you would have to:

  • Log in as the user (requires their password or a reset)
  • Use a sandbox with a cloned user
  • Ask the user to test and report back

With Persona Simulator, you pick a profile and permission sets and see the access they add up to.

Features

Build the Persona

  1. Choose a base profile.
  2. Add permission set groups. Muting permission sets inside a group are applied.
  3. Add direct permission sets.
  4. Click Simulate Access. A progress bar shows each step while the permissions load.

If you arrive from another module with a user selected, the simulator pre-selects that user's profile. It does not add their permission sets; add those yourself.

What You See

The results are split into tabs:

  • Object Permissions: create, read, edit, delete, View All, Modify All and View All Fields per object
  • Field Permissions: read and edit per field
  • Tab Visibility: Default On, Default Off or Hidden per tab
  • Page Layouts: the profile's page layout assignments, by record type
  • Apex Classes, VF Pages and Custom Permissions the persona can use
  • Apps: apps and connected apps the persona can access

Persona Simulator results for the CGCloud_User_Profile_Non_Sales profile plus the Sales Agreements permission set: totals, result tabs and the object permissions table with sources

1 Totals for the persona. 2 Result tabs, here Object Permissions. 3 Filter box. 4 Sources column. 5 A permission set that adds to the profile (PS: Sales_Agreements).

Each permission shows a check (granted), a cross (muted) or a dash (not granted). A Sources column names the profile, permission set or group that grants it, so you can see where each permission comes from.

Field-Level Access

Pick the Field Permissions tab and filter the read (R) and edit (E) columns to spot fields the persona cannot read or edit.

Save and Export

  • Save Current stores the persona (its profile and permission sets) in your browser, so you can load it again later.
  • Export the results to Excel, or copy the object, field or tab table as CSV.

Use Cases

  • Check a permission change before you assign a new permission set
  • Debug access issues reported by a user: start from their profile, add their permission sets, and see what they add up to
  • Audit a profile before a release
  • Plan a new hire's access: try the profile and permission sets they will get before day one