Security and Permissions
Security can be applied to Actionflows so that only those with sufficient permissions can run the Actionflow. In addition, if an Actionflow is assigned to a button and the user does not have permission to run the Actionflow, the button will not be displayed on a screen.
Permissions can also be set on form fields, table attributes and screens. For example, if a user does not have permission to view the form fields but runs an Actionflow that uses these fields, the Actionflow will show an error.
Access Permissions
For some items, you can specify a user group, e.g. Managers, or set of user groups, where only users in this group(s) have permission to see the item.
You must have saved the property tab at least once before you can change the permissions.
| Access Permissions | Description |
|---|---|
| All Users Can View Data |
|
User Groups | Available when All Users Can View Data is unticked. The grid contains a list of user groups that have permission to access to this item. To add a user group to the list:
To remove a user group from the list, click the tick box next to the user group then click the |
Worked Example
Here's a worked example using the Company Data (available from the Learning Centre).
In this example, we are using:
- A Company Merger Pop up screen containing:
- two manual drop down fields of the company name's of the companies to be merged
- two string fields showing the company ID's of the companies to be merged
- a button to initiate the Actionflow - this screen was created using the Tile no Buttons template
If you are completing this chapter as part of the Actionflow course and using a training instance, the data and screens have already been pre-loaded into the Actionflow Advanced Application. For this example, we'll be working on the Company Merger Pop up screen.
Limit Permission to Merge Companies
In this example, we'll limit the users/user groups that can run the Actionflow that merges two companies together.
Prerequisites
For this example, we'll limit permission to run an Actionflow that merges two companies together. This Actionflow was created in 3.04 Bulk Update Action Configuration. If you have not completed this chapter, expand the section below and follow the steps to create the Actionflows.
Alternatively, you can follow the instructions below to limit access to any Actionflow in your application.
Create Limited Access User
- In the
Full Repository, expand the 
Users section - Click
to create a new user who will not have access to run the acquisition- Login:
limitedaccess - First Name:
Limited - Surname:
Access - Password:
Phixflow123! - Enabled:
Apply the user- In the User Groups section, click the
icon- Drag across the User Groups, Actionflow Advanced Application and Users into the User Groups section of the Limited Access user
- There will be two Actionflow Advanced Application user groups. Ensure the one ending _Admin is not chosen
- Drag across the User Groups, Actionflow Advanced Application and Users into the User Groups section of the Limited Access user
Apply and Close all tabs
- Login:
Change Actionflow Permissions
- Open the Company Merger Pop up screen and open the Actionflow on the Run Acquisition button
- Open the Actionflow
Properties - Click on the
Security tab - Disable
All Users can Run Action - Click the icon and drag across the User Group, Actionflow Advanced Application_Admin into the User Groups section of the Security tab
- This limits the permission to run this Actionflow to just this User Group
Testing
- Log out and login as the user, Limited Access
- You should not be able to see the Run Acquisition button on the Company Merger Pop up screen