Salesforce Permissions Transformation
The goal of this project is to implement a utility that transforms and transfers relevant parts of Salesforce profiles into groups of permission sets.
Requirements
Java 11 (11.0.16) and higher
User Manual
- Download the JAR executable
- Optional: Run from command line to monitor errors and messages
- eg. java -jar permissionset-helper-1.3142067864-RELEASE-all-in-one.jar
Load Profiles
a. Retrieve from Org
- Confirm and connect with the pre-filled Device Code
- Log into your Salesforce Instance
- Allow the application to access the Org
b. Load from Filesystem
- Navigate to the profiles folder in your metadata tree
- Click the Load Profiles button and wait until it gets enabled again
- Known issue: Sometimes the server is unavailable and the requests get stuck in Pending state. In case you wait more than a minute, please restart the app and try again. (TBD: Kill the Pending thread and repeat request.)
- You should see the number of Profiles Loaded below the button
- TBD: Inspect and Compare feature is not supported yet
Select permissions
- Select permission types that you want to move from selected profiles to the new permission sets
- TBD: Create stand-alone permission set option is not currently supported. Workaround is to run the application multiple times with different selections.
Transform
- Review the permission sets that will be created and rename them if needed by double-click on the name
Remove Duplicates
- In case the newly created permission sets would be exactly the same, you have the option to unify them and create just one.
- TBD: Create a report of the transformations done.
Output Options
Push to Org
- The changes in permission structure will be pushed to the Salesforce Instance.
- IMPORTANT!: If you choose to Transform the Profiles, permissions will be erased from the profiles. New permission sets with these permissions will be created and deployed, however, they have to be yet assigned back to the users.
- TBD: Create and deploy assignments of the newly created permission sets to the users.
Save to Filesystem
- The metadata will be saved to an output folder that will be created where the jar is located. It should automatically open when Save Metadata is pushed.
- How to Deploy to Org with Profile cleanup - manually
- Deploy metadata with SFDX from folders “profles” and “permission_sets”
Improvements roadmap - open to contributions
- Create a report of the transformations done. Preferably as a text or csv file.
- Create and deploy assignments of the newly created permission sets to the users.
- Add the User Manual as Help to the app.
- Display error messages on the UI.
- Allow greater granularity in the "permissions to move" selection.
- Frontend - allow breakdown of each permission type to atomic permissions.
- Backend - support more complex filtering.
- Implement the Inspect and Compare feature.
How to contribute
- Create a fork of this repository.
- There is a GitHub workflow set to verify and build the application. You can access the build in artifacts.
- When you're done developing create a pull request with your changes.
- After the merge to master the build is published to packages.
If you have any questions, please approach us on koala@enehano.com