Make Playground Access Optional via Admin Panel

[jeannotdamoiseaux]

I would like to suggest adding an option in the admin panel to enable or disable access to the “playground” feature, similar to how document uploads, model access, and web search access are currently managed by admins.

Most of our users do not utilize the playground feature and often find it confusing. Allowing admins to control its availability would help streamline the user experience and reduce potential confusion, making the interface cleaner and more relevant for our user base.

If there is agreement on this approach, I’m happy to work on the implementation.

[17jmumford]

Agreed, would be great to hide the playground for default users.

[Classic298]

+1

[jeannotdamoiseaux]

Given the interest, I’d like to take on the implementation of this feature.

I have a specific question regarding translations:
What is the usual procedure for a new feature? Should I provide translations for all supported languages from the start (e.g. via LLM translations), or is it sufficient to submit my changes in English and Dutch only?

[tth37]

You don't need to worry about providing all translations initially. Just wrap all translatable content (user-facing strings) with the $i18n.t() function, and optionally run npm run i18n:parse to update the translation files with new keys. It's perfectly okay to submit your changes with only English (and Dutch) translations filled in, leaving others empty.

[Classic298]

created a PR, let's see #13480