User in Cards #170

New Issue

OVERLORD · 2026-02-04T17:37:32+03:00

OVERLORD commented

2026-02-04 17:37:32 +03:00

Originally created by @derrobin154 on GitHub (Apr 17, 2022).

If you delete/remove a user he should still remain assigned to the map to track this. Alternatively, introduce the function to lock a user.

Originally created by @derrobin154 on GitHub (Apr 17, 2022). If you delete/remove a user he should still remain assigned to the map to track this. Alternatively, introduce the function to lock a user.

OVERLORD added the enhancement label 2026-02-04 17:37:32 +03:00

OVERLORD commented

2026-02-04 17:37:40 +03:00

@meltyshev commented on GitHub (Apr 18, 2022):

Yes, you are definitely right 🤔

@meltyshev commented on GitHub (Apr 18, 2022): Yes, you are definitely right 🤔

OVERLORD commented

2026-02-04 17:37:48 +03:00

@nickbe commented on GitHub (Apr 20, 2022):

I guess somewhere during the next changes we have to think about how to manage this. I guess when a user gets deleted then there are several aspects which should be considered:

Technically for assigned cards there should be a simple way to replace the assigned user.
For projects and everything below them it's a completely different problem. All user data is by definition private. So no other user has the right to access data without the permission of the owner - not even the admin - which is very important.
This follows that it must be possible for a user to delete his/her account and that all previously shared projects, boards and cards have to vanish. This is the prime directive to comply with gdpr and other privacy protection laws. A user creates data and a user has a right to remove the data.
BUT if we talk about a company account then you are right in that we must be able to prevent exactly this. So when creating a new PLANKA instance we basically have to ask: Will there be private accounts OR company accounts. Depending on that either only an administrator can delete accounts (and he will have the option to replace assigned users or move projects boards to other users) or only the user can decide what to do with his projects. The he's the one who should be able to transfer projects and board to other users.

So a lot of decision making will be done along with user deleting. But the important thing is that we strongly stick to privacy laws.

@nickbe commented on GitHub (Apr 20, 2022): I guess somewhere during the next changes we have to think about how to manage this. I guess when a user gets deleted then there are several aspects which should be considered: 1. Technically for assigned cards there should be a simple way to replace the assigned user. 2. For projects and everything below them it's a completely different problem. All user data is by definition private. So no other user has the right to access data without the permission of the owner - not even the admin - which is very important. 3. This follows that it must be possible for a user to delete his/her account and that all previously shared projects, boards and cards have to vanish. This is the prime directive to comply with gdpr and other privacy protection laws. A user creates data and a user has a right to remove the data. 4. BUT if we talk about a company account then you are right in that we must be able to prevent exactly this. So when creating a new PLANKA instance we basically have to ask: Will there be private accounts OR company accounts. Depending on that either only an administrator can delete accounts (and he will have the option to replace assigned users or move projects boards to other users) or only the user can decide what to do with his projects. The he's the one who should be able to transfer projects and board to other users. So a lot of decision making will be done along with user deleting. But the important thing is that we strongly stick to privacy laws.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#170