Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Introduction
There are two elements of security we will look at in this chapter:
- Controlling who can access an application.
Controlling Privileges within an application.
From PhixFlow Version 9.0 onwards,
2two user groups are automatically created
forwith each application:
appname
for people who need to use the application.appname_Admin
for people who need to manage the application and user access to it.
where appname
is the same as the application's name.
We will cover the
fundamentalfundamentals of security and access control in this chapter using existing configuration. For more information on this topic see:
- Controlling User Access to Applications.
- This page covers this topic in more detail and explains how to
setup - set up new groups and
role- roles.
- Managing User Groups and Privileges.
- This page goes into detail about setting up user groups, roles and privileges.
Access Control
Accessing
toan Application
Open the Properties of your application
Click on the
Insert excerpt _security _security nopanel true
tab
- All Users Can View Application, ticking this makes the application available to all. If you want to use this option consider applying it once the application is complete.
- User Groups, lists the groups that have access to our application.
- Selecting a group
- enables the delete icon
- allowing you to remove the group.
- Click on the group icon to see a list of available groups, these can be dragged into the list.
- For our example, we will leave the options as they are.
Testing
- First, we need to create a new test user as follows.
- In the Full Repository, right-click Users.
Click
and set:Insert excerpt _addIcon _addIcon nopanel true the username and password.
Enabled, tick.
Add the User Group, Users to the user.
Log out of PhixFlow.
Log into PhixFlow as the test user. You should not be able to see your application, click on the 9 dots to open the application selection window to confirm this.
- If you see an error stating you cannot access this application it is because you are loading the URL to directly access the application you just restricted access to. Use the URL that takes you in to the base PhixFlow, e.g. https://myserver.phixflow.com/phixflow/start.html?
- Now, log back in as yourself
- Update the test user's associated User Groups, adding the group associated to your application. This should be the My Application group, as illustrated below:
- Image Modified
- Log in as the test user and your application is now available.
Controlling Privileges in an Application
Within an application, there can be varying levels of permissions. Here we will look at adding permissions to a specific button but they permissions can be added to other content to restrict access and interactions.
- Open the Home screen so it is ready to edit.
- Click on the Orders button so the properties open. We can restrict who has
- permission to see this and use this button
- .
- Click on the
Insert excerpt _security _security nopanel true
- tab.
- By default All Users can View Data is ticked. This allows all users permission to see and click this button.
- Note it is possible to create user accounts that only have read-only permissions and therefore cannot click on any button. For more information on this see the links in the introduction section above.
- Untick All Users can View Data.
- As before User Groups lists the groups that have access to this button.
- Click on the group icon to see a list of available groups, drag the appname_Admin group into the list i.e. My Application_Admin.
- Select a group and the delete icon appears allowing you to remove the group.
- Click on the group icon to see a list of available groups, drag the appname_Admin group into the list i.e. My Application_Admin.
- Save your changes.
Testing
- Login as the test user created earlier.
- When the Home screen loads the Orders option will not appear:
- This option will only be available to users in the My Application_Admin user group.
Tip |
---|
In a future release the security will be assigned to the actionflow backing the button, this will result in all buttons using the actionflow only being available to users with the appropriate user groups. |