Idea #2044
Updated by Tom Clegg about 10 years ago
Acceptance criteria: * "Share" tab shows a list of users and groups who can already read/write this group. * One of: ** "Edit permissions" Share button opens a dialog box with an editable a list of users and groups who can already read/write this group. Changes do not get committed until you hit "Save changes". Click "Cancel" to abandon all modifications since opening dialog. *...or...* ** The list presented in the "Share" tab is editable. Changes take effect immediately. * Click a "trash" or "x" button to un-share with a listed user/group. * Click a drop-down to This change permission type (read, modify, manage permissions). does not get committed immediately. * 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.)_ permissions.)_ * Choose a user or group from the auto-complete list. * The chosen user is added to the sharing list. list, but permission is not assigned yet. * When a "user/group" input is edited, ensure the last row in the list is a "blank" row, Click "Save changes" to commit. * Click "Cancel" to abandon all modifications since opening dialog. * Click Share button again to refresh current permissions and add a new blank row if necessary. adjust from there. * 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.