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/flow?
• Who can edit the form/flow?
• Who can view form/flow submissions?
• Who can edit form/flow submissions?
• Who can access the audit trail - available only for flows
• Who can administer the flow - available only 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. 

Who can start the form/flow

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

• Anyone(login not required) - anyone can use it even if they are not logged in.
• Authenticated Users(login required) - the form is usable to anyone who has an account (username/password) and is logged in to your tenant.
• Designers/Owner Only - the designer user who created the form/flow (owner) can edit, test or use the form. They must be logged into .
• 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.
  
  

Who can edit the form/flow

Form and flow owners (designer users that created the form/flow) can give other users (designers/non-designers) the capability to edit form/flows. This is particularly helpful if a designer user takes a leave of absence or leaves the company. The "backup designer" has the ability to make changes to the form/flow without having to download the form/flow(s) from the owner's account to the backup designer's account. The "backup designer" also can view related submissions by clicking on the Submission or Legacy Submission icons. The ability to edit submissions is granted by a different permission.

Users given this permission access the shared form/flow from the Shared Items tab even if they have the frevvo.designer role assigned to them. They can only edit the form/flow that was shared with them. They will not have the ability to create new forms/flows from the Shared Items tab. The ability to make changes to a form/flow is not available from Shared Items on the Important Items menu in a space.

To assign users the ability to edit forms/flows, follow these steps:

1. Open the Access Control wizard by clicking the Lock icon on the Forms Home Page, Flows Home Page or on the Form/Flow designer toolbars. 
2. Select Who can edit the form/flow from the Permission field dropdown.
3. Enter the roles that you want to grant editing capability to, separated by commas, in the Roles section. Templates are NOT allowed at this time.
4. Enter the users that you want to grant editing capability to, separated by commas, in the Users. Templates are NOT allowed at this time.
5. Click Finish or select the next option in the dropdown to continue with the Access Control List.

Users that have been granted the editing permission, access forms and flows that have been shared with them via the Shared Items tab on their Home Page. It will not work from the Shared Items selection in a Space or any other embedded scenario.

The Who can edit the form/flow permission does not apply if you are running with Confluence. Confluence users share form/flow editing by specifying the Forms Editor group on the /wiki/spaces/frevvo81/pages/441855914 screen. Users who will be sharing the editing function must be assigned to the specified group.

A browser notification message displays if the user who has been granted permission to edit forms/flows tries to modify their own ACL. will not allow the "backup designer" to remove themselves from the ACL list.

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 Page, Flows 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 or select the next option in the dropdown to continue with the Access Control List.

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 in the SUBMITTED, ABORTED or ERROR states. Submissions in the PENDING, SAVED or WAITING states can only be deleted by the tenant admin, flow admin or designer user that created the flow. Refer to the Deleting Submissions for more information.

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 Page, Flows 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 or select the next option in the dropdown to continue with the Access Control List for flows.

Who can access the audit trail - Flows Only

 The audit trail is accessed on a  user's Task List by clicking the View Task History icon. Roles/Users granted this permission will see theView Task History icon on tasks in their task list.

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

1. Open the Access Control wizard by clicking the Lock icon on the Flows Home Page or on the Flow designer toolbar. 
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 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 flow encased in curly braces to act as templates for dynamic access.
3. Click Finish or select the next option in the dropdown to continue with the Access Control List for flows.

This permissions let a user abort, reassign and reset tasks that are not assigned to them. These administrative tasks are no longer restricted to tenant admins.

The designer can delegate these tasks to additional users/roles by assigning them in the Who can administer the flow section of the Access Control dropdown. Any user/roles listed here will be considered a Flow Administrator.  As such, the Modify Task icon on a task in the task list will be displayed. Tenant admins and designer users get the Modify Task icon by default. 

To assign user/roles as Flow Administrators, follow these steps:

1. Open the Access Control wizard by clicking the Lock icon on the Flows Home Page or on the Flow designer toolbar. 
2. Select Who can administer the flow from the Permission field dropdown. 
3. Enter the roles you want to assign as flow administrators, separated by commas, in the Roles section. You can enter control names from your flow encased in curly braces to act as templates for dynamic access.
4. Enter the users you want to assign as flow administrators, separated by commas, in the Users section. You can enter control names from your flow encased in curly braces to act as templates for dynamic access.
5. Click Finish to save the completed Access Control List.

User jerry has been designated as a flow administrator for the Expense Report but not for the Time Sheet workflow. When Jerry logs into , his task list will appear as shown:

The Modify Task dialog allows a 'flow admin' to execute any one of abort/reassign/reset functions.

When searching for tasks, if a flow is chosen, and the user is a flow admin for it, then all tasks for that flow display. If no flow is selected, then all tasks, even those that the flow admin has not participated in, plus tasks for which the user is a flow admin will display.

Shared Items

Submissions

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

You can add the Shared Item URL to your your existing Space so that a logged in user with the correct permissions will be able to access form/flow submissions from the space menu. The submissions link is automatically added when you create a new space.

Designer ACL

The functions needed to edit forms/flows are only displayed when users given the permission access the Shared Items tab from their Home Page if they are a designer or by clicking the icon on the Task List. The ability to make changes to a form/flow is not available from Shared Items on the Important Items menu in a space.

The functions provided to edit forms/flows from the Shared Items tab, do not include the option to delete or copy them. Deletion of a form/flow is not available to the "backup designer".  Forms/flows can be copied by the download/upload functions.

The backup designer has the ability to run the Refresh Searchable Fields process to update previous submissions with changes made to Searchable Fields by clicking on the Refresh icon. This process can be run for a for a particular form or flow. Click the links for the details.

Let's say users Jack and Jill are both given the ability to edit the Expense report workflow. Jack logs into the flow designer and begins to make changes. When Jill logs in, she will see the error shown in the image:

 

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. Jerry 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. Jerry, Jack, Jill and Sue are flow administrators so you will see the  Modify icon in the images of their task lists.

The  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 (Jerry). If Jerry 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 rule for this example.

To comply with these requirements, the company 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 , Tom's Expense Reports appear on his task list. The 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 , 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 edit the submissions or delete SUBMITTED, ABORTED  or submissions reporting an error condition, if necessary.

When Jack logs into , 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 edit the submisions and SUBMITTED, ABORTED submissions or submissions reporting an error condition, if necessary. 

When Jill logs into , 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. He can edit the submisions and SUBMITTED, ABORTED submissions or submissions reporting an error condition, if necessary.
 

When Jerry signs on to 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 selects all the submissions and tries to Delete them this 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  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.