Hi Community, I’m dropping into this thread to give an update on this feature because the story is more complicated than the “Accepted” status probably communicates. The short story of that status is yes, we want to make it possible for Cards to live in multiple Collections, but… “it’s complicated.” 

The much longer story is that there are a lot of steps that need to take place in Guru’s infrastructure before we can implement this change. You’ve already seen a number of these changes go live over the past year, from the navigation updates in Summer 2022 through to last month’s conversion of Board Groups, Boards, and Sections to folders. We’ve just released a new feature called Workspaces that will add a level of flexibility to how our largest accounts configure access to Guru. Each of these updates has an impact on how we might handle the implementation of the “Cards in multiple Collections” feedback.

We see your feedback and comments and we appreciate that you’re taking the time to share! Know that the work is ongoing and as soon as we are closer to understanding timing, we’ll post an update here.

Any update on how we’re doing on this? @Ly Nguyen 

Capability to add cards across multiple collections is imperative for our use case.
Part of our workforce is flexible and outsourced. As a result, we leveraged folder-level permissions so that the managed service provider (MSP) could view a subset of cards available to permanent, full-time employees (FTE). The ability to single source a card, and make it visible to the MSP and FTE folders was helpful.
However, we’ve had to launch a second workspace. The behavior of sharing collections across workspaces translates to isolating the folder formerly known as MSP to its own separate collection, since shared collections across workspaces do not honor embedded hierarchy (folder-level permissions). 
If we could share cards across collections, this would be a cinch! Since we cannot, we need to advise our MSP and FTE users about looking for cards differently, in an additional space, to find what they need. As admins, this adds another layer of complexity and governance to our content cycle where we are trying to drive user adoption.

Tagging you as well @Marie Frei. It’s been 10 months since we’ve received an update on this (enough for this to become the most requested feature).

@David MacVicar / @Noah Carpenter - Do you know who owns this internally? It’s been 12 months since we’ve had an update on this.

Can we get some sort of update? Is this just too hard due to how things were architected from the get go or did this get put on the back burner because executives hopped on the AI hype train and completely derailed the roadmap?

@Skyler Reeves Sorry! I don’t work for Guru. So….no idea. 

Thanks @Skyler Reeves and everyone else for your continued engagement with the community. The owner of this feature ultimately rolls up to me and I am happy to provide updates here as best I can.

Since the last update, Guru’s priorities have shifted towards providing a more comprehensive product suite that incorporates the best capabilities from enterprise search, intranets and knowledge bases all wrapped into a single product to provide your employees with a Single Source of Truth. Investments into connecting your different applications together, providing generated answers from other sources of content, allowing you to manage the layout, look and feel, and content of your homepage (soon to be available via early access) have all been the priorities for the past year. You can see what we have released so far in 2024 in our release notes page in our Help Center.

Because our business priorities have shifted towards these new capabilities and the uptick in interest from the broader market, it means that this particular feature has been deprioritized for the time being until we get through the upcoming roadmap which will last through the end of the year. We will be hosting a virtual customer meetup in the near future to discuss what is on that roadmap, so be on the lookout for an update within this community with the details.

With that said, this feature has been the #1 requested feature for a pretty long time, over a year, if not 2. As much as I would like to prioritize this and knock it out of the park, our architecture needs a few more advancements before this can be fully realized. All of the changes we did last year around migrating from boards to folders incorporated a large investment into the hierarchy and permission model in anticipation of completing this particular feature. We made some great progress in this area, but we still need to do more. This particular feature, and the #2 “folder level permissions” feature are inextricably linked, and we do hope to revisit them in the future once we can reallocate resources to the underlying permission model that drives all of this.

Thanks again for your patience. When we pick this up again, I’ll make sure to provide an update here with the news.

Thanks for the update @Mitch Stewart. 

For everyone else, here’s the tl;dr of Mitch’s update:

• Guru’s focus is on expanding its market right now.
• Prioritizing other features helps Guru get new customers.
• This feature is hard to implement.
• Despite being the most upvoted feature, it’s not a priority right now.

As Guru grows, more and more people will keep updating this feature request. For what it’s worth, I don’t blame the product team here. Pressure from above causes all sorts of detours in a roadmap.

New Quarter. New Reminder. We’re up to 195 votes now on this 3 year old request. Users still want this feature more than anything else. New competitors in the market already have this and are starting to look pretty enticing.

Ah yes, the old ignore your existing customers for new customers approach. It's a bold strategy, Cotton. Let's see if it pays off for 'em.

Yep. Maybe they didn’t learn that growth through acquisition is logarithmic while growth through retention and expansion are hyperbolic. ‍♂️

Thanks all for your continued patience on this and I understand your frustration. As I had mentioned earlier, we will be continuing on our current roadmap through the end of this year so there has not been a change in priority for this particular feature.

We walked through our roadmap for the remainder of the year back in September during a Virtual Customer Meetup - this is the recording so please give it a watch so you are aware of what is coming.

As of November, we have released the initial versions of a lot of the features in that roadmap and will continue to invest in them for the next few months.

One item that is not mentioned during the virtual customer meetup was the addition of a foundational change to the permission model we have in Guru. We are adding the concept of an Owner role to the system which will allow you to assign ownership of particular objects to different people, effectively granting them “admin rights” to those objects without needing to give them the full Admin role. This foundational layer will be the final puzzle piece needed before we can begin to look at how that impacts the permission model needed to allow for Cards in multiple collections as well as things like Folders (i.e. ability to grant author access to Folders, another popular request).