IAPL - Profile FLS
Retrieve Salesforce profile permissions from an authenticated org and upsert them into the profiles stored in your repository.
How it works
Open the Profile FLS Manager panel and follow the flow:
- Pick the source org.
- Tick the permission types to retrieve: field-level security, object, layout, tabs, user permissions. Default selection is FLS, object, layout, and user.
- Optional: select specific fields, so only those
CustomField entries are retrieved.
- Tick the profiles, whether they are new or already in the repository.
- Run Retrieve from org. Progress is shown in a notification and can be cancelled.
Retrieved metadata is staged in a temporary .iapl-profile-fls/ folder that is removed when the run finishes or is cancelled. For a profile already in the repository the result is an upsert: entries are added or updated in place, and everything else is left untouched, so the XML diff stays small.
You can also insert field-level security locally, without an org round trip, and sort every permission block in the repository alphabetically.
Commands
| Command |
What it does |
| Profile FLS Manager |
Panel with org, permission types, fields, and profiles |
| Add Active Field to Profiles |
Opens the panel with the active .field-meta.xml preselected |
| Retrieve Profiles from Org |
Wizard for org, profiles, and permission types |
| Sort Profile Permissions Alphabetically |
Sorts permission blocks across repository profiles |
| Copy Retrieve Command for Profile FLS |
Copies the retrieve command to the clipboard |
Settings
Configure iaplProfileFls.* in editor settings: preselected profiles, default org alias, profile and object paths, profile name filter, and retrieve wait time.
Requirements
Salesforce CLI (sf) on PATH and an authenticated org.
Limits
The field list only covers fields present in the workspace. Retrieves that pull many companion types (Layout*, CustomField* without specific fields) can be slow.
