Live Forms v5.3 is no longer supported. Click here for information about upgrading to our latest GA Release.

Skip to end of metadata
Go to start of metadata

The Access Control feature offers the Live Forms designer increased flexibility when assigning access to forms/flows and form/flow submissions. Runtime access can be assigned to specific users/roles as long as they exist in your tenant. Also, the Access Control feature  enables the designer to use templates to define user and role lists to dynamically control access.

Tenant admins will continue to have full access to all capabilities and will not be subject to Access Control List (ACL) checks.

On This Page:

 

Access Control List (ACL) User Interface

Open the Access Control wizard by clicking the  Lock icon on the Forms Home Page or the Flows Home Page. It is also accessible by clicking the  icon on the Form/Flow designer toolbars.

Form designers as well as users with the publisher role are authorized to configure access control. The Access Control wizard makes the following permissions available for forms/flows:

  • Who can use the form - available for forms and flows
  • Who can view submissions - available for forms and flows
  • Who can edit submissions - available for forms and flows
  • Who can access the audit trail - available only for flows

 

ACL Permissions for Forms

 

ACL Permissions for Flows

 

Dynamic ACLs

Templates provide the ability to dynamically determine and restrict access to submissions/ task audit trails when assigning Access Control permissions. Templates are like variables in your form that can be filled in by the user, populated by a business rule or from a back end system.  Any item on the Access Control screens contained in curly braces is a form template and will be replaced with the value of the associated control. For example, the list below contains two fixed roles(reviewer and superuser) and one dynamic template based role - {acctmgrrole} : 

 

In the example discussed below, templates are used to navigate the flow to the correct employee in the Accounting department and to define user lists to dynamically control access. 

Important Note on Dynamic Access Controls:

Whenever a template is used to determine access control the derived set of users and roles are tied to the submission. They will only change if the submission is edited. Once a role is granted permission to a submission, that cannot be changed by editing the access control configuration in the designer.

 

Who can use the form/flow

Setting this permission determines who is allowed to create form/flow submissions. The choices for Form/Flow visibility are: 

  • Private  - only the owner can edit, test or use the form. The owner must log in to Live Forms.
  • Public In Tenant - the form is usable to anyone who has an account (username/password) and is logged in to your tenant.
  • Public -  anyone can use it even if they are not logged in.
  • Custom - The owning designer always has access to the form/flow. Additionally, the designer may configure selected users and/or roles (i.e. users with these roles) to have runtime access to the form/flow.

This topic is discussed in detail here

Who can view submissions

The designer can assign permission to view form/flow submissions to specific roles/users.  Any user with view access can view submissions in read-only mode. Submission deletion is not allowed. Templates can be used to dynamically determine at runtime which users and roles are allowed to view submissions.

To assign permission to view submissions, follow these steps:

  1. Open the Access Control wizard by clicking the Lock icon on the Forms Home PageFlows Home Page or on the Form/Flow designer toolbars. 
  2. Select Who can view submissions from the Permission field dropdown. 
  3. Enter the roles you want to grant view access to, separated by commas, in the Roles section. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  4. Enter the users you want to grant view access to, separated by commas, in the Users section. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  5. Click Finish.

Who can edit submissions

The designer can assign permission to edit form/flow submissions to specific roles/users. Any user with edit access can view, edit and delete submissions. Templates can be used to dynamically determine at runtime which users and roles are allowed to edit submissions.

To assign permission to edit submissions, follow these steps:

  1. Open the Access Control wizard by clicking the Lock icon on the Forms Home PageFlows Home Page or on the Form/Flow designer toolbars. 
  2. Select Who can edit submissions from the Permission field dropdown. 
  3. Enter the roles you want to grant edit access to, separated by commas, in the Roles section. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  4. Enter the users you want to grant edit access to, separated by commas, in the Users section. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  5. Click Finish.

Who can access the audit trail - Flows Only

 The audit trail is accessed on a Live Forms user's Task List by clicking the View Task History icon. Roles/Users granted this permission can view the events in the task history by clicking on the icon. 

