Labeling and Usage Statistics

This page covers two settings that concern the rules of your organization: a notice that labels AI-generated content, and statistics about which features of AI Studio send requests to your own AI servers.

Labeling AI-generated content

Rules on transparency, such as the EU AI Act, may require that a text says when an AI generated it, for example, when your colleagues publish it. AI Studio can add such a notice: AI answers that users copy or export then end with a paragraph of its own, in bold, saying that the content was generated using artificial intelligence. The notice is written in the language of the app. It's off by default.

What gets the notice

• Copied answers: the copy button of an answer in the chat or in an assistant, and the "Copy result" button of the assistants.
• Exported answers: every format of the export menu, that is, Word, OpenDocument, LaTeX, web page, and Markdown.
• Files of the Batch Processing Assistant, when it writes one file per document.

Content that one more sentence would break, or that goes on to a program or another model rather than to a reader, stays unchanged:

• code blocks copied on their own, and single files or tables exported from an answer;
• the CSV table of the Batch Processing Assistant;
• the Lua code of the Assistant Builder and the prompt of the Prompt Optimizer;
• visual briefings, which AI Studio exports exactly as it checked them;
• messages of the users, transcripts, IDs, and paths.

The notice covers what AI Studio copies and exports itself. Text that somebody selects and copies by hand carries no notice. So the setting supports the rules of your organization, but it can't enforce them.

Switching on the notice

For everybody, without a way to opt out:

CONFIG["SETTINGS"]["DataApp.AddAIGeneratedContentDisclosure"] = true

As the default of your organization, which users may change:

CONFIG["SETTINGS"]["DataApp.AddAIGeneratedContentDisclosure"] = true
CONFIG["SETTINGS"]["DataApp.AddAIGeneratedContentDisclosure.AllowUserOverride"] = true

Set it to false without AllowUserOverride to keep everybody from switching it on.

Feature usage statistics

When your organization runs its own AI servers, for example, behind a LiteLLM gateway, you may want to know which features of AI Studio your colleagues use: the chat, the assistants, the agents. AI Studio can name the feature in the User-Agent header of each request it sends to these servers. Your servers log it like any other header; LiteLLM, for example, shows it as a tag of the request. This is off by default, and AI Studio then sends no User-Agent at all.

What your servers receive

Request sent by	User-Agent
The chat	MindWorkAIStudio/26.10.1 (win-x64) Component/CHAT
The Translation Assistant	MindWorkAIStudio/26.10.1 (win-x64) Component/TRANSLATION_ASSISTANT
The agent that selects data sources	MindWorkAIStudio/26.10.1 (win-x64) Component/AGENT_DATA_SOURCE_SELECTION
An assistant plugin of your organization	MindWorkAIStudio/26.10.1 (win-x64) Component/DYNAMIC_ASSISTANT Assistant/Cafe-Menu-Writer-Beta
Transcriptions, embeddings, and model lists	MindWorkAIStudio/26.10.1 (win-x64)

• The platform is one of win-x64, win-arm64, linux-x64, linux-arm64, osx-x64, and osx-arm64.
• The User-Agent names neither the user nor the device.
• Assistant plugins are named only when they come with AI Studio, or when your organization deployed or approved them. Users may build assistants for themselves and name them after a person or a private project; such a name never leaves the device, and the request shows only Component/DYNAMIC_ASSISTANT. A name is reduced to ASCII letters, digits, dots, underscores, and dashes, and cut after 64 characters.

Who receives it

• Only providers of the types self-hosted and LiteLLM. AI Studio decides by the type of the provider, not by its address.
• Cloud providers never receive it, such as OpenAI, Anthropic, Google, or Mistral.
• Other services never learn which feature sent a request, such as ERI servers, Confluence, or web pages.
• AI Studio sends no usage data to its developers, with or without this setting.

What the numbers mean

• They count requests, not uses. One message in the chat may cause several requests: each round of tool calls is a request of its own, and when a chat searches its data sources with every message, agents select and check them first. Some assistants work in several steps, and the Batch Processing Assistant sends one request per file.
• Agents appear under their own name, not as part of the chat.
• Transcriptions, embeddings, and model lists name only the app. Your server sees from the endpoint which kind of request it was.

Before you switch it on

As long as your server can't tell users apart, the numbers say how often each feature is used, and nothing about anybody in particular. That changes as soon as it can: for example, when every user has an API key of their own, such as a virtual key in LiteLLM, or when your logs keep the IP addresses of the devices. The usage data then relates to persons, and data protection law applies. In some countries, such as Germany, evaluating it may also need the consent of your works council, because it could be used to monitor the behavior or performance of employees.

Clarify this before you switch it on, evaluate the numbers per feature rather than per person, and tell your colleagues that their requests name the features they use.

Switching it on

For everybody, without a way to opt out:

CONFIG["SETTINGS"]["DataApp.ShareFeatureUsageWithSelfHostedServerOperators"] = true

As the default of your organization, which users may change:

CONFIG["SETTINGS"]["DataApp.ShareFeatureUsageWithSelfHostedServerOperators"] = true
CONFIG["SETTINGS"]["DataApp.ShareFeatureUsageWithSelfHostedServerOperators.AllowUserOverride"] = true

Users find the setting in "Settings" → "App Options", together with an explanation of what is sent; when you lock it, they see your value. A change applies to the requests that follow.

Where to go next

• Managing Backups
• Enterprise IT