I. Add/configure an approver node

1. Path for adding an approver node

In the Admin Console, choose “App Management” -> “Approvals”, and then click a template to enter its details page. On the “Rule Settings” tab, click “setting” of “Approval process” to enter the process settings page, and then click the plus sign (+) to add an approver node.


To remove an approver node, simply click the “X” icon on that node.

2. Configure/modify an approver node

There are many types of approver nodes. Different types of approver nodes lead to different approvers of the nodes.
(1) Approval by specified members
Admins specify members as approvers for this node. For all applicants, approvers of this node are the same.
When multiple members are specified, you can specify “Agree by Anyone”, “Agree by Everyone”, or “Approve in Sequence”.

(2) Approval by specified superiors
To use this function, you need to set superiors for members in Contacts.
After the superior for a certain tier is set, the superior will be automatically set as the approver according to the Contacts settings.
From bottom to top: Starting from the immediate superior of the applicant, the application goes from the department of the lower level to that of the higher one. A Tier-3 superior is higher than a Tier-2 superior.

From top to bottom: Starting from the top superior, the application goes from the department of the higher level to that of the lower one. A Tier-2 superior is higher than a Tier-3 superior.

(3) Approval by continuous multi-level superiors
To use this function, you need to set superiors for members in Contacts.
After the top superior is specified, the application goes from the applicant’s direct superior upward until the specified tier according to the applicant’s identity.
Applicants of different identities may face different numbers of superiors.
For example, when an approval process is set to be passed on to the “Top Superior”, if the applicant is a “Tier-3 Superior”, the approvers are “Tier-2 Superior” -> “Top Superior”.
If the applicant is a “Tier-4 Employee”, the approvers are “Tier-4 Superior” -> “Tier-3 Superior” -> “Tier-2 Superior” -> “Top Superior”.

(4) Approval by specified department heads
To use this function, you need to set heads for departments in Contacts.
After the head for a certain grade is set, the head will be automatically set as the approver according to the Contacts settings.
From bottom to top: Starting from the department head of the applicant, the application goes from the department of the lower grade to that of the higher one. A head of Grade 3 is higher than that of Grade 2.
From top to bottom: Starting from the head of top department, the application goes from department of the higher grade to that of the lower one. A head of Grade 2 is higher than that of Grade 3.
When a department has multiple heads, the approval will be proceeded according to the “Agree by Everyone” or “Agree by Anyone” settings.

(5) Approval by continuous multi-level department heads
To use this function, you need to set heads for departments in Contacts.
After the top department head is specified, the application goes from the applicant’s department head upward until the specified grade according to the applicant’s identity.
Applicants of different identities may face different numbers of department heads.
For example, when an approval process is set to be passed on to the “Head of Top Dept.”, if the applicant is a “Head of Grade 3”, the approvers are “Head of Grade 2” -> “Head of Top Dept.”.
If the applicant is a “Tier-4 Employee”, the approvers are “Head of Grade 4” -> “Head of Grade 3” -> “Head of Grade 2” -> “Head of Top Dept.”.
When the approver sets the “Sequential Multi-level Department Supervisors” and specifies the endpoint setting as “Top-Down” or “Bottom-Up”, the approval process starts from the requester’s direct department supervisor and continues until the designated department supervisor (for example, if the requester is a superior of the department, the approval will move to the superior of the higher-level department).
If there are members with the position of multiple department supervisors in the same department, approvals will still proceed sequentially, and the approval order for multiple department supervisors within the same department is random.

(6) Approval by specified tags
To use this function, you need to set tags in Contacts.
After a tag is specified, approval is required by all members with the tag by default. You can also set the approval scope (“Agree by Anyone” or “Agree by Everyone”) for members with the tag.

(7) Approval by members with specified tags in specified departments
To use this function, you need to set tags in Contacts.
You can specify a department tier and a tag, and then the members with this tag from the applicant’s superior departments will be the approvers.
If multiple approvers are found, the application will be approved based on the configured multi-approver method (“Agree by Anyone” or “Agree by Everyone”).
This function is mainly used for approval by special identities in a department, for example, approval by “finance supervisor in tier-2 department” or “assistant manager in tier-3 department”.
If there are more than one person in the specified label, the order/sort of approvers will be displayed randomly.

(8) Approval by the applicant
The approver for the node is the applicant themself.

(9) Approval by members selected by the applicant
The applicant can select the approver for the node when submitting an application.
Unlimited: The applicant can select any members in Contacts as approvers.
Specified Scope: The applicant can only select approvers from a limited scope of members.
Single-Select: The applicant can only select one member as the approver.
Multi-Select: The applicant can select multiple members as the approvers, where the application will be approved based on the configured multi-approver method (“Agree by Anyone” or “Agree by Everyone”).

(10) Approval by linking members control
You can link the members control required in the template to set the members as the approvers. If the applicant has selected a member for the template control, the member will also serve as an approver for this approval node.

3. Department head for members belonging to multiple departments

When a member belongs to multiple department, the member needs to specify their department when filling in an application. In this case, the head of the department selected is the member’s direct department head for approval. (A department head is displayed with a special logo in Contacts.)

4. Differences between “direct department head” and “head of grade 2”

• A member needs to specify their department when filling in an application. In this case, the head of the department selected is the member’s direct department head for approval. (A department head is displayed with a special logo in Contacts.)
• Head of Grade 2 indicates the head for parent department of the department selected.
  As shown in the following figure, an ordinary member selects A1 as their department, whose parent department is A.
  1. If A1 has a head, the member’s direct department head is head of A1, and head of Grade 2 is head of A.
  2. If A1 has no head, the member’s direct department head is head of A, and head of Grade 2 is head of parent department for A.
  

5. Differences between “direct superior” and “tier-2 superior”

Direct superior refers to the immediate superior set for a member in Contacts.

• In case of “Bottom to Top”, tier-2 superior refers to the second-level superior, starting from the immediate superior of a member.
  As shown in the following figure, when Bottom to Top is set to Tier-2 Superior, the approver for Mike is Peter.
  
• In case of “Top to Bottom”, tier-2 superior refers to the second-level superior, starting from the highest superior of a member.
  As shown in the following figure, when Top to Bottom is set to Tier-2 Superior, the approver for Mike is Sam.
  

II. Multi-approver

1. Agree by anyone

When there are multiple approvers for a node, all of them will receive the approval notification. As long as one of them agrees, rejects, or forwards the application, the application will go to the next step.
When any approver forwards the application, the others do not need to do anything, and the alternative approver will be the next approval node.
When any approver rejects, the status of the application will be changed to “Rejected”, and the process ends.

2. Agree by everyone

When there are multiple approvers for a node, all of them will receive the approval notification. However, the application will only go to the next node after everyone agrees.
When any approver forwards the application, it has to be agreed by the alternative approver as well as the other approvers of this node.
When any approver rejects, the status of the application will be changed to “Rejected”, and the process ends.

3. Approve in sequence

When there are multiple approvers for a node, they will receive the approval notification one by one. Once they all agree, the application will go to the next node. That means, the first approver will be notified first, and the second approver will only receive the notification when the first approver agrees, and so on.
When any approver forwards the application, it has to be agreed by the alternative approver before the next approver is notified.
When any approver rejects, the status of the application will be changed to “Rejected”, and the process ends.