Add organizations (user groups)

[dboehmer]

Users should be organized in groups to grant permissions to an abstract group instead of managing individual permissions.

• a user might be part of multiple groups
• project permissions might be granted to users and/or groups
• groups have 1 owner
• group members may have the group admin role to add/remove members except the group owner
• no viewers/editors for groups
• a group can have viewer|editor|admin permissions for a project
• becoming a group member
  • users can request to get group membership
  • or group admins/owners can invite a user to a group
  • in either case the other party needs to confirm
  • if the request is declined, the request cannot be repeated
  • only the declining party can send a new request
• users may remove themselves from groups
• groups have
  • unique group name
  • must not collide with any username
  • display name
  • description
  • list of project permissions

[dboehmer]

Open question: How to create a UNIQUE constraint over two tables users and groups? Probably have both tables independently and do the checks in Perl.

Additional to do:

• add check to coocook_dbck.pl for duplicated names in users and groups

[moseschmiedel]

@dboehmer I want to attend the implementation of this issue ;)

[dboehmer]

probably also:

• a pending membership request/invitation can be canceled by the initiating party before to other replies

[dboehmer]

Just merged the first milestone for this: 60c5f9a92d8710bb41a729e2c1d186a8b10ab8dc

The branch https://github.com/dboehmer/coocook/tree/organizations still exists and needs to be continued:

Still left to do: complete invitation & confirmation workflow. Currently organization admins can just add users as they want.