A board just for collecting cards would be cool

• Please use the 👍 reaction to show that you are affected by the same issue.

A board just for collecting cards would be cool. All participants of the board can move their cards there without seeing the cards of the other participants. It would also be sufficient if the cards of the other participants could not be clicked on/opened. In other words, a similar function to the collection folders.

Why? In many companies there are internal processes in project management where it is not allowed to see the contents of the other cards. If one were to do this in such a way that each employee can share his or her own temporary board, then the person with whom all the cards run together would possibly have hundreds of boards.

Therefore, a collective board makes a lot of sense

The following function would be useful:

If a card is moved to the shared board of another user, the cards of other users with whom the board was shared can also be viewed there and edited under certain circumstances. “Allow editing” always releases the entire board. It would be cool to be able to fine-tune this so that you can’t click and view other users’ cards.

This is really useful for workflows in internal company application procedures!

Does this suggestion make sense? Is there agreement or have I overlooked something?

Start by reviewing the existing collection-folder and shared-board behavior referenced in the issue. Clarify whether other users’ cards must be hidden, merely unclickable, or editable under specific conditions, then identify the board-sharing entry points and relevant tests in the repository. Done means the permission model is agreed and card visibility, moving, and editing behavior are covered.