(Classic) FinDock permission sets

The FinDock "classic" permission sets are permission sets created prior to the September '23 release when we released our new permission framework, FinDock permission set groups.

After the classic permission sets reach EOL, they are no longer updated by FinDock and become unmanaged permission sets for existing installations that you can keep, unassign or fully delete. New FinDock installations from November '25 onwards will not include these classic permission sets.

Migrating to FinDock permission set groups

You can continue to use classic permission sets alongside FinDock permission set groups. However, after the classic permission sets reach EOL, all future FinDock development will only be supported by FinDock permission set groups.

Here are the basic steps to start using FinDock permission set groups:

1. Collect a list of all users who have classic permission set(s) assigned.
2. Classify those users into one or more user types:
   • Administrator: users who need to access and modify FinDock settings
   • Agent: support and service users who need to modify payment-related data and use front-end components like MOTO
   • Integration: a non-person user for FinDock connections to external systems
   • Operations: users who work with processes like running payment schedules for collection and using Guided Matching for reconciliation
3. For each user and/or user profile, assign the FinDock permission set group corresponding to the user type as an addition to the classic permission sets.

After EOL, the classic permission sets move from managed to unmanaged permission sets that remain active in your org. They are no longer maintained by FinDock after EOL. You can make your own risk assessment to determine if assignments should be removed and the classic permission sets deleted from the org.

(Classic) FinDock permission set descriptions

Please note that these classic permission sets are only available if the respective FinDock package has been installed.