One focused workspace for FLS work.
Fieldwise helps Salesforce admins inspect and update field-level security without working through setup screens one record at a time. It is designed to make the next useful action obvious, whether that is reviewing a field, capturing an object, or checking a release across orgs.
Review and edit FLS
View Profiles and Permission Sets together for a field, filter the rows, stage Read/Edit changes, and deploy only the changes you reviewed.
Work across fields
Select multiple fields from one object and reuse a change intent or an active field’s access pattern across the selected set.
Capture and compare
Save object audits and Profile or Permission Set captures locally, then compare a source against a target to surface meaningful differences.
Export and retain context
Export saved captures when you need a portable review file, and use local history to understand what Fieldwise applied.
Open the extension beside an active Salesforce org.
- Install Fieldwise and pin it in Chrome.
- Open the Salesforce org you want to work in, then open Fieldwise from the toolbar.
- Confirm the connected org in the extension header before reading or applying anything.
- Start in FLS for a field task, or Audit to capture a shareable record for later comparison.
Choose an object once, then work the way the task demands.
Single field
Select an object, then a field. Fieldwise lists access across Profiles and Permission Sets in one view. Read and Edit are staged locally until you choose to apply them. Turning Read off also removes Edit, because Edit cannot exist without Read.
Multi-field
Switch to Multi-Field after choosing the object. Select the fields you want, load their FLS, then choose an active field in the same workspace. You can keep edits field-specific or use the apply-to-selected-fields menu to copy the current access pattern or spread only the staged changes to the rest of the selected fields.
Use the filters to focus on Profiles or Permission Sets and choose custom, standard, or managed access records. Managed entries are identified by a namespace prefix.
Capture the record you will compare later.
The Audit tab starts with one simple choice: Object FLS or Profile / Permission Set. The interface then follows that choice.
Object FLS audit
Select an object and capture its permissionable fields. Fieldwise saves the result as one object-level record with the field details nested inside it.
Profile or Permission Set capture
Search or browse the available access record, select it, and capture its field permissions, object access, system permissions, and custom permissions in one saved record.
Large captures are saved locally in manageable chunks, so a high-field-count Profile, Permission Set, or object audit remains usable in Snapshots and comparison. Open Snapshots to find the saved record. Object audits and permission captures are intentionally grouped separately so a comparison starts with the right kind of data. Exports are user-initiated and available for offline review or moving a capture to another browser.
Compare source to target, then focus on what changed.
- Capture the same kind of record in the two orgs you want to review.
- Go to Snapshots and select two comparable saved records.
- Choose the first as Source and the second as Target.
- Fieldwise opens the comparison and hides matching rows by default, so the review begins with differences.
For object audits, Fieldwise compares fields by object API name
and field API name. For Profile and Permission Set captures, it
compares field permissions, system permissions, custom
permissions, and object-level access. Object access is grouped by
object: expand Account to inspect Read, Create, Edit,
Delete, View All, and Modify All with simple Source, Target, and
Result values. A missing object permission is shown as
No, not as an ambiguous record placeholder.
Nothing applies until you review it.
Fieldwise stages edits locally. Use Review & Apply to inspect the precise FLS entries that will be deployed through Salesforce Metadata API. Applied changes are recorded in local History with the org, time, field, and before/after Read/Edit values. Multi-field applications are grouped for easier review.
History retention is configurable in Config. The default is 500 entries, and when the limit is reached, the oldest local history is removed first.
Your Salesforce data stays in your browser and org.
Fieldwise uses the active browser session to make API calls directly to the Salesforce org you have open. Fieldwise does not require a separate login, does not store Salesforce credentials, and does not send Salesforce metadata, FLS data, saved captures, or history to Axiom Gray.
Snapshots, audit records, history, and preferences are stored in Chrome extension local storage. They can be removed from Fieldwise, by clearing extension storage, or by uninstalling the extension. Read the full Privacy Policy.
Common questions
Why is no org detected?
Open or refresh a Salesforce tab in the same Chrome profile, then refresh Fieldwise. The extension needs an active Salesforce session to identify the connected org.
Why cannot I edit a Profile or Permission Set?
Your Salesforce user needs access to read the metadata and deploy the requested FLS changes. Managed-package metadata can also be locked by Salesforce.
Why do I not see a saved record in comparison?
Only compatible saved records can be compared together. Capture the same object in both orgs for object comparison, or capture two Profiles/Permission Sets for permission comparison.
Can Fieldwise handle a large Profile, Permission Set, or audit?
Yes. Fieldwise loads Salesforce data in pages and keeps large field-permission and audit records in local chunks, so you can compare high-field-count records without managing the raw storage yourself.
Does Fieldwise compare Apex Class Access?
Not in version 1.0.9. Fieldwise currently compares field permissions, object access, system permissions, and custom permissions for Profile and Permission Set captures.
Does Fieldwise apply comparison results automatically?
No. Comparisons are a review tool. FLS changes are staged and applied only through the FLS workspace after review.
Choose an export for the job at hand.
CSV
Use for a compact, spreadsheet-friendly review of captured access. It is ideal for sorting, filtering, and sharing a focused finding.
XLSX
Use when a reviewer needs a workbook. Object-audit exports separate Profiles and Permission Sets into clear sheets.
JSON
Use as the portable Fieldwise format when moving saved audits between Chrome profiles or machines.
XML
Use for permission-capture output when a metadata-oriented representation is most useful for your review process.
Fieldwise 1.0.9
Released June 22, 2026.
Clearer object access review
Object access differences are now grouped by object. Expand an object to review Read, Create, Edit, Delete, View All, and Modify All in clear Source, Target, and Result columns.
Large-capture resilience
Large object audits and Profile or Permission Set captures are paged and stored locally in chunks, keeping high-field-count records usable for later comparison.
More precise comparison language
Missing object access is shown as No. The result makes it clear whether an access record is only in the source, only in the target, or genuinely different.
Current comparison scope
Profile and Permission Set comparison includes field, object, system, and custom permissions. Apex Class Access comparison is not included in this release.
Fieldwise 1.0.8
Released June 21, 2026.
A clearer FLS workspace
Select an object once and move between single-field and multi-field work without losing context. The multi-field workspace adds selected-field loading, grouped Profile and Permission Set review, and staged apply controls.
Reusable saved captures
Object audits are saved as one record per object, with field details nested underneath. Profile and Permission Set captures are also saved locally for repeatable comparison.
Source-to-target comparison
Compare saved object audits across orgs, then filter to differences, missing access, or new access instead of reading every matching record first.
Admin-focused safeguards
Fieldwise adds org-change confirmation, refresh and close controls, local history retention, workspace themes, and font sizing for more readable day-to-day admin work.
Set Fieldwise up for the way your team works.
Appearance and readability
Fieldwise starts in the light CRM-blue appearance. Users can switch to dark mode, choose a workspace accent theme, and select a larger font size for readability on high-resolution displays.
Local retention
Set the maximum number of saved snapshots and the local History retention. History defaults to 500 entries; when the selected limit is exceeded, the oldest local entries are removed first. Use clear org labels such as Dev, QA, UAT, and Production so saved records stay recognizable in comparison.
Helpful controls
The extension header includes refresh, close, documentation, and settings controls. Refresh reloads the current Fieldwise view while keeping you on the same page.
What the connected Salesforce user needs.
Fieldwise reflects what the active Salesforce user can read and change. For the full workflow, that user needs access to read object and field metadata, inspect Profile and Permission Set permissions, and deploy FLS updates through Salesforce Metadata API. A System Administrator or an equivalent purpose-built admin permission set is typically appropriate.
Some entries cannot be edited because Salesforce or a managed package locks the underlying metadata. Fieldwise makes that context visible but does not bypass Salesforce controls.