-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add support for public shares of pages #515
Comments
Is there really a need for being able to share a page without its subpages?
The only option i can think of right now is read-only vs. editable shares. I think they should be independent so i can share the entire collective as read only and a page with its subpages as editable - or the other way around. These links may go to different audiences anyway. |
Being able to share a page with its subpages would be a very useful feature of course. There would be lot of scenarios where this would be enough. But I can imagine, there are also other scenarios in which a seperate possibility would be great. And yes you are right that you can use the files app for that, but I know for lot of users this ist not very intuitive (I handle it this way).
Yes, you are absolutely correct with this. |
+1 on this. It would be very useful. Thanks |
to whom it may concern: If we can support this feature with some financial means let us know. :) |
Ideas for implementation:
|
Is your feature request related to a problem? Please describe.
If you use collectives as cooperative knowledge base of your group/organization it’s a matter of time when the first member wants to share contents with non-members. This is easily possible at the level of collectives. For pages you can manage this a bit complicated via the files-app.
Describe the solution you'd like
I want to be able to:
Describe alternatives you've considered
A detour is to share page via the files app, which is not very intuitive.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: