At the bottom of all forms, there is now a button that allows the creator or the reviewer to restrict access to creator and assignees. By checking the box, the user will further restrict any access and those without access will not be able to access information from this form instance. This will make it so that these form instances are only visible to the creator as well as any user that the form instance has been specifically shared with and/or assigned to. For the user(s) that have visibility to these form instances, they will display to them in their list of forms just like any other form instance. For those users without access, these forms will not be visible. Who can see the form instance if I select Restrict access to creator and assignees ? The creator of the form instance Any user or role listed as the primary assignee using the user list component with the binding Assigned to: Any user(s) or role(s) listed as the secondary assignee using the multi assign component with the binding Assigned users: Who sees the form instance if my form does not have the multi assign component enabled? If the multi assign component is not used on the form, it will only be visible to: The creator of the form instance Any user or role listed as the primary assignee using the user list component with the binding Assigned to. What can users without access to a form instance see? By default, the grid hides all form instances to which the user does not have access. Under the filters, the user can show restricted form instances, which shows limited information about each instance: Form instance ID Name of creator Creation date This can be helpful in case administrators need to track down form instances to which they believe they should have access, while at the same time it does not reveal any sensitive information. When a user enables Show restricted forms , all restricted information will show as [Hidden] in the grid. Does this override form permissions set for the project? Restricting access to a form instance will further restrict access but will not grant additional permissions that are not allowed as per the project settings. If a user/role has permissions to view Deficiency forms and they are not named in the Assigned to or Assigned users bindings on Deficiency 00002 , they will not see Deficiency 00002 If a user/role does not have permissions to view Deficiency forms and they are named in the Assigned to or Assigned users bindings on Deficiency 00002 , they will not see Deficiency 00002 If a user/role has permissions to view Deficiency forms and they are named in the Assigned to or Assigned users bindings on Deficiency 00002 , they will see Deficiency 00002 During a re-assignment, will the previously assigned user/role lose access? Yes, if a user/role was assigned and a re-assignment is needed, they should be added to the secondary assignee list using the multi assign component. If a user/role is removed as the primary assignee and is not added to the secondary assignee, they will lose access to the form instance. This also applies to any automated re-assignment that has been configured in the workflow settings for the form definition. Is there any configuration required to get the Restrict access to creator and assignees checkbox to show up on forms? No, the checkbox will show up for all users on all form definitions without needing any configuration. If you think admin configuration settings are needed, please vote on this idea in the SYNCHRO Control ideas portal. If the box is unchecked, what happens with the permission? Once the Restrict access to creator and assignees is unchecked, the form instance permissions go back to being controlled by the project-level permissions. That means that any user with the permission to view forms of that definition will see the form instance, regardless of whether they are listed as the primary or secondary assignees.
↧