General
System-wide settings — interface languages, startup screen, user intervention logging, security policy, and project management.
On this page

The General settings page controls application-wide behavior through six collapsible sections. Click any section header to expand it.
Languages
Defines which interface languages are available to users. The application ships with English (en) as the default. Additional languages can be added with the Add New Language button — once added, individual users can switch to their preferred language in their account settings.
Drag the handles (⠿) to reorder languages in the selector. Remove an unused language with the × button.
Translating texts
Next to Add New Language there are three more buttons:

| Button | What it does |
|---|---|
| Export Translations | Saves the texts of the project to a file, for example for an external translator. |
| Import Translations | Loads translated texts back into the project. |
| Autofill translations with AI | Lets the AI translate all texts that are still missing in the additional languages. |
Autofill translations with AI uses the AI provider that you set in AI Engineer, so that section has to be enabled and have a valid API key. There is no confirmation question — the translation starts as soon as you click the button, and a window shows the progress:

- Missing translations — the number of texts still missing in each language,
- Translations saved — texts that the AI translated and the project stored,
- Not translated — texts that the AI did not translate,
- Skipped (changed meanwhile) — texts that were changed while the translation was running.
When nothing is missing, the window reports All texts are already translated. Newly translated texts are saved in the project immediately, so create a backup in Settings → Backup before you translate a large project, and have the result checked by someone who speaks the language.
Startup Screen
Component — The HMI view or report page that opens automatically when users log in. Leave blank to show the default Welcome screen. Set this to a specific component (a report view, a live data dashboard) to send all users directly to their working view after login.
To assign a startup screen, drag a view or component from the main component tree into the Component field and save the settings.
This is the project-level default. Individual users can have their own startup screen set in Users.
User interventions
Records all manual changes made by users — tag writes, report triggers, configuration edits — with a timestamp and the username. Useful for shift handover documentation, audit trails, and troubleshooting.
Enable — Turn user intervention logging on or off.
Storage — How long the intervention log is retained (default: 1y 0m 0d 0h = 1 year). After this period, old entries are automatically deleted.
Security
Anonymous Autologin — When enabled, users can access the application without entering credentials. Suitable only for closed, controlled environments (dedicated operator panels with no network exposure). Disable for any installation accessible from a shared network.
With Anonymous Autologin enabled, any device that can reach the application URL gains full access. Enable only on physically secured, network-isolated operator terminals.
AI Engineer
AI Engineer brings artificial intelligence into the project design. It consists of two independent parts — you can use either of them or both:
- the built-in AI assistant, a chat panel directly in the Designer,
- the MCP server, through which you connect an external AI tool of your choice to the project.

Built-in AI assistant
The assistant understands the whole project — assets, tags, connections, graphics, logic and data — and turns your instructions into real project components. Describe what you want to build, change or find, for example “Create a view with a gauge for tag 1.Motor.Speed”.
Setting it up
Open Settings → General, expand AI Engineer and tick Enable in the upper part (the assistant).
Select the provider and its model in AI Provider and Model:
| Provider | Models offered | Default |
|---|---|---|
| Anthropic Claude | claude-opus-5-5, claude-sonnet-5, claude-haiku-4-5 | claude-opus-5-5 |
| OpenAI | gpt-5, gpt-5-mini | gpt-5 |
| Google Gemini | gemini-2.5-pro, gemini-2.5-flash | gemini-2.5-pro |
| Ollama (runs on your own server) | qwen3, gpt-oss:20b, llama3.1 | qwen3 |
After you save the settings, the list of models is loaded from the provider. If that is not possible, the default models are shown.
Paste the API Key of your provider account. Use the eye icon to check what you typed. For Ollama you enter the address of the server instead of a key (by default http://localhost:11434), optionally an access token and the size of the context window (65 536 tokens by default).
Max. Output Tokens limits the length of a single answer of the assistant.
Save the General page. The assistant is active when it is enabled and has an API key (Ollama does not need a key).
Working with the assistant
The assistant opens from the AI Engineer tab on the right edge of the Designer. Write the request into the field at the bottom (Enter sends it, Shift+Enter starts a new line). While the assistant works, the panel lists the individual steps, for example Reading: views or Creating a tag, and then shows the answer. If a step fails, the assistant usually corrects it and tries again.

At the top of the panel you can start a new conversation and open the history of previous ones. Stop interrupts a running answer, and a conversation can be exported to a PDF.
- The assistant works with the permissions of the logged-in user.
- Its changes are saved immediately and there is no button to take them back. Before bigger changes create a backup in Settings → Backup.
- The assistant can make mistakes — check important results.
- Requests are billed by the provider of your API key. Ollama runs locally and has no per-request cost.
MCP server
The MCP server publishes the project to external AI tools that support the MCP protocol (Claude Desktop, Claude Code, ChatGPT, Gemini, Cursor…). Such a tool can then read and edit the project in the same way as the built-in assistant, but from its own environment — useful when you want to combine the project with other work (files, web, version control) or to make larger batch changes.
Setting it up
In AI Engineer tick Enable in the lower part (the MCP server).
Enter an OAuth Password — at least 5 characters, otherwise the settings cannot be saved. The AI tool asks for this password when it connects for the first time. Save the page.
In the AI tool add an MCP server with the address http://<address-of-the-server>/mcpdesigner. For Claude Desktop it looks like this in claude_desktop_config.json:
"datatalk-project-designer": {
"command": "npx",
"args": ["-y", "mcp-remote", "http://localhost/mcpdesigner"]
}mcp-remote needs Node.js. If DataTalk runs on another computer, replace localhost with its address. Outside a local network use HTTPS.
What the AI tool can do
| Area | Examples |
|---|---|
| Connections | Create, edit and delete connections — Modbus, OPC UA, MQTT, EtherNet/IP, databases, REST API, Loxone… |
| Tags | Tags, UDT, ƒx templates and formulas, ranges, limit templates. |
| Views | SVG graphics, inserting components and symbols, animations, commands, opening views, portrait layout, dark mode, translations of texts. |
| Other | Dashboards, charts, tables and linked tables, scripts and custom components. |
What it cannot do
- It does not see the result. The tool works with the drawing data, not with a picture of the screen — check layouts and colors yourself.
- It does not read or write live values of tags, manage users and permissions or delete the project. It designs the project; it does not control the running process.
- Its changes are saved immediately as well — make a backup first.
The AI Expert settings of the project contain a separate MCP Server switch for the AI assistant that works with the current data of the running system. It belongs to the AI Module and has nothing to do with AI Engineer.
Which one to use
| Built-in assistant | MCP server | |
|---|---|---|
| Best for | Quick changes directly in the Designer | Larger batch changes, work together with other tools |
| You need | An API key of an AI provider | An AI tool that supports MCP and the OAuth password |
Delete Project
Permanently deletes the entire project configuration — all connections, tags, report templates, users, and settings. Historical data and generated report files may also be affected depending on storage configuration.
Take a Backup before using Delete Project. There is no confirmation step that can be undone — once deleted, the project configuration cannot be recovered.