Ciao
This conversation is very interesting, I'll add some clarifications and updates
(let me quickly introduce myself, I’m Marco from the Informal Learning Product Team in Docebo)
I see 2 main topics covered.
One is the visibility of the assets, the current behavior is the following:
If an asset is shared in different channels with different visibility, the Q&A visibility for this asset is merged, (the sum of the visibilities of each channel), are not segregated by channel
If I share an asset to the channel “Marketing” with Mario as an expert and visible only to the Marketing people
and
to the Channel “Sales” visible only to the salespeople and Luigi as expert
The 2 visibilities get merged, and salespeople can see marketing questions people in the Q/A and vice versa.
Same for the experts, they’ll see all questions in the assets regardless of who asked it.
This behavior fits perfectly with an approach of “sharing knowledge” and is widely used by our customers.
But in some scenarios, where segregation of visibility is mandatory, to manage visibility was necessary an additional effort by the admins, as to split visibility they had to share the same asset in different channels, different times.
For this reason, we are going to shortly release live (already testable in customer sandboxes) a feature called "cohort".
Basically, with Cohort, you can define “Visibility Groups” for a channel, and people within a visibility group can see Q/A, comments, and shared assets made only by people in the same visibility groups, admin, and experts (but not the ones of the users of the other visibility group)
Superadmins and Expert will be able to filter, to see Q/A, comments, and Assets only from one or more “visibility groups” with a simple filtering
Cohort is helping a lot in similar scenarios, but this is the typical case where first-hand feedback about the usage in specific business needs is very useful for us to evolve the feature, so if you have the opportunity to test according to your business case, please, feel free to give any feedback or suggestion
The second topic is about notifications
The platform notification currently works in this way.
Given I am an expert and an asset is shared in multiple channels including the ones where I’m an expert I receive notifications for all the ask the expert in this asset.
Was designed in this way to match the current behavior of an expert being able to see already all the questions in the asset, regardless of the author of the question is a member of a channel where the expert is an expert or not.
The optimal behavior in the use case mentioned above is
Given I am an expert and an asset is shared in multiple channels including the ones where I'm an expert I receive notifications only for the questions made by a member of the channel where I'm an expert
This is very good feedback indeed and makes more sense also given the approaching release of cohorts, so I’ll evaluate with my team.
thanks for the precious feedback
Marco.T