Team based sharing #101
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
teamson 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 userfield anAdd a teamautocomplete 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.
Merged by #122