Form, active link guide, and application permissions

Permissions determine which access control groups can access forms, active link guides, or applications in the user client (browser). If a user does not have access to the object, it does not appear on the home page or in the object list for the user.

When creating a form, an active link guide, or an application, you must decide the permission for each group or role:

• Visible—Members of the group or role can select and view the object in the user client.
• Hidden—Members of the group or role can access the object through the workflow or by entering the URL in a browser, but cannot select the form on the home page or from the object list.
• None—Members of the group or role have no access to the object.

Giving the members of a group access to a form does not automatically give those users access to the fields in that form or to active links and active link guides that use that form. You must also assign group permissions to each field and related object.

If the form, active link guide, or application is configured to allow static permissions inheritance, the parent groups also inherit the permissions. For example, if you grant permission to a form that is part of a group, the same permission is granted automatically to all the parent groups in that group.

Similarly, when you map a role to a group, the role permissions for the application also apply to any ancestors of the mapped group.

The following figure lists the questions that you can ask to determine the access that users have to forms in AR System. You can use this flowchart for guides and applications as well: 

If a user is a member of a group that has permissions to a form, that user gets access to the form through a hierarchical group relationship. Also, web users can open Hidden forms with the correct URL, but the ability to use the form is controlled by field permissions.