"Restrictions" add-on (beta)

New feature allows to have a strict control over users' operations performed in a space. That is you can set what exactly can and cannot be done with the cards under certain conditions.

The main scenarios of using "Restrictions":

  • Organizing a strict workflow. That is controlling the path the cards go through depending on their type

  • Creating the rules of the movement of cards through statuses. For example, the card cannot be moved to the next stage unless the criteria to fulfil the task haven't been met.

Where to find it and how it works?

«Restrictions» are rules that prevent users from performing certain actions.

In order to get acquainted with the new instrument and create your rules click on the "Restrictions" icon in the right side panel of the space.

The work of this add-on is similar to the "Automation" one. You can create - triggers/conditions that won't allow users to perform certain actions.

E.g: if a card is located in a certain column, the users cannot move it back to the previous column.

There are now the following conditions available:

  • Previous card path is;

  • Card type is.

And the following actions/restrictions:

  • Restrict movement;

  • Restrict creation.

Only space admins can create Restrictions. Restrictions are applied to all users on a space. Be careful and attentive, so that your Restrictions don't contradict with other processes and don't interfere with your workflow.

After saving the Restriction will appear in the Management tab. You can edit or remove it (deleting is only available for the space users with administrative access rights).

Let's take a look at an example

Imagine that it's important that your employees finish the work on a task and don't give it up if the task is challenging.

Then you can create a restriction, that won't let users move the tasks they've taken back to the queue.

  • Set the condition "If": previous card path «Doing»;

  • Add additional info: card type "Bug";

  • Add restriction "Then": Restrict movement in "To Do".

Thus, if the employee starts working on a card with a "Bug" type, they wont be able to put it back to the queue and will have to proceed working on a task till the end.

Sounds good, but not enough?

We are now working on developing the add-on. We are planning to add more available trigger, conditions and actions, that can be restricted.

You're welcome to share what actions you'd like to control, what actions and conditions you'd like to see. Please reach out to our Support team in the chat with your ideas and feedback!