What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders

Seeing Folder Structure without Sharing Folder

9 comments

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Victor Kuznetsov

    Hi Emily, thank you for your feedback. :)ย The thing is, Folders and Projects can belong to tens of other Folders and Projects (thousands, theoretically), and displaying all the different Folder paths from Folder structures not shared with users would make things pretty confusing. Perhaps a solution to this will be thought up eventually, but the only thing I can suggest currently is including the Folder paths into the Description field of the Folder/Project Info Panels. Let me know what you think, I'll be happy to answer any questions.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Ben Silverstein

    (Edited )

    Hi Victor,

    I'd like to explain how I feel this could work, based on some basic (but I'm guessing not immediately easy to program)ย logic.

    1. Provideย two different kinds of sharing for folders - Structure Sharing and Content Sharing (i.e. what Wrike already calls Sharing). For maximum flexibility, Structure Sharing should enable one to include or exclude Subfolders (but that ventures into Inherited Sharing territory)
    2. When Structure Sharing is enabled on a folder by User A forย User B, User Bย can see (depending on the level) the selected folder and folders within it, but not necessarily the Projects and Tasks within it
    3. When Structure Sharing is enabled on a folder by User A forย User B, User Bย can only see the Projects/Tasks within it if the Projects/Tasks themselves are shared with User B, or if a subfolder containing the Projects/Tasks has Content Sharingย with User B
    4. When Structure Sharing is enabled on a folder residing in an unshared parent folder, present that shared folder as top-level for all users lacking access to the parent folder (i.e. in Company Folders/Departments/IT, if User B has Structure Sharing access to "Departments" but not "Company Folders", present "Departments" as a Top-Level folder for User B, rather than "Company Folders")
    5. When a Project/Task is shared with User B, it would present within all Folders whose Structures have been Shared with User B. If the Project/Task shared exclusively resides within folders not shared with User B, present it as top-level (as currently is the case when a Project/Task is shared with someone lacking original Folder access)

    I hope this makes sense. I truly feel that if executed exactly this way, this would not cause any confusion. I can also tell you that you will overcome a major on-boarding hurdle with your platform: companies that want to give a strong foundation in Wrike by setting up best practice folder structures, while not giving consent to see everything within them. I'd be happy to chat more about this, whether on here or on a phone call, if your company sees value in it.ย 

    Is this helpful? 3
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Stephen

    Hi Ben, thanks for taking the time to expand on this topic, it adds so much value to the Product Team's internal conversations to see this level of detail. We'll make sure the relevant time is made aware of it ๐Ÿ‘

    Stephen Community Team at Wrike ๐ŸŒŽDiscover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Joe Quinn

    Our team has been really struggling lately with no solution for this in place.

    Thinking through this it'd be really great if you could provide permission to view folders separate from viewing the contents of the folders. Or an even simpler solution to this would be to show the full folder tree above the item that someone has permission to view. So if the folder tree is Department -> Team -> Client -> Project -> Task. So if you're added to a Project you already see all the Tasks inside of it but you'd also see the Client, Team, and Department folder the Project is in, but if you click those folders you can't view anything in them other than what you already have access to.

    I commented on another thread but saw that there was more activity here so I've included my message again below:

    ย 

    We desperately need this as well. We have a fairly intricate folder structure:

    -> Client Projects

    - - > Account Manager 1

    - - - > Client 1

    - - - - > Client 1 Project 1

    - - - - > Client 1 Project 2

    - - - > Client 2

    - - - - > Client 2 Project 1

    - - - - > Client 2 Project 2

    - - > Account Manager 2

    - - - > Client 3

    - - - - > Client 3 Project 1

    - - - - > Client 3 Project 2

    - - - > Client 4

    - - - - > Client 4 Project 1

    - - - - > Client 4 Project 2

    ย 

    And this is only for projects, doesn't include other things we use Wrike to keep track of. The big challenge is that most people are assigned access at the project level for projects they're working on and don't have permission to view the Client folder or folders further up the folder tree. So when most usersย login they see a bunch of random projects and folders scattered in an unmanageable, unorganized list. Those of us who have theย top level access have no issues, but once you're access starts to go further down all organization is lost.

    Is this something that's in the pipeline for development soon?

    Is this helpful? 6
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Angi Hast

    This is a huge struggle for us.ย  We have to align our folder structure a certain way to accommodate for budgeting and project alignment, so permissions get tricky.ย  When we start granting permissions, it destroys the users view.ย  Since they cannot have access to the base folder, their subfolders get thrown all over.ย  We really need a "view only" option to help keep the folder structures intact and organized for all users.

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Lisa

    @Angi Hi, I completely understand your need for this feature. Our Product Team constantly review the feedback posted here when discussing developments internally. This particular feature is not currently on their short-term roadmap but we have made our Product Team aware of this thread. Thank you for sharing.

    Lisa Community Team at Wrike ๐ŸŒŽDiscover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Laetitia Boden

    I mirror these comments. We are planning on sharing tasks with contractors, but as they won't have access to the entire project, or other folders, their tasks are not easily identifiable by project/client. Even if the different projects could remain it would go a long way to help

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Tim Batt

    We also DESPERATELY need this ability to allow shared users to see the tree structure.ย  Without it, they have no structure, context, or organization to their tasks.ย  When I go to their desks to assist, or reference a project during a consult, I can't help them without doing a "search".ย  Instead I should be able to conduct an organized, logical journey down a hierarchy tree ending at the task in question.

    The other related feature we need to accompany this enhancement would be some sort of "Lock Folders & Priority" checkbox when sharing the Structure.ย  Users sometimes change the order of tasks, or the folders they are stored in for their own preference.ย  That's OK, unless management wants the contributors to stick to the pre-defined order of tasks and the folder hierarchy determined to be the most appropriate.ย  We also use Wrike as a knowledgebase / wiki.ย  Some of those wiki entries have checklists/protocol and the tasks should not be re-ordered, nor moved into other folders. It needs to be consistent across the company for training.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Al Sape

    I agree with the last several posters.ย  I don't really understand the workarounds here, for example with Ben's, how do you create a Structured Sharing arrangement?

    It would be hugely helpful if the folder structure/hierarchy existing by team owners who establish them, would trickle down to users who can only see tasks in these folders.ย  I don't see the harm in allowing what would be largely "empty" folders and projects to be visible to users with permission to see tasks in those groupings.ย  Otherwise I agree fully with the others that this just creates a flat task list out of context, and you lose a lot of the benefit of Wrike.ย  This really underscores the importance of this as in most teams I think, as they grow more users with limited permissions are added, so over time most of the users of Wrike don't see the great hierarchy that Wrike offers, and that is really compromising things since this one one great feature isn't even able to be made available to most users, really too bad until there is a solution here.

    Is this helpful? 0
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: Seeing Folder Structure without Sharing Folder
[this list is visible for admins and agents only]

Community

Welcome ๐Ÿ––

Hi there! ๐Ÿ™‚ Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome ๐Ÿ–– Have you checked out this week's Release Notes yet?

Hey! ๐Ÿ‘‹ Curious about something? Visit How To to search and ask the Community for answers.

Welcome! ๐Ÿ‘‹ Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.