To assign permission to view the audit trail, follow these steps:

  1. Open the Access Control wizard by clicking the Lock icon on the Forms Home PageFlows Home Page or on the Form/Flow designer toolbars. 
  2. Select Who can access the audit trail from the Permission field dropdown. 
  3. The Permission dropdown has two choices: All participants and Custom
  4. All participants indicates that any user that participated in the flow can view the audit trail for the task (provided they have access to the task). 
     

     
     
  5. Custom indicates that only users granted explicit access or with one of the specified roles can view the audit trail for the task (provided they have access to the task).  Roles and users can be selected via an editable combo-box control

  1. Enter the roles you want to grant audit trail access to, separated by commas, in the Roles section. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  2. Enter the users you want to grant audit trail access to, separated by commas, in the Users section. You can enter control names from your form/flow encased in curly braces to act as templates for dynamic access.
  3. Click Finish.

Shared Items

All users granted Submission Access, either by name or because they have a granted role, will see the Shared Item tab on their Home Page. Click on the Submissions  icon to view/edit them. 

You can add the Shared Item URLSpace to your Space so that a logged in user with the correct permissions will be able to access form/flow submissions from the space menu. 

Access Control/Shared Item Example

Let's consider an example to illustrate how this feature works. An Accounting Department in a company has three employees, Sue, Jack and Jill. There are three project catagories: Sales Demo, Customer Meetings and Infrastructure. Sue is responsible for processing Expense Reports for the Sales Demonstration project, Jack processes Expense Reports for the Customer Meeting project and Jill process Expense Reports for the Infrastructure project. The Accounting employees must have the ability to view and edit only the Expense Report submissions they processed. Jack is the manager who approves/rejects the Expense Reports. He can view all the Expense Report submissions but cannot edit them. Any employee in the company can submit an Expense Report. 

The Live Forms designer for the company creates an Expense Report workflow that displays the Expense Report form as the first step, then routes the request to the employee's manager (Jack). If Jack approves the expenses, then the workflow is routed to Sue, Jack or Jill based on the project category.

In the Expense report form, there is a dropdown control for the Project Type and a business rule that populates a text control named AccountUser with the user id of Sue, Jack or Jill based on the project type selected. You can populate the AccountUser control from a back end system or by user entry but we will use the business rue for this example.

To comply with these requirements, the company Live Forms designer has configured the Access Control screens for the Expense Report as shown:

Let's say Tom Cat submits three Expense Reports, one for each project type:

The workflow routes the three tasks to Jerry the Reviewer. It is his responsibility to approve/reject the expenses. When Jerry logs into Live Forms, Tom's Expense Reports appear on his task list. Th Access Control permissions above allow him to view the Audit trail for these tasks as well. Jerry approves all three Expense Reports and the flow is routed to the user id specified in the {AccountUser} template in the Expense Report form. Remember, we used this template when assigning access control. The Sales Demonstration Expense Report goes to Sue for final processing while the Customer Meeting Expense Report is routed to Jack and the Infrastructure Expense Report is routed to Jill.

When Sue logs into Live Forms, she will see tasks for any employees in the company who submitted an Expense Report for the Sales Demonstration project. Tom's will be among them. She can view the Audit trail for the flow as indicated by the  View Task History icon. 

When Sue completes the processing. and clicks on the Shared Item tab, she will see only the Expense Report submissions that she processed. She can view/edit and delete submissions, if necessary. 


When Jack logs into Live Forms, Tom's Expense Report for the Customer Meeting project will appear on his Task List along with any others submitted by company employees. Jack can view the Audit trail for the flow as indicated by the  View Task History icon. 

When Jack completes the processing and clicks on the Shared Item tab, he will see only the Expense Report submissions that he processed. He can view/edit and delete submissions, if necessary. 

When Jill logs into Live Forms, Tom's Expense Report for the Infrastructure project will appear on her Task List. She can view the Audit trail for the flow as indicated by the  View Task History icon.

When Jill completes the processing and then clicks on the Shared Item tab, she will see only the Expense Report submissions that she processed. She can view/edit and delete submissions, if necessary. 


When Jerry signs on to Live Forms and clicks on the Shared Items tab, all of the Expense Report submissions will be listed in the Submissions Table. Jerry is a Reviewer and can view submissions but he will not be able to edit or delete them. 

If Jerry clicks the Delete or Delete All icons, one of these deletion confirmation messages will display:

When he clicks OK, the deletion will be denied and one of these error messages will display.

Harry is the company Technical Writer. Since the form/flow visibility is set to Public in Tenant, Harry will be able to access the form/flow if he needs to submit an expense report after he logs onto Live Forms but he does not need permissions to view/edit the Expense Report submissions. When Harry clicks on the Shared Item tab it will be empty.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  • No labels