Manage the team

Introduction

This tutorial briefly explains the functionalities of Qflow Team. This toolis used to represent the organization’s structure and its members in the system.

The elements that make up the organizational model are nodes, groups and users. In the next section, we will explain how to create each one, athe permissions that can be given to users within each of the elements, and how users can participate within work queues.

Node structure

The site’s sidebar menu displays three buttons with which you can show/hide the solution tree and operate with the organizational nodes of said tree (Show disabled nodes and Create a new organizational node).

Within each organizational node, you can see the hierarchical structure of the organizational model and select the element on which you want to operate.

There is a node that serves as the root of the structure. It has child nodes and can be displayed either open, expanded (showing its children), or closed.To expand a node you must click the triangle that is on the left.

In this example, a node for “Administration” was created with two subnodes (children) “Finance” and “Human Resources.”

To view the groups and users associated with the nodes, double click on them.

Groups:

Users with shared properties can be grouped together.
They can contain other groups.

Users:

They represent Qflow users.
They can be members of multiple groups.
They can be in a single node.

Clicking these different buttons allows you to create the users or groups of the node:

In this tutorial, an “Employee” user and a “Managers” group are created. Once the users and groups are created, the window will appear as follows:

Work queues

Another property of nodes is that they can behave like work queues. Work queues can be chosen as task recipients. When a task is assigned to a node that behaves as a work queue, any user who has permission to act on that queue can reply to the task.

Configure a work queue

Within the node properties in the “Advanced” section, the “Behaves as a work queue” option must be checked.

After enabling the option, the configuration button becomes available. This button allows configuring the permissions and validity of the work queue. When that button is clicked, the work queue properties will appear. The node icon in the tree changes once it’s defined as a work queue

Fig. 266 Work queue properties configuration button

The “Security” section of the work queue’s properties form allows you to define permissions for it. By clicking on the “+” button you can add the groups and/or users that will participate in the queue.

To add them, start typing the name and a list of available users and/or groups will be displayed.

Once it is selected, a table is displayed to configure the permissions.

You must select “Allowed” or “Denied” next to each permission as shown in the image below. If you check the “Inheritable” option, the permission will be applied recursively.

This means that the selected user, role or group will have permission on the node being edited and also on all descendant nodes of that node. For example, to grant a manager permission to “View” tasks in the work queues of an entire branch of the organization, grant them “View” permissions on the root node of that branch and select the “Inheritable” option.

The possible permissions are:

Visualize: allows access to the work queue’s inbox.
Actuate: allows responding to a task in the work queue.
Sign: This permission is not used in Qflow, but it is used in Q-expeditive, which is built on top of Qflow. It allows signing.

Work queues's permissions — Fig. 268 Work queues’s permissions

In the “Permissions” section, you can view the permissions of users on the work queue: whether the user can visualize, actuate and/or sign.

In the “Notifications” section, it is possible to specify the sending of notifications when an event related to the queue occurs. To specify the events that should trigger notifications, check the options you want from the following:

Work queue's notifications — Fig. 269 Work queue’s notifications

In the “Advanced” section you can define the validity period of the queue.To set a validity period, check the option “Defines period of validity” and select the start date of the period (“Valid from”) and the end date of the period (“Valid to”). The node will only behave as a work queue during that period.

Manage tool permissions

Within “Settings” in the top menu of the site, in the “Manage tool settings” option, you can configure various permissions.

For each permission, the panel shows which role the permission is for, the role description, a list of allowed actions, and a list of denied actions. The list can be filtered as usual and can also be modified by adding, removing and modifying elements.

There are three types of permissions defined:

Access tool
Manage configuration
Manage security

To add a permission to the previously created “Employee” user:

Click on the “Add” (+) button. This prompts Qflow to display a role searcher.
Select the permission’s recipient. To do this, type part of the user’s name, in this case “Employee”, into the search box (where it says “Start typing …”) and when you see it in the list that appears, select it.

When a permission’s recipient is selected, Qflow displays a form to select the actions included in the new permission.
For each of the permissions shown on that form, indicate whether it is allowed or denied.

Finally, if you want more information that was not covered in the tutorial, you refer to the Qflow Team manual.