Hide root folders e.g "Shared with all"

Hi,

Is it possible within the configs to hide root folders “Shared with all” & “Shared with groups” or rename them, as my staff are very confused with too many folders and choices. As they only need “My Libraries” and “Shared with me”…

Cheers

Unfortunately, this is not supported at this point in time.

You find a statement by Seafile’s CTO regarding this feature request here.

Are you a Seafile Pro or Seafile Community user?

Many thanks for your prompt response.

We are a Seafile Pro user.

Paying customers have a greater say in the future development of the software. :wink:

I suggest you just leave a comment that you’d like this feature.

I’m no pro user but I still back the request. Personally I’d like just a flat structure like the old versions but I understand if this is not possible. However, having 3 “Shared with me” folders seems over the top and I could imagine that regular users get confused by it. We resell Filecloud at work and it just seperates it into “My Files” and a optionally named folder for all the ‘shared’ folders. By default, just called “Team Folders”. I think that works alright.

2 Likes

I am also not happy with the web client ux in this aspect.

Currently, the UI serves well if I use seafile personally (My libraries is the default view). I have deployed it for many organizations, everywhere the main use was: Collaboration on files. People are confused, why different libraries are in different places. People are confused, which kind of share link they should use.

From my point of view, it would be the best if the default view gave people an overview of what they have access to. My libraries, Shared to me (includes all kinds of shares).

Or, leaving it in the left panel, still divided into Mine, Shared, and being able to set default for all users (and they could change it in their settings if needed).

People have been complaining about this since seadrive moved to using the windows explorer cloud provider. I think the important question everyone is ignoring is what to do with libraries that share the same name. I haven’t seen any good answers for this, I don’t think mashing everything under one directory is not going to create other kinds of even more confusing problems. Personally I’ve had instances in the past where someone would share their “Photos” library, and it would collide with my “Photos” library causing a lot of confusion.