Form Composition: Access List


The Access List specifies how users are able to connect to a specific form. All users, active and inactive, can be listed, alongside details about their access and their relationship to your organization. This list is referenced when accessing a form if that form is setup to use the access list.

screenshot_composition_access_list

By selecting one or more users from the list, and then choosing an Access Type from the Assign to Selected menu, the desired access level will be established to your selection. Tags may be placed on one or more users to define special logic or features that should be applied in the actual form when a user with specified tags accesses the form. The number of times a user accesses a form is shown in the Access column; a log showing each time users accessed the form is availible from the Reports menu. To remove access from a user, the Denied access type must be used; once access has been granted, it cannot be removed, only revoked: this allows log entries to be listed after access is terminated. A further breakdown of the content in this section follows.

Username: the account name used to login to OmegaForms.

Access Type: An option chosen from a predefined list that specifies how the user is able to interact with the form. Examples include 1) Denied: the user is unable to open the form; 2) Reader: the form can be opened but changes to data cannot be made; 3) User: the form can be opened and edited; 4) Manager: able to access the form’s settings; 5) Designer: able to access the form’s composition and design sections; 6) Programmer: accesses the form as a Designer with additional access to Subscript sections.

Tags: if additional access levels with a form are desired, such as limiting certain functionality on the form to a certain group of users, user accounts can be tagged with keywords. For example, to allow additions to a datagrid only by a select few users, a tag of “” can be used. While any type of tags can be used (free-form tags, hashtags, triple tags), a manager must be cautious to prevent overlapping tags: a user with the tag “#AllowAdd” would match the tag “#AllowAddForTopOnly”.

Access: The number of times the user has accessed the form. Additional details about the access can be viewed from the Reports menu after selecting one or more rows from the Access List datagrid.

Last Accessed: The data the form was last accessed by the related user.

Helper and Helper Details: If Helper is checked, the user will show up in lists that identify the user can be sought out for help on the form. The Helper Details provide notes to other users when seeking out helpers, to ensure the proper helper is contacted.

Private Notes: Any generic notes that are desired by the managers for the selected users can be entered in this section. For example, specifying the reason for a change of Access Type or Tags can be logged in this area.