Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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? 

2 answers

@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). 

0 votes
Iain Dooley Community Leader Aug 16, 2020

@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:

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:

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:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Trello

📹 What is Trello?

Hello Community!  My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. I'll be sharing with you a series of videos with my top tips on how to best use Trello...

846 views 14 30
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you