FEATURE: Persona with default extensions selected about azurechat HOT 3 OPEN

This gets my vote as well. To achieve this while we wait for the feature, I have made the following chage:

And then I manually added the extension ID to the corresponding persona in CosmosDB.

Then, when a user starts a persona chat, the correct extension is automatically set. I also hide the list of extensions on the chat home page to avoid our users from getting confused and picking the wrong thing.

from azurechat.

This is a much cleaner way of doing it. This gets my vote as well.

from azurechat.

@dpayne-voss That is a good solution for now but while trying your solution, I realized that we might probably get the wrong idea from @thivy by making Persona and Extension isolated.

I am confused now. I tried to log in with 2 different users, Admin, and user.

With admin user, I tried to create 1 Extension to AI Search and published it, Also created 1 Persona.
Login with user, on the UI portal, it does not show "Reporting" menu, which is good, but users also see Personas and Extensions menu where they can create their own Persona, so each user can define their own Persona and Extensions, not the one defined by Admin.

But the user also sees the extensions created by Admin without permission to publish but is still able to Save it. This confuses me what is the main purpose of letting users save an extension created by Admin? The user can create extensions as well.

In a nutshell:
Admin can NOT see Extensions and Personas created by User.
Users can see Extensions from the admin if they are published, but can not see Admin's Personas.

from azurechat.