Given the current implementation of the backend list sharing feature, an owner of a list can create a one-time share link to send to someone else who can use it to get the permissions set by the owner for that link. However, users should have the option to somewhat customize these for their needs. The details of this customization must fit the following constraints for a PR to be accepted for this issue:
- Lists have a hard 90-day limit for expiration and users should be told this when creating a share link.
- List share links should have a usage limit of 100, meaning 100 users can utilize the share link. A user creating a share link can specify the link's share limit but only up to this maximum of 100.
- If a user has already been shared the list, 1 of the following outcomes must occur:
- If the permissions are higher than what the user already has been granted, their permissions will be updated with those set in the share link in the database (this behavior is already implemented, but no check is done if the user already has permissions; it's just an update without any check).
- If the permissions are lower than what the user already has, no update happens to their permissions and they are notified of this without any usage of the link being done.
- If a user owns the list and tries using a share link for it, no update should occur and they should be notified briefly before being redirected.
Given the current implementation of the backend list sharing feature, an owner of a list can create a one-time share link to send to someone else who can use it to get the permissions set by the owner for that link. However, users should have the option to somewhat customize these for their needs. The details of this customization must fit the following constraints for a PR to be accepted for this issue: