Form Definition Permissions

Learn about the form definition permissions

Last published at: May 2nd, 2024

User Level / Application Role Level:

As an Admin user, you may grant View, Design, and Remove permissions on Form Definitions (private) to a user and an application role, mutually independent. If a user is associated with an application role, the permissions granted may be the same or more. Only the higher permissions between the two are considered valid to change the definition. 

 

Render Public Forms v/s Private Forms:

The public forms are rendered without view permissions. The private form instances are rendered to a user/application role with appropriate access, or else access is denied. The form instance task assigned to the current user is rendered with inherent view permissions.    

 

Manage Permissions:

You must navigate to the Create—Form Definitions page. Select the form definition from the list and click on the Security—Permissions menu option. 

 

On the Manage Permissions page, you may grant permissions to the user and/or the application role(s), assuming both are defined earlier.  You must type in the first three characters to search for a user or application role. Select the user from the dropdown and click the Add button to consider. Select the checkbox to grant View, Design, and Remove permissions. Click on the Save Permissions button to confirm the access. A confirmation message is displayed in the top right-end corner below.  

 

To view a user's System and Application roles, navigate to the Administration—User Management page. Select the user from the list and click on the View—Roles menu option.  

 

This page manages the user roles. Select the necessary checkboxes to align the responsibilities. Click on the "Apply" button to confirm the changes. The user has privileges to view and design the form definition through extended permissions from the application role.  

 

Lock and Unlock form definitions.

By default, an average user can only view the form definitions they have created or have permission to view. They can also view form definitions developed by other users if they permit them. Based on the “Permissions” assigned by the admin or the user who created the definition, the average user can “View,” Design,” or “Remove” the form definition.

The definition is locked to the user creating/modifying the form. There is no concept of building forms collaboratively, and the definition is unlocked only after the changes are saved and closed. 

Another user with View / Design / Remove permissions can unlock the locked definition and lock it for further modification. The first user cannot save the changes now that the definition is no longer locked to self. The application shall alert the first user on the lock status and the username who is making the changes. This safety check thus prevents the contents from being overwritten by concurrent usage.