We often have forms where one group of users (submitters/approvers) should be able to see a piece of information whereas another group shouldn't.

We have found two ways of doing this:

1. Have a lookup-driven permission system where the current user's permissions are looked up from a custom database table, then field rules are used to hide/show information.

2. Create copies of the entire BP and add/remove fields as needed, then use BP Access Rights to control access.

Both methods have severe shortcomings. The first method requires creating custom database tables and keeping them up-to-date, and doesn't offer any sort of "real" security since field rules are just CSS that can be easily undone by technically-savvy users. The second method drastically increases the amount of work that needs to be done when changes need to be made to a form - the system administrator must remember to push those changes to each and every single "copy" BP. If the BP triggers workflows, copies of those workflows must also be created and maintained.

I think it's clear at this point that in order to push Laserfiche Forms to the "next level", some sort of granular access right system needs to be implemented. Ideally this would be both field-based (e.g. only certain users can read/edit certain fields/sections) and process based (e.g. if current_user is part of the Sales Staff group, use Message Start Event A that has Starting Form A attached, but if they are part of the Sales Managers group, use Message Start Event B.)

Are there any plans for stuff like this, or are we, as systems implementors, destined to spending countless hours manually creating and customizing these behaviors?