Added a way for organizations to prohibit providers (#1105)

app/MindWork AI Studio/wwwroot/changelog/v26.10.1.md

@@ -24,6 +24,7 @@
 - Added a choice of how AI Studio encrypts API keys, tokens, and passwords when you export providers, data sources, or tool settings for your organization. The new protected format needs AI Studio v26.10.1 or newer on every computer that reads it, and your encryption secret stays the same. If you used AI Studio before, your exports keep the previous format until you switch, so your organization can update all computers first. You find the choice in the app settings, under Enterprise Administration.
 - Added organization-wide management for the format in which exports encrypt API keys, tokens, and passwords. IT departments can set it for all their administrators, either fixed or as a default which users may change.
 - Added a way for IT departments to ask you for your personal API key on the start page. When the configuration of your organization brings providers that need your own key, the start page explains how to get it, checks the key with the provider, and stores it for all of these providers at once. Thanks, Dominic Neuburg (`donework`), for this contribution.
+- Added a way for IT departments to prohibit providers. When you add a provider, you can still select a prohibited one, but AI Studio then tells you that your organization does not allow it. Providers you set up before stay in your settings, but AI Studio no longer uses them.
 - Added providers, profiles, and workspaces to your chat templates. A template can now decide which provider, and with it which model, and which profile a chat starts with, and keep its chats in a workspace of its own. A template for your mails, for example, can start every chat with a provider that meets the confidence level your mailbox requires. You can still pick another provider or profile in the chat.
 - Added a way for IT departments to roll out chat templates that bring their own provider, profile, and workspace. Set the template up in the app, then export it as ready-made Lua code for your configuration plugin.
 - Added settings to the Assistant Builder. There you choose the provider, and with it the model, that the Assistant Builder starts with, the language in which the assistants you build answer, and the minimum confidence level a provider needs. Thanks, Nils Kruthoff (`nilskruthoff`), for this contribution.