Organize solutions by categories.
Reference → Solution → Designer → Settings and Tools → Settings | Categories | Import Tags | Import Plugin | Export | History
Categories provide metadata labels for organizing and classifying objects throughout your solution. Every configuration table (Tags, Alarms, Devices, Displays, and others) has a Category column where one or more categories can be assigned to each object. Categories also control AI write permissions through the built-in MCP category.
Access: Solution → Categories
Categories Grid
The Categories table in Designer shows the following columns:
| Column | Description | Type | Required |
|---|---|---|---|
| Name | Category identifier. Must be unique across the solution. | Text | Yes |
| Description | Purpose or usage notes for this category. | Text | No |
| EnableMCP | Marks whether AI tools may change this category. See EnableMCP and AI Permissions below. | Checkbox | No |
A solution supports up to 64 categories.
Assigning Categories to Objects
Most configuration tables include a Category column. Click the Category cell on any object row to open a checkbox dialog where you can select one or more categories. The assigned categories appear as a semicolon-separated list in the cell.
Tables that support category assignment include:
| Module | Tables |
|---|---|
| UNS | Tags |
| Devices | Channels, Nodes |
| Alarms | Items |
| Displays | List, Layouts |
Categories are stored internally as a bitmask, which is why the maximum is 64 categories per solution.
EnableMCP and AI Permissions
By default, AI tools work on objects that carry the built-in MCP category.
- Objects the AI tools create receive the MCP category automatically.
- To open an existing object to AI changes, add MCP to its Category in Designer.
- The MCP category is created automatically when AI tools are used. It cannot be renamed or deleted.
The EnableMCP checkbox on a category marks whether AI tools may change that category itself.
Best Practices
- Define categories before creating objects so they are available for assignment from the start.
- Use a consistent naming convention across the solution.
- Use the Description field to document each category’s purpose, especially when multiple engineers work on the same solution.
- Check usage before deleting a category — objects that reference it will lose that classification.
In this section...