Contextual Search
under review
Nibu Thomas
We have multiple projects and we have customers who may use only some of the products. The capability right now is that we can enable search across projects (which works great for those who use all our products) But for those who don't, we'd want a way to contextualize the search filter to only the products that they have access to.
Log In
D
D360 Product Management
marked this post as
under review
K
Kavya
Hi Nibu Thomas,
Thanks for sharing this! Contextualizing search so customers only see results from the products they actually use makes a lot of sense, especially when you’re managing multiple projects with different access levels.
This isn’t something we support today, but it’s a valuable idea and we’ll consider it as it gains more traction and aligns with our roadmap.
To understand your setup a bit better, could you share more about how you’re organizing things?
-Would you expect the search filter to adapt automatically based on the user’s permissions?
-Or would you prefer manually configuring which projects should be searchable for specific customer groups?
-How are customers with partial product access handled today?
-And just to clarify, how are multiple products arranged across a single project on your side—are they separate sections, categories, or something else?
Your context will help us evaluate the best approach moving forward
Nibu Thomas
Kavya
One way could be to allow the user to choose a default workspace. Another could be to use analytics. Which content are they clicking on the most. That becomes default.
It's not partial product access. It's a product line that they either have access or don't. For example Whatfix Web customers may not always have a subscription to Mobile or Desktop versions. Right now, their access is controled in the product. But when it comes to documentation, everyone can access everything (whatever is public)
Seperate product content is arranged in workspaces (versions).