Different persona experiences?

[Hampus1]

Hi, I've got a question regarding creating different experiences for different personas in Employee Center.

As an example, If I have 3 different types of personas in my organization: Office user, Backoffice user and Store user. All of these three different personas are going to use self-help in some manner so I want to onboard all of them to ESC. The three different personas have very different needs and work related tools so I want to in some way create a tailored self-help experience for each of them.

If a Store user logs into the ESC they will see requests and articles related to Store issues or routines. Also be able to see open incidents and requested items for their direct store.

The Backoffice user would be able to see much more IT related requests and incidents, maybe be able to see outages and get access to admin access related items.

The office user would be able to see basic catalog items and their own incidents and requests.

Is this something that is possible? The closest thing that I've seen is probably the "curated experiences in ESC" but I have not been able to see any practical demo or example of this? I have not been able to see any specific taxonomies for user criteria if I want to limit access or set up a specific taxonomy for Office, backoffice or store. I want to be able to impersonate these three different personas and access ESC and see a tailored portal for those specific personas.

[palanikumar · Accepted solution]

You can create User criteria in Catalog Item to make it visible for specific role

[Hampus1]

That must have slipped my mind... But so the idea of ESC in that scenario is that we can add all of the products and categories directly in the taxonomy but with role limits to the different catalog items or categories to make the page show specific items for specific personas?

I guess that would make sense since the dynamic popularity and lists would "automate" setup of featured topics and commonly used requests.

[Susan Britt]

Correct, the visibility of the content within a Topic (e.g., catalog item, knowledge article) is based on the individual record's access.  As @palanikumar mentioned, using the User Criteria for those will limit the access as needed.  You do not need roles set on the topics.