Existe alguma forma de restringir quantas ou quais pessoas podem arrastar cartões?

[Atendimento Max Lira]

Existe um problema nos meus cards com relação a arrasto de cartões para lugares errados ou por pessoas não autorizadas, eu gostaria que em um quadro de 20 pessoas, apenas 2 conseguissem mover os cartões de colunas e posições, é possível? 

[Iain Dooley]

@Atendimento Max Lira one option is to add everyone to a team, then make the board "Team Viewable" but don't add the "non-admins" to the board as members. Then everyone on the team can see the board, and can comment on cards, but can't move the cards:

https://help.trello.com/article/791-changing-permissions-on-a-board

You can kind of prevent accidental moves using the API, for example this Trellinator function would prevent any list move by someone who isn't an admin:

https://gist.github.com/iaindooley/927f0c154c71f396cb46b9ad40bf44b1

But it won't really be enough to prevent *malicious* moves or multiple moves in sequence, because if someone were to move a card multiple times then by the time the API reacts to the second card move event, the card has been moved back to the very first list, and is then moved into the list it was incorrectly moved to in the first place (hahaha I wonder how well Google will translate that sentence into Portuguese ;)

Anyway, if you just want to prevent people from accidentally moving things then using the API is a reasonable option, if you want to really prevent even malicious moves or guarantee that no-one can move cards who is not supposed to, then you have to use the Team Viewable solution. You can read more about Trellinator here:

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Introducing-Trellinator-Automate-Trello-with-Google-Apps-Script/ba-p/925271

[milynnus]

@Atendimento Max Lira the way I had done it for one application was to inspect board updateCard actions for changes in idList on the card and the usernames (for my case it is more that just username) via a webhook or trigger and to use the json represent the change (aka action) to reverse the changes. This can be quite resource intensive because the same updateCard action can be used for other changes on the board. In my application, a card can only be moved to a specific list by sole person assigned to the card (aka owner of the card).