Skip to main content
Set up approval workflow with tags

Assign approvers to specific users.

Marko Klopčič avatar
Written by Marko Klopčič
Updated over 2 years ago

After you have divided your employees into departments and set up some managers for them, you will probably want to set up managers of your managers. Or you can create a completely new approval workflow with which you can assign approvers to a certain user, not necessarily a department.

How to make sure a manager receives approval requests from certain users only

You can limit access to Approvals by using tags. Tags are user-based labels that are used for data filtering across the application. For example, you can tag certain users with the tag "Approver Tom" and add this restriction to Tom's profile.

1. Go to Users > Tags to create a new tag.

  • Click on the button +Add tag at the top right corner.

  • Choose a name (e.g. Approver Tom) and choose a color.

  • Save.

2. Go to approver's profile (in this case Tom) and open Administrative restriction to assign tag Approver Tom into Approvals tag restrictions.

3. Furthermore assign this newly created tag to users who will have Tom as their approver. Do this:

  • by going to the user's profile and enter add tag in the field tags

  • bulk select all users and with actions manage tags (assign or unassign)

4. Logic behind it - Tom will only receive approval requests from users tagged with "approver Tom" (in this case from Michael) while still having access to the data of every user in the Sales, because of department restriction.

Setting up another manager for Tom

Setting up another manager for Tom is very similar. You would simply apply a new tag to Tom and then restrict another manager by the chosen tag. This would mean all of Tom's requests will be sent to the selected manager:

Any person with the Approval tag set to "approver-Mike" will receive Tom's approval requests now. Setting up several such admins would send an approval request to all of them. The requests are then resolved on a first-come-first-serve basis.

Did this answer your question?