Deleting a POST!

Question

We have a team of programmers and from time to time we have an outside programmer work on a task. We give them limited access to the trello board.

For some reason these temp programmers and able to DELETE tasks that we create. Even if they are given the lowest level of access they can still DELETE.

We have had two people quit now due to this issue. They spend time researching and creating a ticket only to allow someone else to delete it if they so desire.

MAJOR flaw in this system unless we are doing something incorrectly.

Daryl Williams_eibf1x · Answer

Too many other products out there to manage tasks. Not willing to go through all this to prevent a LOW LEVEL person from deleting posts.

Just simply time to move on.....if the Trello creators haven't thought of such a simple issue then hard to say what else they have missed. Not interested in sticking around to find out.

Thank you for responding.

Iain Dooley · Answer

@Daryl Williams that's right, there's no way to prevent someone from deleting a card if they have access to the board. Even if you use the API to protect against a card being archived, someone is able to archive and then delete too quickly so you can't prevent malicious action.

If you can't enforce this through process, here are some options:

1) Create a contractor board where cards are copied to and use labels to designate who should receive the cards. The cards can be linked to each other so people who are members of both boards can see them, but the contractors can only get access to cards they're added to. Using the API would be key to making this work efficiently because even though you can set up each one manually, it will be a hassle.

2) Add contractors to the team, but don't add them to the board as members, then set permissions on the board so that team members are comment and disallow anyone who isn't an admin from adding members to the boards. Only members of the boards will be able to move, archive, delete and edit cards, but anyone on the team will be able to comment. Use labels or lists to assign tasks to people rather than adding members