-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App defined share permission flags #22220
Comments
@nextcloud/sharing @nextcloud/designers |
So (API wise aside etc). You are suggesting to have an extra field in the share table. And store some JSON thing there with a couple of bools? Should be fine in my opinion. |
Either that or we have a extended share permission table that we can then query if needed only |
@jancborchardt fixed witht he concept of the new sharing ui, right? |
No that would be a new feature that gets requested from time to time to give a more granular permission options is specific collaborative editing solutions like ONLYOFFICE or Collabora Online. |
Moved over from #12178 (comment) since this recently came up again with ONLYOFFICE.
There are several use-cases where apps like Collabora or OnlyOffice could provide additional sharing permissions.
OnlyOffice (https://api.onlyoffice.com/editors/config/document/permissions):
Collabora has quite fine granular options to set (DisableCopy, DisableExport, HidePrintOption, HideSaveOption, HideExportOption, UserCanWrite) but I think we do fine by just using our current hide download/read/write permissions for those. However in the future there also might be options similar to the ones in OnlyOffice.
Edit: It should be possible for apps to limit the availability of permissions like https://api.onlyoffice.com/editors/faq/sharing
Additional options that might be possible for link shares:
My proposal would be to allow apps adding custom permission flags that can either be true or false and then would be added to the additional settings
I've also did some quick mockups to make the menu restructuring a bit clearer:
Additional permissions would then pile up under the Can delete, only if the shared mime type would support them of course.
The text was updated successfully, but these errors were encountered: