Idea #2044
Updated by Brett Smith almost 10 years ago
Acceptance criteria: * "Share" tab shows a list of users and groups who can already read/write this group. * "Add User" One of: ** "Edit permissions" button opens a dialog box with an editable list of users and "Add Group" buttons bring up our usual chooser. You groups who can make multiple selections from here. When confirmed, they already read/write this group. Changes do not get committed until you hit "Save changes". Click "Cancel" to abandon all get read permission, and modifications since opening dialog. *...or...* ** The list presented in the "Share" tab is reloaded to render them. editable. Changes take effect immediately. ** This requires changes to @users.list@ api permissions, see #2665. ** Workbench needs a special "create bulk permissions" method/route to support this. * Click a "trash" or "x" button to un-share with a listed user/group. * Click a drop-down to change permission type (read, modify, manage permissions). * Start typing name or email address in a "blank" row to bring up an auto-complete list (e.g., "PGP" or "Tom"). _(This requires changes to @users.list@ api permissions, see #2665.)_ * Choose a user or group from the auto-complete list. * The chosen user is added to the sharing list. * When a "user/group" input is edited, ensure the last row in the list is a "blank" row, and add a new blank row if necessary. * Screen captures for demonstration purposes. Not necessary [yet]: * Don't auto-refresh while the dialog is open, or worry about race conditions with other users/windows. Aside: This is a special case of a generic "Share" mechanism needed in Workbench. * Collections do not have "write" permission. * Collections are always owned by system_user. * When you create a collection, you get a free permission/can_read link which is owned by system_user. * Other than Collections, everything else should act pretty much the same as Groups. So -- hopefully sooner rather than later -- none of the Javascript or Workbench-server support will be specific to Groups. (But if it makes the difference between getting it done or not, "only groups are essential for this story" is the rule.) Other notes: * You can't necessarily tell whether another user is a member of a group.