Grouped link share

[PVince81]

New design for public link shares:

• a link share is a set of permissions (permissions, expiration, password, etc) represented by a single oc_share entry
• a link share can have one or multiple recipients
  • each recipient receives a separate token: allows revocation of specific recipients
  • new table to map tokens to oc_share entries
• UI allows entering multiple email addresses but internally creates multiple tokens
• UI must display the grouped share as an expandable entry:
  • when collapsed, only show the grouped share name
  • when expanded, show every recipient by email
  • when no email, let the user specify an arbitrary name (stored along with token in DB)
• recipients can be added later, and receive email notification
  • personal note can be added when adding recipients (not sure if we should store this one to be able to view it again)

This makes it possible to manage the permissions of a given link share and for example set the expiration date to a later point for delayed projects, doing so in a single location. No need to manually send multiple link shares and set expiration individually.

Ref: personal note ticket #29935 #29937

@felixheidecke @pmaier1 let me know if I forgot anything

[PVince81]

• technical concept
  • UI changes
  • examine API endpoint changes
  • DB changes: new table, mapping, classes

[ownclouders]

GitMate.io thinks the contributor most likely able to help you is @rullzer.

[pmaier1]

Ref: Requirements for public link share mail input field #29695

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.