Restricting Custom Form Permissions on Projects
Here is the solution we are trying to solve for:
We use Workfront enterprise wide with multiple groups/processes onboarded into our system. One team has a very specific custom form with very specific questions that have to be answered in order for a project to be created. Once a project is created with that form they do not want users to have the ability to access the fields to change the values. They must remain intact in order for the project to meet strict compliance/risk standards.
I've set the form up so that only "admins" have access to edit the form, which works in theory. However, in my risk assessment I've been able to identify "work arounds" that creates the ability for end users to edit the fields.
- Anyone with manage access to the project, has the ability to add additional custom forms to the project.
- If they add a custom form that utilizes the same fields as the first form, without restrictions in place, the user can edit the fields on the second form and it will update the form fields on the original form.
- I tested removing manage access to the project and that will remove the owners ability to add custom forms but then they can't do other things that are required of a project owner, like changing the status, managing the finance, manage risks, modifying dates, etc.
- I have reporting that can/will show changes made to the field but this doesn't solve for removing the ability to edit the fields. Which is a compliance issue for these types of projects.
- I couldn't find a way to remove a users ability to add custom forms if they have manage access to the project.
- I can't restrict the ability to edit custom forms entirely on the project because there are certain fields that will need to be updated by a project manager and those fields don't live in the restricted section.
Any suggestions from the community on how to truly lock down fields/forms to end users with manage access?