Team based sharing #101

Closed
opened 2022-01-31 17:17:48 +01:00 by mpeltriaux · 1 comment
Owner

Status quo

Single users can be added directly to the list of shared users of a dataset.

However, sometimes multiple users need to have or at least want to have access on the same dataset, e.g. users who work in the same department. One would have to add every user one-by-one by selecting their username on the share-by-user autocomplete field (if they do not use the share-link).

Idea

Teams

We could introduce teams on the user settings. Teams would simply consist of a title, a short description and a list of users, which are part of this team. Users can create new teams, add or remove users from their team or delete the whole team.

Team invitation

We should evaluate which way of adding users would be more efficient: Being free to add any user to our team without their approval or if they should get an automated mail, stating that they are invited to be member of the team XY and can confirm the invitation by clicking on a link, provided in the mail.

But then we would conflict with the 'not-allowed-to-click-links-in-mail' security policy of some user departments again...

Sharing with teams

We then could extent the share menu of a dataset, so that below the Add a user field an Add a team autocomplete field is provided. In here, we could add the team's name and select the one, we want to give shared access to.

In the background we can run the same share-logic as usual and add the team member to the list of shared users. The team itself would not appear on the list of shared users but the single users would.

# Status quo Single users can be added directly to the list of shared users of a dataset. However, sometimes multiple users need to have or at least want to have access on the same dataset, e.g. users who work in the same department. One would have to add every user one-by-one by selecting their username on the share-by-user autocomplete field (if they do not use the share-link). # Idea ## Teams We could introduce `teams` on the user settings. Teams would simply consist of a title, a short description and a list of users, which are part of this team. Users can create new teams, add or remove users from their team or delete the whole team. ### Team invitation We should evaluate which way of adding users would be more efficient: Being free to add any user to our team without their approval or if they should get an automated mail, stating that they are invited to be member of the team XY and can confirm the invitation by clicking on a link, provided in the mail. But then we would conflict with the 'not-allowed-to-click-links-in-mail' security policy of some user departments again... ## Sharing with teams We then could extent the share menu of a dataset, so that below the `Add a user` field an `Add a team` autocomplete field is provided. In here, we could add the team's name and select the one, we want to give shared access to. In the background we can run the same share-logic as usual and add the team member to the list of shared users. The team itself would not appear on the list of shared users but the single users would.
mpeltriaux added the
feature
label 2022-01-31 17:17:48 +01:00
mpeltriaux self-assigned this 2022-01-31 17:17:48 +01:00
mpeltriaux referenced this issue from a commit 2022-02-17 15:09:48 +01:00
mpeltriaux referenced this issue from a commit 2022-02-17 15:09:48 +01:00
mpeltriaux referenced this issue from a commit 2022-02-18 13:52:32 +01:00
mpeltriaux referenced this issue from a commit 2022-02-18 13:52:32 +01:00
mpeltriaux referenced this issue from a commit 2022-02-18 14:07:49 +01:00
mpeltriaux referenced this issue from a commit 2022-02-18 15:19:42 +01:00
Author
Owner

Merged by #122

# Merged by #122
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
btuelek referenced this issue from a commit 2024-12-05 13:18:37 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: IT-Naturschutz/konova#101
No description provided.