Skip to main content
  Friday, October 09 2020
  1 Replies
  1.1K Visits
  Subscribe
Imagine you have an Intranet folder. And you have shared folders for all users, but other are private. All them stored in Dropbox.

Imagine this structure:

\CommonFolder1
\CommonFolder2
\User1
\User2
...
And now you mark "user1" as private and only allow that user to browse that folder. And the same form "user2". And so on.

And now the users create subfolders inside their dropbox. That's a filesystem.

And (logged in with user1) while you cannot directly browse to others users folders, you can search their subfolders (created by the search engine shortcode generator). That has no sense at all.

You should allow us to mark "user1" folder as private, and a check to "Propagate permissions to subfolders" or similar. Because the user will dinamically create and remove folders and subfolders.

In this scenario, the search engine is completely unusable.

Thanks.
A
3 years ago
Hi,

Thanks for adding your feature request here.

Imagine you have an Intranet folder. And you have shared folders for all users, but others are private. All of them stored in Dropbox.

Imagine this structure:

\CommonFolder1
\CommonFolder2
\User1
\User2
...
And now you mark "user1" as private and only allow that user to browse that folder. And the same form "user2". And so on.

And now the users create subfolders inside their dropbox. That's a filesystem.

And (logged in with user1) while you cannot directly browse to others users folders, you can search their subfolders (created by the search engine shortcode generator). That has no sense at all.

You should allow us to mark "user1" folder as private, and a check to "Propagate permissions to subfolders" or similar. Because the user will dynamically create and remove folders and subfolders.

In this scenario, the search engine is completely unusable.


In our plugin, all new categories will be created with Public state so users can see/search them on frontend presently.
The inheritance role from parent categories or current users is something that should be improved in the future.
Anyways, we noted that in our planning area.

Thanks a lot!
Cheers,
  • Page :
  • 1
There are no replies made for this post yet.