mirror of
https://github.com/MindWorkAI/AI-Studio.git
synced 2026-09-27 07:13:38 +00:00
fe35630eff
Resolved 29 conflicting files. The notable decisions: Confidence: main's tool-calling gate (RequiredProviderConfidence) and this branch's local-RAG gate (DataConfidenceLevel) turned out to be the same rule on the same axis, so they are now one field. Both tool results and data sources raise it through RequireProviderConfidence(). The gate checks the level strictly and no longer exempts providers trusted by configuration: TrustedProviderIds is documented as applying to data-source security checks only, and organizations set confidence through DataConfidence .CustomConfidenceScheme instead. The security axis (DataSecurity, ERI, IsTrustedForDataSourceSecurityChecks) is unchanged. Provider creation: main's CreateProvider signature won (hfEndpointKind, capabilityOverrides, no model parameter); tokenizerPath was added to it and is set for every provider, including the new Hetzner, IONOS and LiteLLM. Provider and EmbeddingProvider combine the record parameters, Lua parsing and Lua serialization of both sides. File types: main's hierarchy (ODT leaf, WORD parent, PowerPoint without the legacy .ppt, TABULAR instead of DELIMITED_TABLE) plus this branch's SPREADSHEET parent with ODS and the xlsm/xlsb/xla/xlam extensions, which the runtime already reads. Both sides had added a conflicting HTML filter; the reading family keeps the name, and the export path uses a narrow HTML_DOCUMENT, following the existing LATEX/TEX split. Runtime: main's file_data.rs is the base, including the prompt-injection sanitizer and the extraction routes. Token counting and chunk segmentation moved into take_released, so they act on the text the filter has released rather than on text it is still holding. A failed count is logged and left out instead of ending the extraction, because the app counts such a segment itself. Data sources: the participating-provider checks of this branch are kept, and main's GetAllowedDataSources overload now builds on them. DirectChatService resolves the launched chat's data source options before the check, so filter and chat see the same options. .NET and Rust both build clean; I18N regenerated to 4060 keys.
1104 lines
60 KiB
Lua
1104 lines
60 KiB
Lua
require("icon")
|
|
|
|
-- ------
|
|
-- This is an example of a configuration plugin. Please replace
|
|
-- the placeholders and assign a valid ID.
|
|
-- All IDs should be lower-case.
|
|
-- ------
|
|
|
|
-- The ID for this plugin:
|
|
ID = "00000000-0000-0000-0000-000000000000"
|
|
|
|
-- The icon for the plugin:
|
|
ICON_SVG = SVG
|
|
|
|
-- The name of the plugin:
|
|
NAME = "<Company Name> - Configuration for <Department Name>"
|
|
|
|
-- The description of the plugin:
|
|
DESCRIPTION = "This is a pre-defined configuration of <Company Name>"
|
|
|
|
-- The version of the plugin:
|
|
VERSION = "1.0.0"
|
|
|
|
-- The type of the plugin:
|
|
TYPE = "CONFIGURATION"
|
|
|
|
-- True when this plugin is deployed by an enterprise configuration server:
|
|
DEPLOYED_USING_CONFIG_SERVER = false
|
|
|
|
-- The priority of this configuration plugin. Optional, defaults to 0.
|
|
--
|
|
-- It only matters when your organization deploys more than one configuration
|
|
-- plugin. A plugin with a higher priority is applied later and therefore wins
|
|
-- whenever two of your configuration plugins manage the same setting or define
|
|
-- the same object, e.g. the same LLM provider.
|
|
--
|
|
-- A typical setup: deploy one base configuration for everybody with PRIORITY = 0
|
|
-- and one configuration per department with PRIORITY = 100. The department
|
|
-- configuration may then override the default model, while everything it does
|
|
-- not mention stays at the values of the base configuration.
|
|
--
|
|
-- Give two plugins that must override each other different priorities. With an
|
|
-- equal priority, the order is stable but arbitrary.
|
|
--
|
|
-- The priority never lifts a local configuration plugin above one of your
|
|
-- organization: configuration plugins your IT department deployed are always
|
|
-- applied first, whatever a local plugin declares.
|
|
PRIORITY = 0
|
|
|
|
-- The authors of the plugin:
|
|
AUTHORS = {"<Company Name>"}
|
|
|
|
-- The support contact for the plugin:
|
|
SUPPORT_CONTACT = "<IT Department of Company Name>"
|
|
|
|
-- The source URL for the plugin. Can be a HTTP(S) URL or an mailto link.
|
|
-- You may link to an internal documentation page, a Git repository, or
|
|
-- to a support or wiki page.
|
|
--
|
|
-- A mailto link could look like:
|
|
-- SOURCE_URL = "mailto:helpdesk@company.org?subject=Help"
|
|
SOURCE_URL = "<Any internal Git repository>"
|
|
|
|
-- The categories for the plugin:
|
|
CATEGORIES = { "CORE" }
|
|
|
|
-- The target groups for the plugin:
|
|
TARGET_GROUPS = { "EVERYONE" }
|
|
|
|
-- The flag for whether the plugin is maintained:
|
|
IS_MAINTAINED = true
|
|
|
|
-- When the plugin is deprecated, this message will be shown to users:
|
|
DEPRECATION_MESSAGE = ""
|
|
|
|
CONFIG = {}
|
|
CONFIG["LLM_PROVIDERS"] = {}
|
|
|
|
-- An example of a configuration for a self-hosted server:
|
|
-- CONFIG["LLM_PROVIDERS"][#CONFIG["LLM_PROVIDERS"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["InstanceName"] = "<user-friendly name for the combination of server and model>",
|
|
-- ["UsedLLMProvider"] = "SELF_HOSTED",
|
|
--
|
|
-- -- Allowed values for Host are: LM_STUDIO, LLAMACPP, OLLAMA, and VLLM
|
|
-- ["Host"] = "OLLAMA",
|
|
-- ["Hostname"] = "<https address of the server>",
|
|
--
|
|
-- -- Optional: Additional parameters for the API.
|
|
-- -- Please refer to the documentation of the selected host for details.
|
|
-- -- Might be something like ... \"temperature\": 0.5 ... for one parameter.
|
|
-- -- Could be something like ... \"temperature\": 0.5, \"max_tokens\": 1000 ... for multiple parameters.
|
|
-- -- Recognized reasoning parameters, such as reasoning_effort, thinking, think, and chat_template_kwargs.enable_thinking, may affect whether AI Studio shows the reasoning icon for this provider.
|
|
-- -- Please do not add the enclosing curly braces {} here. Also, no trailing comma is allowed.
|
|
-- ["AdditionalJsonApiParameters"] = "",
|
|
--
|
|
-- -- Optional: tokenizer path for this provider relative to the plugin directory.
|
|
-- -- ["TokenizerPath"] = "",
|
|
--
|
|
-- -- Optional: replace the built-in provider logo with a project-specific icon.
|
|
-- -- The path is relative to this plugin.lua and must point to an SVG file inside
|
|
-- -- this plugin directory, for example: assets/project-icon.svg. Absolute paths,
|
|
-- -- parent-directory segments (..), links leaving the plugin directory, files
|
|
-- -- larger than 32 KiB, and files which are not well-formed SVG are rejected.
|
|
-- -- An invalid or missing icon logs a warning while the provider still loads
|
|
-- -- with its built-in logo. AI Studio shows every icon in an isolated image
|
|
-- -- element, so scripts or external references inside an SVG never run; for the
|
|
-- -- same reason, the icon cannot inherit colors from the app and has to bring
|
|
-- -- its own. Provide a single icon with enough contrast on both light and dark
|
|
-- -- surfaces.
|
|
-- -- ["IconPath"] = "assets/project-icon.svg",
|
|
--
|
|
-- -- Optional: expert capability overrides.
|
|
-- -- Allowed keys are exactly:
|
|
-- -- AUDIO_INPUT, FUNCTION_CALLING, MULTIPLE_IMAGE_INPUT, SPEECH_INPUT, VIDEO_INPUT,
|
|
-- -- OPTIONAL_REASONING, ALWAYS_REASONING, REASONING_BY_DEFAULT
|
|
-- -- Allowed values are booleans only.
|
|
-- -- For default-on reasoning (rhinking), set OPTIONAL_REASONING and REASONING_BY_DEFAULT to true.
|
|
-- -- ALWAYS_REASONING means the model cannot disable reasoning (thinking).
|
|
-- -- Missing keys keep the automatic capability detection result.
|
|
-- -- ["CapabilityOverrides"] = {
|
|
-- -- ["VIDEO_INPUT"] = false,
|
|
-- -- },
|
|
--
|
|
-- -- Optional: Hugging Face inference provider. Only relevant for UsedLLMProvider = HUGGINGFACE.
|
|
-- -- Allowed values are: BASETEN, CEREBRAS, COHERE, DEEPINFRA, FEATHERLESS_AI, FIREWORKS, GROQ,
|
|
-- -- NOVITA, NSCALE, OVHCLOUD, PUBLIC_AI, SCALEWAY, TOGETHER_AI, ZAI
|
|
-- -- Instead of naming a provider, you may let Hugging Face choose one:
|
|
-- -- AUTOMATIC (the fastest), CHEAPEST, or PREFERRED (the order configured in your
|
|
-- -- Hugging Face account). An automatic choice also fails over to another provider when the
|
|
-- -- selected one is unavailable.
|
|
-- -- Note: Hugging Face stopped routing HYPERBOLIC, SAMBANOVA, and NEBIUS_AI_STUDIO in July
|
|
-- -- 2026, and HF_INFERENCE_API serves no models we can reach. Configurations still naming one
|
|
-- -- of them are treated as if no provider was set, and the user is asked to choose again.
|
|
-- -- ["HFInferenceProvider"] = "NOVITA",
|
|
--
|
|
-- -- Optional: Encrypted API key for cloud providers or secured on-premise models.
|
|
-- -- The API key must be encrypted using the enterprise encryption secret.
|
|
-- -- Format: "ENC:v1:<base64-encoded encrypted data>"
|
|
-- -- The encryption secret must be configured via:
|
|
-- -- Windows Registry: HKEY_CURRENT_USER\Software\github\MindWork AI Studio\Enterprise IT\config_encryption_secret
|
|
-- -- Environment variable: MINDWORK_AI_STUDIO_ENTERPRISE_CONFIG_ENCRYPTION_SECRET
|
|
-- -- You can export an encrypted API key from an existing provider using the export button in the settings.
|
|
-- -- ["APIKey"] = "ENC:v1:<base64-encoded encrypted data>",
|
|
--
|
|
-- -- Optional: let each user set their own API key for this otherwise locked provider,
|
|
-- -- instead of (or in addition to not) embedding one centrally. Host, model, instance
|
|
-- -- name, and every other field stay locked; only the API key becomes editable.
|
|
-- -- Mutually exclusive with "APIKey" above: when both are set, the embedded key is
|
|
-- -- ignored and a warning is logged. The user's key is preserved in the OS keyring even
|
|
-- -- if this configuration is later withdrawn.
|
|
-- -- ["AllowUserProvidedAPIKey"] = true,
|
|
--
|
|
-- ["Model"] = {
|
|
-- ["Id"] = "<the model ID>",
|
|
-- ["DisplayName"] = "<user-friendly name of the model>",
|
|
-- }
|
|
-- }
|
|
|
|
-- Transcription providers for voice-to-text functionality:
|
|
CONFIG["TRANSCRIPTION_PROVIDERS"] = {}
|
|
|
|
-- An example of a transcription provider configuration:
|
|
-- CONFIG["TRANSCRIPTION_PROVIDERS"][#CONFIG["TRANSCRIPTION_PROVIDERS"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly name for the transcription provider>",
|
|
-- ["UsedLLMProvider"] = "SELF_HOSTED",
|
|
--
|
|
-- -- Allowed values for Host are: LM_STUDIO, LLAMACPP, OLLAMA, VLLM, and WHISPER_CPP
|
|
-- ["Host"] = "WHISPER_CPP",
|
|
-- ["Hostname"] = "<https address of the server>",
|
|
--
|
|
-- -- Optional: project-specific SVG icon. The same path, size, rendering, and
|
|
-- -- fallback rules described for IconPath under LLM_PROVIDERS apply here.
|
|
-- -- ["IconPath"] = "assets/project-icon.svg",
|
|
--
|
|
-- -- Optional: Encrypted API key (see LLM_PROVIDERS example for details)
|
|
-- -- ["APIKey"] = "ENC:v1:<base64-encoded encrypted data>",
|
|
--
|
|
-- -- Optional: let each user set their own API key for this otherwise locked transcription
|
|
-- -- provider (see LLM_PROVIDERS example for details). Mutually exclusive with "APIKey"
|
|
-- -- above: when both are set, the embedded key is ignored and a warning is logged.
|
|
-- -- ["AllowUserProvidedAPIKey"] = true,
|
|
--
|
|
-- -- Optional: Hugging Face inference provider. Only relevant for UsedLLMProvider = HUGGINGFACE.
|
|
-- -- Hugging Face transcribes audio through some of its inference providers only, so the choice
|
|
-- -- is narrower than for chatting. Allowed values are: DEEPINFRA and TOGETHER_AI. The automatic
|
|
-- -- options are not available here, because a transcription request has to name its provider.
|
|
-- -- ["HFInferenceProvider"] = "TOGETHER_AI",
|
|
--
|
|
-- ["Model"] = {
|
|
-- ["Id"] = "<the model ID>",
|
|
-- ["DisplayName"] = "<user-friendly name of the model>",
|
|
-- }
|
|
-- }
|
|
|
|
-- Embedding providers for local RAG (Retrieval-Augmented Generation) functionality:
|
|
CONFIG["EMBEDDING_PROVIDERS"] = {}
|
|
|
|
-- An example of an embedding provider configuration:
|
|
-- CONFIG["EMBEDDING_PROVIDERS"][#CONFIG["EMBEDDING_PROVIDERS"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly name for the embedding provider>",
|
|
-- ["UsedLLMProvider"] = "SELF_HOSTED",
|
|
--
|
|
-- -- Allowed values for Host are: LM_STUDIO, LLAMACPP, OLLAMA, and VLLM
|
|
-- ["Host"] = "OLLAMA",
|
|
-- ["Hostname"] = "<https address of the server>",
|
|
--
|
|
-- -- Optional: project-specific SVG icon. The same path, size, rendering, and
|
|
-- -- fallback rules described for IconPath under LLM_PROVIDERS apply here.
|
|
-- -- ["IconPath"] = "assets/project-icon.svg",
|
|
--
|
|
-- -- Optional: Encrypted API key (see LLM_PROVIDERS example for details)
|
|
-- -- ["APIKey"] = "ENC:v1:<base64-encoded encrypted data>",
|
|
|
|
-- -- Optional: tokenizer path for this provider relative to the plugin directory.
|
|
-- -- ["TokenizerPath"] = "",
|
|
--
|
|
-- -- Optional: maximum number of tokens per embedding chunk. If omitted, AI Studio uses its default.
|
|
-- -- ["TokenLimit"] = 8192,
|
|
--
|
|
-- -- Optional: number of chunks sent to the embedding provider in one request. If omitted, AI Studio sends one chunk per request.
|
|
-- -- ["EmbeddingBatchSize"] = 1,
|
|
--
|
|
-- -- Optional: let each user set their own API key for this otherwise locked embedding
|
|
-- -- provider (see LLM_PROVIDERS example for details). Mutually exclusive with "APIKey"
|
|
-- -- above: when both are set, the embedded key is ignored and a warning is logged.
|
|
-- -- ["AllowUserProvidedAPIKey"] = true,
|
|
--
|
|
-- -- Optional: Hugging Face inference provider. Only relevant for UsedLLMProvider = HUGGINGFACE.
|
|
-- -- Hugging Face serves embeddings through some of its inference providers only, so the choice
|
|
-- -- is narrower than for chatting. Allowed values are: DEEPINFRA and TOGETHER_AI. The automatic
|
|
-- -- options are not available here, because an embedding request has to name its provider.
|
|
-- -- ["HFInferenceProvider"] = "TOGETHER_AI",
|
|
--
|
|
-- ["Model"] = {
|
|
-- ["Id"] = "<the model ID, e.g., nomic-embed-text>",
|
|
-- ["DisplayName"] = "<user-friendly name of the model>",
|
|
-- }
|
|
-- }
|
|
|
|
-- ERI v1 data sources for retrieval-augmented generation:
|
|
CONFIG["DATA_SOURCES"] = {}
|
|
|
|
-- Example: ERI v1 data source with a shared access token.
|
|
-- CONFIG["DATA_SOURCES"][#CONFIG["DATA_SOURCES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly data source name>",
|
|
-- ["Type"] = "ERI_V1",
|
|
-- ["Hostname"] = "<https address of the ERI server>",
|
|
-- ["Port"] = 443,
|
|
-- ["AuthMethod"] = "TOKEN",
|
|
-- ["Token"] = "ENC:v1:<base64-encoded encrypted token>",
|
|
-- ["SecurityPolicy"] = "SELF_HOSTED",
|
|
-- ["SelectedRetrievalId"] = "<retrieval process ID from the ERI server>",
|
|
-- ["MaxMatches"] = 10,
|
|
-- }
|
|
|
|
-- Example: ERI v1 data source with a shared username and password.
|
|
-- CONFIG["DATA_SOURCES"][#CONFIG["DATA_SOURCES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly data source name>",
|
|
-- ["Type"] = "ERI_V1",
|
|
-- ["Hostname"] = "<https address of the ERI server>",
|
|
-- ["Port"] = 443,
|
|
-- ["AuthMethod"] = "USERNAME_PASSWORD",
|
|
-- ["UsernamePasswordMode"] = "SHARED_USERNAME_AND_PASSWORD",
|
|
-- ["Username"] = "<shared username>",
|
|
-- ["Password"] = "ENC:v1:<base64-encoded encrypted password>",
|
|
-- ["SecurityPolicy"] = "SELF_HOSTED",
|
|
-- ["SelectedRetrievalId"] = "<retrieval process ID from the ERI server>",
|
|
-- ["MaxMatches"] = 10,
|
|
-- }
|
|
|
|
-- Example: ERI v1 data source using the user's username and a shared password.
|
|
-- CONFIG["DATA_SOURCES"][#CONFIG["DATA_SOURCES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly data source name>",
|
|
-- ["Type"] = "ERI_V1",
|
|
-- ["Hostname"] = "<https address of the ERI server>",
|
|
-- ["Port"] = 443,
|
|
-- ["AuthMethod"] = "USERNAME_PASSWORD",
|
|
-- ["UsernamePasswordMode"] = "OS_USERNAME_SHARED_PASSWORD",
|
|
-- ["Password"] = "ENC:v1:<base64-encoded encrypted password>",
|
|
-- ["SecurityPolicy"] = "SELF_HOSTED",
|
|
-- ["SelectedRetrievalId"] = "<retrieval process ID from the ERI server>",
|
|
-- ["MaxMatches"] = 10,
|
|
-- }
|
|
|
|
CONFIG["SETTINGS"] = {}
|
|
|
|
-- ------
|
|
-- How settings combine when your organization deploys more than one configuration
|
|
-- ------
|
|
--
|
|
-- A configuration with a higher PRIORITY is applied later and wins. This works per
|
|
-- setting: everything a later configuration does not mention keeps the value of the
|
|
-- configuration below it.
|
|
--
|
|
-- For a setting that holds a list or a table, the winning configuration replaces the
|
|
-- whole collection instead of merging the entries. A department configuration that
|
|
-- lists a single entry therefore drops every entry the base configuration had set for
|
|
-- that setting. That is intentional: replacing is the only way a department can take
|
|
-- something back that the base configuration has set.
|
|
--
|
|
-- The affected settings below carry a note. Two settings are the exception and add up
|
|
-- across configurations instead: DataApp.EnabledPreviewFeatures and
|
|
-- DataAssistantPluginAudit.EnterpriseApprovedPlugins.
|
|
-- ------
|
|
|
|
-- ------
|
|
-- What happens to a setting when your configuration is removed
|
|
-- ------
|
|
--
|
|
-- AI Studio remembers the value a setting had before a configuration took it over.
|
|
-- Once no configuration manages that setting anymore -- because your IT department
|
|
-- stopped deploying this configuration, because the user deleted it, or because a test
|
|
-- configuration ended -- the user gets that value back. When there is nothing to
|
|
-- restore, e.g. for a setting the user had never changed, AI Studio falls back to its
|
|
-- own default value.
|
|
--
|
|
-- One case differs: when you allow users to override a setting and somebody makes use
|
|
-- of that, their choice outlives your configuration and stays as it is.
|
|
-- ------
|
|
|
|
-- Both update settings below only ever apply to installations AI Studio is able to update.
|
|
-- Installations you rolled out yourself, for example, into C:\Program Files or into a location
|
|
-- your users cannot write to, never update themselves, no matter what you configure here. You
|
|
-- can therefore leave automatic updates enabled for everybody: your deployments ignore them,
|
|
-- while installations your colleagues fetched from GitHub keep updating themselves. Place a file
|
|
-- named "managed-installation" next to the program file to mark any other installation as one
|
|
-- you maintain. The Enterprise IT documentation describes this in detail.
|
|
|
|
-- Configure the update check interval:
|
|
-- Allowed values are: NO_CHECK, DISABLE_UPDATES, ONCE_STARTUP, HOURLY, DAILY, WEEKLY
|
|
-- NO_CHECK disables automatic checks, but users can still check and install updates manually.
|
|
-- DISABLE_UPDATES is intended for enterprise configurations and disables all update checks
|
|
-- and installations. It is not offered as a selectable option in the normal app settings.
|
|
-- CONFIG["SETTINGS"]["DataApp.UpdateInterval"] = "NO_CHECK"
|
|
|
|
-- Configure how updates are installed:
|
|
-- Allowed values are: MANUAL, AUTOMATIC
|
|
-- CONFIG["SETTINGS"]["DataApp.UpdateInstallation"] = "MANUAL"
|
|
|
|
-- Configure the page that should be opened when AI Studio starts.
|
|
-- Allowed values are: HOME, CHAT, ASSISTANTS, INFORMATION, PLUGINS, SUPPORTERS, SETTINGS
|
|
-- CONFIG["SETTINGS"]["DataApp.StartPage"] = "CHAT"
|
|
--
|
|
-- Allow users to change the configured start page locally.
|
|
-- Allowed values are: true, false
|
|
-- When set to true, the configured start page becomes the organization default,
|
|
-- but users can still choose another start page in the app settings.
|
|
-- CONFIG["SETTINGS"]["DataApp.StartPage.AllowUserOverride"] = true
|
|
|
|
-- Configure whether the quick start guide is shown on the welcome page.
|
|
-- CONFIG["SETTINGS"]["DataApp.ShowQuickStartGuide"] = false
|
|
|
|
-- Configure whether the built-in introduction is shown on the welcome page.
|
|
-- CONFIG["SETTINGS"]["DataApp.ShowIntroduction"] = false
|
|
|
|
-- Configure whether the last changelog is shown on the welcome page.
|
|
-- CONFIG["SETTINGS"]["DataApp.ShowLastChangelog"] = false
|
|
|
|
-- Configure whether the vision panel is shown on the welcome page.
|
|
-- CONFIG["SETTINGS"]["DataApp.ShowVision"] = false
|
|
|
|
-- Configure whether AI Studio shows a dialog listing suspicious instructions it
|
|
-- removed from external content, together with an explanation of the attack pattern.
|
|
-- A short notification is still shown when this setting is disabled.
|
|
-- CONFIG["SETTINGS"]["DataApp.ShowPromptInjectionAlert"] = true
|
|
|
|
-- Configure the user permission to add providers:
|
|
-- CONFIG["SETTINGS"]["DataApp.AllowUserToAddProvider"] = false
|
|
|
|
-- Configure the user permission to import plugin archives from disk.
|
|
-- When set to false, the import button on the plugins page stays visible but is disabled.
|
|
-- CONFIG["SETTINGS"]["DataApp.AllowUserToImportPlugins"] = false
|
|
|
|
-- Configure the user permission to import configuration plugin archives from disk.
|
|
-- This is a second gate on top of DataApp.AllowUserToImportPlugins: both must allow the
|
|
-- import. Configuration plugins get their own switch because they can do far more than an
|
|
-- assistant: they define LLM providers and data sources, and they lock settings. You may
|
|
-- therefore let users import assistants while keeping configurations to your IT department.
|
|
-- CONFIG["SETTINGS"]["DataApp.AllowUserToImportConfigurationPlugins"] = false
|
|
|
|
-- Configure the user permission to share or export plugins as archives.
|
|
-- When set to false, the share button on the plugins page stays visible but is disabled.
|
|
-- On Linux, this button exports the plugin archive instead of using a native share sheet.
|
|
-- CONFIG["SETTINGS"]["DataApp.AllowUserToSharePlugins"] = false
|
|
|
|
-- Configure whether administration settings are visible in the UI:
|
|
-- CONFIG["SETTINGS"]["DataApp.ShowAdminSettings"] = true
|
|
|
|
-- Configure the visibility of preview features:
|
|
-- Allowed values are: NONE, RELEASE_CANDIDATE, BETA, ALPHA, PROTOTYPE, EXPERIMENTAL
|
|
-- Please note:
|
|
-- I: that this setting does not hide features that are already enabled.
|
|
-- II: lower levels include all features of the higher levels. E.g. BETA includes RELEASE_CANDIDATE features.
|
|
-- CONFIG["SETTINGS"]["DataApp.PreviewVisibility"] = "NONE"
|
|
|
|
-- Configure the enabled preview features:
|
|
-- Allowed values are can be found in https://github.com/MindWorkAI/AI-Studio/blob/main/app/MindWork%20AI%20Studio/Settings/DataModel/PreviewFeatures.cs
|
|
-- Examples are PRE_WRITER_MODE_2024 and PRE_RAG_2024.
|
|
--
|
|
-- Adds up, does not replace: this is the one setting where all configurations
|
|
-- contribute together. Enable one preview feature for the whole organization and
|
|
-- another one for a single department, and users of that department get both. Each
|
|
-- configuration keeps its own contribution, so removing one of them only withdraws
|
|
-- the features that this configuration had enabled.
|
|
-- CONFIG["SETTINGS"]["DataApp.EnabledPreviewFeatures"] = { "PRE_RAG_2024" }
|
|
|
|
-- Configure the preselected provider.
|
|
-- It must be one of the provider IDs defined in CONFIG["LLM_PROVIDERS"].
|
|
-- Please note: using an empty string ("") will lock the preselected provider selection, even though no valid preselected provider is found.
|
|
-- CONFIG["SETTINGS"]["DataApp.PreselectedProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
|
|
-- Configure the preselected profile.
|
|
-- It must be one of the profile IDs defined in CONFIG["PROFILES"].
|
|
-- Please note: using an empty string ("") will lock the preselected profile selection, even though no valid preselected profile is found.
|
|
-- CONFIG["SETTINGS"]["DataApp.PreselectedProfile"] = "00000000-0000-0000-0000-000000000000"
|
|
|
|
-- Configure chat-specific preselected options.
|
|
-- This must be enabled for the chat-specific provider, profile, and chat template to take effect.
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectOptions"] = true
|
|
--
|
|
-- Configure the preselected provider for chats.
|
|
-- It must be one of the provider IDs defined in CONFIG["LLM_PROVIDERS"].
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
-- Configure the preselected profile for chats.
|
|
-- It must be one of the profile IDs defined in CONFIG["PROFILES"].
|
|
-- Please note: using an empty string ("") means chats will use the app default profile.
|
|
-- Please note: using "00000000-0000-0000-0000-000000000000" means chats will use no profile.
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedProfile"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
-- Configure the preselected chat template for chats.
|
|
-- It must be one of the chat template IDs defined in CONFIG["CHAT_TEMPLATES"].
|
|
-- Please note: using an empty string ("") or "00000000-0000-0000-0000-000000000000" means chats will use no chat template.
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedChatTemplate"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
--
|
|
-- Configure default data source options for new chats.
|
|
--
|
|
-- Controls whether data sources are off by default:
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourcesDisabled"] = false
|
|
|
|
-- Controls whether AI Studio asks an agent to choose data sources:
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourcesAutomaticSelection"] = true
|
|
|
|
-- Controls whether retrieved data is validated by an agent:
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourcesAutomaticValidation"] = true
|
|
|
|
-- Must contain IDs from CONFIG["DATA_SOURCES"] or user-configured data sources.
|
|
-- IDs from another configuration of your organization work as well: they are resolved
|
|
-- against every known data source, not only against the ones defined here. IDs that
|
|
-- resolve to nothing are ignored.
|
|
--
|
|
-- Replaces, does not merge: a configuration with a higher priority replaces this list
|
|
-- completely. To keep an entry of the base configuration, list that ID here again.
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourceIds"] = {
|
|
-- "00000000-0000-0000-0000-000000000000",
|
|
-- }
|
|
--
|
|
-- Configure whether default chat data source options are applied when assistant results are sent to chat.
|
|
-- Allowed values are: NO_DATA_SOURCES, APPLY_STANDARD_CHAT_DATA_SOURCE_OPTIONS
|
|
-- CONFIG["SETTINGS"]["DataChat.SendToChatDataSourceBehavior"] = "APPLY_STANDARD_CHAT_DATA_SOURCE_OPTIONS"
|
|
--
|
|
-- Allow users to change any configured chat default locally.
|
|
-- Allowed values are: true, false
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectOptions.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedProvider.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedProfile.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedChatTemplate.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourcesDisabled.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourcesAutomaticSelection.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourcesAutomaticValidation.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.PreselectedDataSourceIds.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataChat.SendToChatDataSourceBehavior.AllowUserOverride"] = true
|
|
|
|
-- Configure defaults for the Batch Processing Assistant.
|
|
-- Preselection must be enabled for the remaining batch settings to take effect.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PreselectOptions"] = true
|
|
--
|
|
-- Configure the default input and output folders.
|
|
-- Leave the input folder empty to require a selection for every new batch run.
|
|
-- Leave the output folder empty to use the ai-results subfolder of the input folder.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.InputDirectory"] = ""
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.OutputDirectory"] = ""
|
|
--
|
|
-- Configure the default file patterns and whether subfolders are included.
|
|
-- Separate multiple patterns with semicolons.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.FilePatterns"] = "*.pdf;*.docx;*.pptx;*.xlsx;*.md;*.txt;*.mp3;*.wav;*.wave;*.aac;*.flac;*.ogg;*.opus;*.m4a;*.m4b;*.wma;*.alac;*.aif;*.aiff;*.caf;*.mp4;*.m4v;*.avi;*.mkv;*.mov;*.wmv;*.flv;*.webm"
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.IncludeSubdirectories"] = false
|
|
--
|
|
-- Configure the default instruction source.
|
|
-- Allowed values are: FREE_PROMPT, FILE_IMPORT, POLICY
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PromptSource"] = "FREE_PROMPT"
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.FreePrompt"] = "Summarize each document."
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PromptFilePath"] = ""
|
|
--
|
|
-- The policy ID must reference an entry in CONFIG["DOCUMENT_ANALYSIS_POLICIES"] or a
|
|
-- user-configured policy. It is used only when PromptSource is POLICY.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PreselectedPolicyId"] = ""
|
|
--
|
|
-- Configure the default output mode.
|
|
-- Allowed values are: INDIVIDUAL_FILES, TABLE_ONLY
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.OutputMode"] = "INDIVIDUAL_FILES"
|
|
--
|
|
-- Configure the file format of the individual result files. Used only when the output
|
|
-- mode is INDIVIDUAL_FILES. Everything except MARKDOWN is converted by Pandoc, which
|
|
-- AI Studio installs on demand.
|
|
-- Allowed values are: MICROSOFT_WORD, OPEN_DOCUMENT_TEXT, LATEX, MARKDOWN, HTML
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.ResultFileFormat"] = "MARKDOWN"
|
|
--
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.CsvFileName"] = "batch-results.csv"
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.ResultColumnHeader"] = "Result"
|
|
-- Allowed CSV separator values are: COMMA, SEMICOLON, PIPE, TAB, CUSTOM
|
|
-- A custom separator must be exactly one punctuation or symbol character.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.CsvSeparator"] = "SEMICOLON"
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.CustomCsvSeparator"] = "^"
|
|
--
|
|
-- Enforce the lower end of the random pause between files for the organization.
|
|
-- The value must be between 6 and 300 seconds. Users can configure only the upper
|
|
-- end of the interval while this setting is managed by a configuration plugin.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.MinimumDelaySeconds"] = 12
|
|
--
|
|
-- Configure the minimum provider confidence and the default provider.
|
|
-- Allowed confidence values are: NONE, UNTRUSTED, UNKNOWN, VERY_LOW, LOW, MODERATE, MEDIUM, HIGH
|
|
-- A policy can require a higher minimum confidence; the stricter level wins.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.MinimumProviderConfidence"] = "NONE"
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PreselectedProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
-- Allow users to change individual managed batch defaults locally.
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PreselectOptions.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.InputDirectory.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.OutputDirectory.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.FilePatterns.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.IncludeSubdirectories.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PromptSource.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.FreePrompt.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PromptFilePath.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PreselectedPolicyId.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.OutputMode.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.ResultFileFormat.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.CsvFileName.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.ResultColumnHeader.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.CsvSeparator.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.CustomCsvSeparator.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.MinimumProviderConfidence.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataBatchProcessing.PreselectedProvider.AllowUserOverride"] = true
|
|
|
|
-- Configure the transcription provider for voice-to-text functionality.
|
|
-- It must be one of the transcription provider IDs defined in CONFIG["TRANSCRIPTION_PROVIDERS"].
|
|
-- Without a selected transcription provider, dictation and transcription features will be disabled.
|
|
-- Please note: using an empty string ("") will lock the selection and disable dictation/transcription.
|
|
-- CONFIG["SETTINGS"]["DataApp.UseTranscriptionProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
|
|
-- Configure which assistants should be hidden from the UI.
|
|
-- Allowed values are:
|
|
-- GRAMMAR_SPELLING_ASSISTANT, ICON_FINDER_ASSISTANT, REWRITE_ASSISTANT,
|
|
-- PROMPT_OPTIMIZER_ASSISTANT, TRANSLATION_ASSISTANT, AGENDA_ASSISTANT,
|
|
-- CODING_ASSISTANT, TEXT_SUMMARIZER_ASSISTANT, EMAIL_ASSISTANT,
|
|
-- LEGAL_CHECK_ASSISTANT, SYNONYMS_ASSISTANT, MY_TASKS_ASSISTANT,
|
|
-- JOB_POSTING_ASSISTANT, BIAS_DAY_ASSISTANT, ERI_ASSISTANT,
|
|
-- DOCUMENT_ANALYSIS_ASSISTANT, BATCH_PROCESSING_ASSISTANT, SLIDE_BUILDER_ASSISTANT,
|
|
-- VISUAL_BRIEFING_ASSISTANT, I18N_ASSISTANT,
|
|
-- LOG_VIEWER_ASSISTANT
|
|
--
|
|
-- Replaces, does not merge: a configuration with a higher priority replaces this list
|
|
-- completely. This is what lets a department show an assistant again that the base
|
|
-- configuration hides. The department configuration must then list every other
|
|
-- assistant that is supposed to stay hidden, otherwise those become visible too.
|
|
-- CONFIG["SETTINGS"]["DataApp.HiddenAssistants"] = { "ERI_ASSISTANT", "I18N_ASSISTANT" }
|
|
|
|
-- Configure organization defaults for the Visual Briefing Assistant.
|
|
-- The assistant turns documents, images, audio, and video into a self-contained interactive
|
|
-- briefing. All settings below are defaults for new briefings; users can change them per briefing.
|
|
--
|
|
-- Configure the preselected provider for briefing builds.
|
|
-- It must be one of the provider IDs defined in CONFIG["LLM_PROVIDERS"].
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
-- Configure the preselected profile for briefing builds.
|
|
-- It must be one of the profile IDs defined in CONFIG["PROFILES"].
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedProfile"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
-- Configure the language the briefing content is written in.
|
|
-- Allowed values are: AS_IS, EN_US, EN_GB, ZH_CN, HI_IN, ES_ES, FR_FR, DE_DE, DE_CH, DE_AT,
|
|
-- JA_JP, RU_RU, OTHER
|
|
-- AS_IS keeps the language of the source material.
|
|
-- Please note: AI Studio's own texts inside an exported briefing, such as the footer and the
|
|
-- reset button, are always US English regardless of this setting.
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedTargetLanguage"] = "EN_US"
|
|
--
|
|
-- Configure a free-form language, used only when PreselectedTargetLanguage is "OTHER".
|
|
-- Any language name is allowed, for example "Swiss German" or "Brazilian Portuguese".
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedOtherLanguage"] = ""
|
|
--
|
|
-- Configure the audience the briefing is written for. These four settings steer wording,
|
|
-- level of detail, and which evidence is emphasized.
|
|
--
|
|
-- Allowed values are: UNSPECIFIED, STUDENTS, SCIENTISTS, LAWYERS, INVESTORS, ENGINEERS,
|
|
-- SOFTWARE_DEVELOPERS, JOURNALISTS, HEALTHCARE_PROFESSIONALS, PUBLIC_OFFICIALS,
|
|
-- BUSINESS_PROFESSIONALS
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedAudienceProfile"] = "UNSPECIFIED"
|
|
--
|
|
-- Allowed values are: UNSPECIFIED, CHILDREN, TEENAGERS, ADULTS
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedAudienceAgeGroup"] = "UNSPECIFIED"
|
|
--
|
|
-- Allowed values are: UNSPECIFIED, TRAINEES, INDIVIDUAL_CONTRIBUTORS, TEAM_LEADS, MANAGERS,
|
|
-- EXECUTIVES, BOARD_MEMBERS
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedAudienceOrganizationalLevel"] = "UNSPECIFIED"
|
|
--
|
|
-- Allowed values are: UNSPECIFIED, NON_EXPERTS, BASIC, INTERMEDIATE, EXPERTS
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.PreselectedAudienceExpertise"] = "UNSPECIFIED"
|
|
--
|
|
-- Configure whether each briefing component lists the source files it was derived from.
|
|
-- Allowed values are: true, false
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.ShowSourceReferences"] = true
|
|
--
|
|
-- Configure whether images are downscaled and re-encoded before they are embedded.
|
|
-- Allowed values are: true, false
|
|
-- Images are always embedded in the exported file. With true, images larger than 2560 pixels on
|
|
-- their longest edge are scaled down, which keeps exported briefings substantially smaller.
|
|
-- With false, the original image bytes are embedded unchanged.
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.OptimizeImages"] = true
|
|
--
|
|
-- Configure the minimum provider confidence required to build a briefing.
|
|
-- Allowed values are: NONE, VERY_LOW, LOW, MODERATE, MEDIUM, HIGH
|
|
-- Source material is sent to the selected provider, so this acts as a guard for confidential
|
|
-- documents. Providers below this level cannot be selected in the assistant.
|
|
-- CONFIG["SETTINGS"]["DataVisualBriefing.MinimumProviderConfidence"] = "NONE"
|
|
|
|
-- Configure enterprise approvals for assistant plugins.
|
|
-- Each approval is matched only by the current SHA-256 hash over all Lua files
|
|
-- in the assistant plugin folder, in canonical sorted order.
|
|
-- When the hash matches, the assistant plugin is treated as SAFE immediately and
|
|
-- no user-run security audit is required.
|
|
-- You can generate the exact hash with the build-script command:
|
|
-- dotnet run --project app/Build -- assistant-plugin-hash "<plugin-dir>" --lua-snippet
|
|
--
|
|
-- Only works in configurations your configuration server deploys. An approval marks an
|
|
-- assistant plugin as safe without any audit, and AI Studio then tells users that their
|
|
-- organization approved it. A configuration plugin that a user placed locally therefore
|
|
-- cannot approve anything: AI Studio ignores its approvals and writes a warning to the
|
|
-- log. This is decided by where the plugin is stored, not by DEPLOYED_USING_CONFIG_SERVER.
|
|
--
|
|
-- Adds up, does not replace: approvals of all your configurations are combined, so a
|
|
-- department configuration can approve additional assistant plugins without repeating
|
|
-- the approvals of the base configuration. Each configuration keeps its own approvals,
|
|
-- so removing one of them only withdraws the approvals it had granted.
|
|
--
|
|
-- An approval only says that a plugin is safe. Whether it is enabled is a second
|
|
-- decision, and without the optional Activate field it stays with your colleagues: the
|
|
-- assistant is approved, and everybody switches it on themselves. Set Activate to have
|
|
-- AI Studio enable it instead. AllowUserOverride works as it does for every setting:
|
|
-- without it, your colleagues cannot switch the assistant off; with it, you only provide
|
|
-- a default, which AI Studio applies once and then leaves alone.
|
|
--
|
|
-- Activate AllowUserOverride Result
|
|
-- ------------------------------------------------------------------------
|
|
-- absent any approved, everybody enables it themselves
|
|
-- true true enabled for everybody, may be switched off
|
|
-- true absent enabled for everybody, cannot be switched off
|
|
--
|
|
-- Activating needs more than the approval: AI Studio only enables an assistant plugin
|
|
-- your organization actually rolled out, i.e. one below .config or .config-tests, or one
|
|
-- marked with DEPLOYED_USING_CONFIG_SERVER. An approval alone is matched by hash and would
|
|
-- otherwise also cover a copy a user placed themselves, which you can neither update nor
|
|
-- withdraw. Such a copy stays approved, but nobody's settings are changed for it.
|
|
--
|
|
-- When two of your configurations approve the same hash, any Activate wins, while the
|
|
-- freedom to switch the assistant off survives only if every configuration asking for the
|
|
-- activation grants it.
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.EnterpriseApprovedPlugins"] = {
|
|
-- {
|
|
-- ["PluginHash"] = "0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF",
|
|
-- ["DisplayName"] = "Name of Plugin",
|
|
-- ["Comment"] = "Optional comment",
|
|
-- ["ApprovedBy"] = "Optional Approver",
|
|
-- ["ApprovedAtUtc"] = "2026-07-02T09:30:00Z",
|
|
-- ["Activate"] = true,
|
|
-- ["AllowUserOverride"] = true,
|
|
-- }
|
|
-- }
|
|
|
|
-- Configure a global shortcut for starting and stopping dictation.
|
|
--
|
|
-- The format follows the Rust and Tauri conventions. Especially,
|
|
-- when you want to use the CTRL key on Windows (or the CMD key on macOS),
|
|
-- please use "CmdOrControl" as the key name. All parts of the shortcut
|
|
-- must be separated by a plus sign (+).
|
|
--
|
|
-- Examples are: "CmdOrControl+Shift+D", "Alt+F9", "F8"
|
|
-- CONFIG["SETTINGS"]["DataApp.ShortcutVoiceRecording"] = "CmdOrControl+1"
|
|
|
|
-- Configure whether tools are available at all. The default is true.
|
|
-- When tools are disabled globally, tool selection is hidden in chats and assistants,
|
|
-- but the global tool settings remain available to administrators.
|
|
-- CONFIG["SETTINGS"]["DataTools.EnableTools"] = false
|
|
|
|
-- Disable individual tools by their stable tool ID. The default is an empty set.
|
|
-- Unknown IDs are safely ignored and can be deployed before a future tool is installed.
|
|
-- CONFIG["SETTINGS"]["DataTools.DisabledToolIds"] = { "web_search" }
|
|
|
|
-- Configure the minimum provider confidence level required for individual tools.
|
|
-- Tool IDs include: web_search, read_web_page
|
|
-- Allowed values are: NONE, UNTRUSTED, VERY_LOW, LOW, MODERATE, MEDIUM, HIGH
|
|
-- Defaults: web_search = VERY_LOW, read_web_page = VERY_LOW
|
|
-- CONFIG["SETTINGS"]["DataTools.MinimumProviderConfidenceByToolId"] = {
|
|
-- ["web_search"] = "VERY_LOW",
|
|
-- ["read_web_page"] = "VERY_LOW"
|
|
-- }
|
|
|
|
-- Configure the settings of individual tools. Keys are "<tool ID>.<field name>", values are
|
|
-- always strings. This works for every tool, including tools added by plugins, because nothing
|
|
-- here needs to be known to AI Studio in advance.
|
|
--
|
|
-- Two tables decide how firmly a value applies:
|
|
-- LockedToolSettings - the user cannot change it, and it is reapplied on every update.
|
|
-- DefaultToolSettings - pre-fills the setting; a value the user saves afterwards wins.
|
|
--
|
|
-- A tool field marked as secret, such as an API key, can be rolled out as well — but only
|
|
-- encrypted with the enterprise encryption secret, in the same "ENC:v1:<base64>" form the
|
|
-- providers above use, and only through LockedToolSettings. A locked secret leaves whatever
|
|
-- the user entered untouched, so their own key returns when you stop deploying yours. A
|
|
-- plaintext secret is refused with a warning in the log rather than used.
|
|
--
|
|
-- Field names of the Web Search tool. At least one of its search services has to be configured
|
|
-- before the tool can be used; which one you pick is up to you, since all three can be rolled
|
|
-- out from here:
|
|
-- searxng.baseUrl SearXNG HTTP(S) root URL or /search endpoint. The instance
|
|
-- must have the JSON format enabled, i.e. "json" listed under
|
|
-- search.formats in its settings.yml. Public instances usually
|
|
-- serve only the web interface and block automated requests,
|
|
-- so use an instance your organization operates.
|
|
-- staan.apiKey Secret. Staan API key, encrypted as described above and set
|
|
-- through LockedToolSettings, or entered by the user in the
|
|
-- tool's settings dialog.
|
|
-- staan.market Which market Staan searches when the AI model asks for a
|
|
-- language Staan does not offer, or for none in particular.
|
|
-- Staan searches one market at a time and cannot search
|
|
-- without one. Allowed values are: de-de, en-us, fr-fr.
|
|
-- tavily.apiKey Secret. Tavily API key, encrypted as described above and set
|
|
-- through LockedToolSettings, or entered by the user in the
|
|
-- tool's settings dialog.
|
|
-- tavily.searchDepth How thoroughly Tavily searches. A basic search costs one
|
|
-- request of the account's monthly quota, an advanced search
|
|
-- costs two. Allowed values are: basic, advanced.
|
|
-- backendStrategy What to do when more than one search service is configured.
|
|
-- FAILOVER asks them one after another until one returns hits.
|
|
-- PARALLEL asks all of them at once and combines their
|
|
-- results, which uses one request of every service per search.
|
|
-- SPECIFIC asks only the preferred service. The default is
|
|
-- FAILOVER. Allowed values are: FAILOVER, PARALLEL, SPECIFIC.
|
|
-- primaryBackend Which search service to ask first, and the only one asked
|
|
-- with the SPECIFIC strategy. Left empty, the services are
|
|
-- asked in a fixed order. Allowed values are: SEARXNG, STAAN,
|
|
-- TAVILY.
|
|
-- defaultLanguage Required. IETF language tag such as "de-DE", or "all" for no
|
|
-- restriction. Without a language many search engines return
|
|
-- no results at all, so the tool counts as unconfigured while
|
|
-- this is empty.
|
|
-- defaultSafeSearch How strictly the search services filter explicit results. A
|
|
-- service that cannot filter at all is not asked while this is
|
|
-- set to MODERATE or STRICT, which currently applies to Staan.
|
|
-- Allowed values are: OFF, MODERATE, STRICT.
|
|
-- maxResults Result count, as an integer string.
|
|
-- searchTimeoutSeconds Search request timeout in seconds.
|
|
-- pageTimeoutSeconds Per-page timeout in seconds.
|
|
-- allPagesRetrievalTimeoutSeconds Overall page-retrieval timeout in seconds.
|
|
-- maxTotalContentCharacters Total content-character budget.
|
|
-- minContentCharactersPerResult Per-result content allocation.
|
|
--
|
|
-- Field names of the Read Web Page tool:
|
|
-- timeoutSeconds Page-loading timeout in seconds.
|
|
-- maxContentCharacters Content-character limit.
|
|
-- allowedPrivateHosts Comma-separated private or VPN host patterns. Public pages need not be
|
|
-- listed. Wildcards match subdomains only, so add the root domain
|
|
-- separately. Allowed private hosts require a provider with HIGH
|
|
-- confidence or one trusted by the organization. AI Studio only tries the
|
|
-- current user's operating-system sign-in for explicitly allowed HTTPS
|
|
-- targets when those provider requirements are met, and it never reuses
|
|
-- browser cookies.
|
|
--
|
|
-- CONFIG["SETTINGS"]["DataTools.LockedToolSettings"] = {
|
|
-- ["web_search.searxng.baseUrl"] = "https://searxng.example.org/",
|
|
-- ["web_search.defaultLanguage"] = "de-DE",
|
|
-- ["web_search.backendStrategy"] = "FAILOVER",
|
|
-- ["web_search.tavily.apiKey"] = "ENC:v1:<base64-encoded encrypted data>",
|
|
-- ["read_web_page.allowedPrivateHosts"] = "example.org, *.example.org"
|
|
-- }
|
|
--
|
|
-- CONFIG["SETTINGS"]["DataTools.DefaultToolSettings"] = {
|
|
-- ["web_search.maxResults"] = "5",
|
|
-- ["web_search.defaultSafeSearch"] = "MODERATE",
|
|
-- ["web_search.tavily.searchDepth"] = "basic",
|
|
-- ["read_web_page.timeoutSeconds"] = "30"
|
|
-- }
|
|
|
|
-- Configure the HTTP timeout for external requests, in seconds.
|
|
-- The default is 3600 (1 hour).
|
|
-- CONFIG["SETTINGS"]["DataApp.HttpClientTimeoutSeconds"] = 3600
|
|
|
|
-- Configure additional root certificates for external HTTPS requests.
|
|
--
|
|
-- This is intended for managed Linux/Flatpak deployments where organization-internal
|
|
-- HTTPS certificates chain to a private root CA that is not visible inside the sandbox.
|
|
-- The file must be a PEM bundle with one or more root CA certificates and must be
|
|
-- readable by AI Studio.
|
|
--
|
|
-- IMPORTANT: A configuration plugin cannot fix the very first download of that same
|
|
-- configuration plugin. For bootstrapping enterprise configuration downloads, deploy
|
|
-- the equivalent environment variables before AI Studio starts:
|
|
--
|
|
-- MINDWORK_AI_STUDIO_EXTERNAL_HTTP_CUSTOM_ROOT_CERTIFICATES_ENABLED=true
|
|
-- MINDWORK_AI_STUDIO_EXTERNAL_HTTP_CUSTOM_ROOT_CERTIFICATE_BUNDLE_PATH=/path/in/sandbox/company-root-cas.pem
|
|
-- MINDWORK_AI_STUDIO_EXTERNAL_HTTP_CUSTOM_ROOT_CERTIFICATE_ALLOWED_HOSTS=*.intra.example.org;data.example.org
|
|
--
|
|
-- Replaces, does not merge: a configuration with a higher priority replaces the host
|
|
-- list completely. Deploy this setting in one configuration only, or repeat every host
|
|
-- of the base configuration. Otherwise, hosts of the base configuration silently stop
|
|
-- trusting your root certificates.
|
|
--
|
|
-- CONFIG["SETTINGS"]["DataApp.ExternalHttpCustomRootCertificatesEnabled"] = true
|
|
-- CONFIG["SETTINGS"]["DataApp.ExternalHttpCustomRootCertificateBundlePath"] = "/path/in/sandbox/company-root-cas.pem"
|
|
-- CONFIG["SETTINGS"]["DataApp.ExternalHttpCustomRootCertificateAllowedHosts"] = { "*.intra.example.org", "eri.example.org" }
|
|
|
|
-- Configure provider confidence settings.
|
|
-- These settings apply to LLM providers, embedding providers, and transcription providers.
|
|
--
|
|
-- Configure a predefined confidence scheme.
|
|
-- Allowed values are: TRUST_ALL, TRUST_USA_EUROPE, TRUST_USA, TRUST_EUROPE, TRUST_ASIA, LOCAL_TRUST_ONLY, CUSTOM
|
|
-- CONFIG["SETTINGS"]["DataConfidence.ConfidenceScheme"] = "TRUST_EUROPE"
|
|
--
|
|
-- Configure whether users can still change the confidence scheme locally.
|
|
-- Allowed values are: true, false
|
|
-- When set to true, the configured confidence scheme becomes the organization default,
|
|
-- but users can still choose another scheme in the app settings.
|
|
-- CONFIG["SETTINGS"]["DataConfidence.ConfidenceScheme.AllowUserOverride"] = true
|
|
--
|
|
-- Configure whether confidence levels are shown in the UI.
|
|
-- CONFIG["SETTINGS"]["DataConfidence.ShowProviderConfidence"] = true
|
|
--
|
|
-- Configure an app-wide minimum confidence level.
|
|
-- Allowed values are: NONE, VERY_LOW, LOW, MODERATE, MEDIUM, HIGH
|
|
-- CONFIG["SETTINGS"]["DataConfidence.EnforceGlobalMinimumConfidence"] = true
|
|
-- CONFIG["SETTINGS"]["DataConfidence.GlobalMinimumConfidence"] = "MEDIUM"
|
|
--
|
|
-- Configure whether users can change the app-wide minimum confidence level locally.
|
|
-- CONFIG["SETTINGS"]["DataConfidence.EnforceGlobalMinimumConfidence.AllowUserOverride"] = false
|
|
-- CONFIG["SETTINGS"]["DataConfidence.GlobalMinimumConfidence.AllowUserOverride"] = false
|
|
--
|
|
-- Configure a custom confidence scheme.
|
|
-- This is used when DataConfidence.ConfidenceScheme is set to CUSTOM.
|
|
-- Allowed provider keys are: OPEN_AI, ANTHROPIC, MISTRAL, GOOGLE, X, DEEP_SEEK, ALIBABA_CLOUD,
|
|
-- PERPLEXITY, OPEN_ROUTER, HETZNER, IONOS, LITE_LLM, FIREWORKS, GROQ, HUGGINGFACE, SELF_HOSTED,
|
|
-- HELMHOLTZ, GWDG
|
|
-- Allowed confidence values are: UNTRUSTED, VERY_LOW, LOW, MODERATE, MEDIUM, HIGH
|
|
--
|
|
-- Replaces, does not merge: a configuration with a higher priority replaces the whole
|
|
-- table. Every configuration that sets this must therefore list all providers it wants
|
|
-- to cover. A partial table is not completed from the configuration below it, and the
|
|
-- providers left out fall back to the app default.
|
|
-- CONFIG["SETTINGS"]["DataConfidence.CustomConfidenceScheme"] = {
|
|
-- ["OPEN_AI"] = "MODERATE",
|
|
-- ["ANTHROPIC"] = "MODERATE",
|
|
-- ["MISTRAL"] = "HIGH",
|
|
-- ["GOOGLE"] = "LOW",
|
|
-- ["X"] = "LOW",
|
|
-- ["DEEP_SEEK"] = "LOW",
|
|
-- ["ALIBABA_CLOUD"] = "LOW",
|
|
-- ["PERPLEXITY"] = "MODERATE",
|
|
-- ["OPEN_ROUTER"] = "MODERATE",
|
|
-- ["HETZNER"] = "HIGH",
|
|
-- ["IONOS"] = "HIGH",
|
|
-- ["LITE_LLM"] = "MODERATE",
|
|
-- ["FIREWORKS"] = "MODERATE",
|
|
-- ["GROQ"] = "MODERATE",
|
|
-- ["HUGGINGFACE"] = "MODERATE",
|
|
-- ["SELF_HOSTED"] = "HIGH",
|
|
-- ["HELMHOLTZ"] = "HIGH",
|
|
-- ["GWDG"] = "HIGH",
|
|
-- }
|
|
--
|
|
-- Configure whether users can change the custom confidence scheme locally.
|
|
-- CONFIG["SETTINGS"]["DataConfidence.CustomConfidenceScheme.AllowUserOverride"] = false
|
|
--
|
|
-- Configure provider instances trusted by your organization for data-source security checks.
|
|
-- These IDs may refer to LLM providers, embedding providers, or transcription providers
|
|
-- defined in this configuration. Trusted providers are treated like self-hosted providers
|
|
-- only for data-source security checks and related local data warnings. Trusted LLM providers
|
|
-- can also use read_web_page for explicitly allowed private or VPN hosts.
|
|
--
|
|
-- Replaces, does not merge: a configuration with a higher priority replaces this list
|
|
-- completely, so providers trusted by the base configuration lose that status. Repeat
|
|
-- them here to keep them trusted.
|
|
-- CONFIG["SETTINGS"]["DataSourceSecuritySettings.TrustedProviderIds"] = {
|
|
-- "00000000-0000-0000-0000-000000000000",
|
|
-- "00000000-0000-0000-0000-000000000001",
|
|
-- }
|
|
|
|
-- Configure the data source selection agent.
|
|
-- This agent is used when chat data source options enable AI-based data source selection.
|
|
-- The provider must be one of the provider IDs defined in CONFIG["LLM_PROVIDERS"].
|
|
-- CONFIG["SETTINGS"]["DataAgentDataSourceSelection.PreselectAgentOptions"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentDataSourceSelection.PreselectedAgentProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
-- CONFIG["SETTINGS"]["DataAgentDataSourceSelection.PreselectAgentOptions.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentDataSourceSelection.PreselectedAgentProvider.AllowUserOverride"] = true
|
|
|
|
-- Configure the retrieval context validation agent.
|
|
-- This agent is used when retrieval context validation is enabled globally and chat data source options enable AI-based validation.
|
|
-- The provider must be one of the provider IDs defined in CONFIG["LLM_PROVIDERS"].
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.EnableRetrievalContextValidation"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.PreselectAgentOptions"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.PreselectedAgentProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.NumParallelValidations"] = 3
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.EnableRetrievalContextValidation.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.PreselectAgentOptions.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.PreselectedAgentProvider.AllowUserOverride"] = true
|
|
-- CONFIG["SETTINGS"]["DataAgentRetrievalContextValidation.NumParallelValidations.AllowUserOverride"] = true
|
|
|
|
-- Configure assistant plugin security audits.
|
|
--
|
|
-- Configure whether assistant plugins must be audited before users can activate them.
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.RequireAuditBeforeActivation"] = true
|
|
--
|
|
-- Configure a dedicated provider for assistant plugin audits.
|
|
-- It must be one of the provider IDs defined in CONFIG["LLM_PROVIDERS"].
|
|
-- Without a selected audit provider, AI Studio uses the app-wide default provider.
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.PreselectedAgentProvider"] = "00000000-0000-0000-0000-000000000000"
|
|
--
|
|
-- Configure the minimum audit level assistant plugins must meet.
|
|
-- Allowed values are: UNKNOWN, DANGEROUS, CAUTION, SAFE
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.MinimumLevel"] = "CAUTION"
|
|
--
|
|
-- Configure whether activation is blocked when the audit result is below the minimum level.
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.BlockActivationBelowMinimum"] = true
|
|
--
|
|
-- Configure whether new or changed assistant plugins are audited automatically in the background.
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.AutomaticallyAuditAssistants"] = false
|
|
--
|
|
-- Configure whether users can change assistant plugin audit settings locally.
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.RequireAuditBeforeActivation.AllowUserOverride"] = false
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.PreselectedAgentProvider.AllowUserOverride"] = false
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.MinimumLevel.AllowUserOverride"] = false
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.BlockActivationBelowMinimum.AllowUserOverride"] = false
|
|
-- CONFIG["SETTINGS"]["DataAssistantPluginAudit.AutomaticallyAuditAssistants.AllowUserOverride"] = false
|
|
|
|
-- Example chat templates for this configuration:
|
|
CONFIG["CHAT_TEMPLATES"] = {}
|
|
|
|
-- A simple example chat template:
|
|
-- CONFIG["CHAT_TEMPLATES"][#CONFIG["CHAT_TEMPLATES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly name of the chat template>",
|
|
-- ["SystemPrompt"] = "You are <Company Name>'s helpful AI assistant for <Department Name>. Your task is ...",
|
|
-- ["PredefinedUserPrompt"] = "Please help me with ...",
|
|
-- ["AllowProfileUsage"] = true,
|
|
-- ["ExampleConversation"] = {
|
|
-- {
|
|
-- -- Allowed values are: USER, AI, SYSTEM
|
|
-- ["Role"] = "USER",
|
|
-- ["Content"] = "Hello! Can you help me with a quick task?"
|
|
-- },
|
|
-- {
|
|
-- -- Allowed values are: USER, AI, SYSTEM
|
|
-- ["Role"] = "AI",
|
|
-- ["Content"] = "Of course. What do you need?"
|
|
-- }
|
|
-- }
|
|
-- }
|
|
|
|
-- An example chat template with file attachments:
|
|
-- This template automatically attaches specified files when the user selects it.
|
|
-- CONFIG["CHAT_TEMPLATES"][#CONFIG["CHAT_TEMPLATES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000001",
|
|
-- ["Name"] = "Document Analysis Template",
|
|
-- ["SystemPrompt"] = "You are an expert document analyst. Please analyze the attached documents and provide insights.",
|
|
-- ["PredefinedUserPrompt"] = "Please analyze the attached company guidelines and summarize the key points.",
|
|
-- ["AllowProfileUsage"] = true,
|
|
-- -- Optional: Pre-attach files that will be automatically included when using this template.
|
|
-- -- These files will be loaded when the user selects this chat template.
|
|
-- -- Note: File paths can be absolute paths that are accessible to all users, or relative paths
|
|
-- -- inside this plugin folder, for example "attachments/00000000-0000-0000-0000-000000000001/Guidelines.pdf".
|
|
-- ["FileAttachments"] = {
|
|
-- "G:\\Company\\Documents\\Guidelines.pdf",
|
|
-- "G:\\Company\\Documents\\CompanyPolicies.docx"
|
|
-- },
|
|
-- ["ExampleConversation"] = {
|
|
-- {
|
|
-- ["Role"] = "USER",
|
|
-- ["Content"] = "I have attached the company documents for analysis."
|
|
-- },
|
|
-- {
|
|
-- ["Role"] = "AI",
|
|
-- ["Content"] = "Thank you. I'll analyze the documents and provide a comprehensive summary."
|
|
-- }
|
|
-- }
|
|
-- }
|
|
|
|
-- Introduction texts shown as expansion panels on the welcome page:
|
|
CONFIG["INTRODUCTIONS"] = {}
|
|
|
|
-- An example introduction:
|
|
-- CONFIG["INTRODUCTIONS"][#CONFIG["INTRODUCTIONS"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Title"] = "Welcome to Your Organization's AI Studio",
|
|
-- ["Version"] = "1",
|
|
-- ["Index"] = 1,
|
|
-- ["Markdown"] = [===[
|
|
-- ## Getting Started
|
|
--
|
|
-- This AI Studio installation is managed by your organization.
|
|
-- Please use the preconfigured providers and follow your internal
|
|
-- AI usage guidelines.
|
|
--
|
|
-- Further information is available in the [internal wiki](https://example.org/wiki).
|
|
-- ]===]
|
|
-- }
|
|
|
|
-- Mandatory infos that users must explicitly accept before using AI Studio:
|
|
-- AI Studio asks users again when Version, Title, or Markdown change.
|
|
-- Changing Version additionally allows the UI to communicate that a new version is available.
|
|
CONFIG["MANDATORY_INFOS"] = {}
|
|
|
|
-- An example mandatory info:
|
|
-- CONFIG["MANDATORY_INFOS"][#CONFIG["MANDATORY_INFOS"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Title"] = "AI Usage Requirements",
|
|
-- ["Version"] = "1",
|
|
-- ["Markdown"] = [===[
|
|
-- ## Usage Requirements
|
|
--
|
|
-- Before using this AI offering, please ensure that:
|
|
--
|
|
-- - you have completed the required internal training,
|
|
-- - generated output is clearly labeled where necessary,
|
|
-- - results are reviewed by a human before reuse,
|
|
-- - all internal policies and applicable law are followed.
|
|
--
|
|
-- Further information is available in the [internal wiki](https://example.org/wiki).
|
|
-- ]===],
|
|
-- ["AcceptButtonText"] = "Yes, I comply with these requirements",
|
|
-- ["RejectButtonText"] = "Stop. I do not agree to these requirements"
|
|
-- }
|
|
|
|
-- Document analysis policies for this configuration:
|
|
CONFIG["DOCUMENT_ANALYSIS_POLICIES"] = {}
|
|
|
|
-- An example document analysis policy:
|
|
-- CONFIG["DOCUMENT_ANALYSIS_POLICIES"][#CONFIG["DOCUMENT_ANALYSIS_POLICIES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["PolicyName"] = "Compliance Summary Policy",
|
|
-- ["PolicyDescription"] = "Summarizes compliance-relevant clauses, obligations, and deadlines found in provided documents.",
|
|
--
|
|
-- ["AnalysisRules"] = [===[
|
|
-- Focus on compliance obligations, deadlines, and required actions.
|
|
-- Ignore marketing content and high-level summaries.
|
|
-- Flag any ambiguous or missing information.
|
|
-- ]===],
|
|
--
|
|
-- ["OutputRules"] = [===[
|
|
-- Provide a Markdown report with headings for Obligations, Deadlines,
|
|
-- and Open Questions.
|
|
-- ]===],
|
|
--
|
|
-- -- Optional: minimum provider confidence required for this policy.
|
|
-- -- Allowed values are: NONE, VERY_LOW, LOW, MODERATE, MEDIUM, HIGH
|
|
-- ["MinimumProviderConfidence"] = "MEDIUM",
|
|
--
|
|
-- -- Optional: the tools an analysis with this policy may use, by tool ID.
|
|
-- -- This is a limit, not a preselection: a tool which is not listed here cannot be
|
|
-- -- used for this policy. Omitting the list, or leaving it empty, means no tools.
|
|
-- -- A listed tool must still meet the confidence requirements of the provider in
|
|
-- -- use, so a tool may stay unavailable even though this policy permits it.
|
|
-- -- Tool IDs include: web_search, read_web_page
|
|
-- ["AllowedToolIds"] = { "web_search" },
|
|
--
|
|
-- -- Optional: preselect a provider or profile by ID.
|
|
-- -- The IDs must exist in CONFIG["LLM_PROVIDERS"] or CONFIG["PROFILES"].
|
|
-- ["PreselectedProvider"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["PreselectedProfile"] = "00000000-0000-0000-0000-000000000000",
|
|
--
|
|
-- -- Optional: hide the policy definition section in the UI.
|
|
-- -- When set to true, users will only see the document selection interface
|
|
-- -- and cannot view or modify the policy settings.
|
|
-- -- This is useful for enterprise configurations where policy details should remain hidden.
|
|
-- -- Allowed values are: true, false (default: false)
|
|
-- ["HidePolicyDefinition"] = false
|
|
-- }
|
|
|
|
-- Profiles for this configuration:
|
|
CONFIG["PROFILES"] = {}
|
|
|
|
-- A simple profile template:
|
|
-- CONFIG["PROFILES"][#CONFIG["PROFILES"]+1] = {
|
|
-- ["Id"] = "00000000-0000-0000-0000-000000000000",
|
|
-- ["Name"] = "<user-friendly name of the profile>",
|
|
-- ["NeedToKnow"] = "I like to cook in my free time. My favorite meal is ...",
|
|
-- ["Actions"] = "Please always ensure the portion size is ..."
|
|
-- }
|