Differences

This shows you the differences between two versions of the page.

Link to this comparison view

262:workspace_collections [2026/09/28 19:26] – created - external edit 127.0.0.1262:workspace_collections [2026/11/19 12:40] (current) – Goetz, Sebastian
Line 3: Line 3:
 To manage complex process landscapes with many process owners, the processes should be modeled in separate process modules and then integrated into larger entities. Those process modules should have defined interfaces, e.g. via work products or roles. To manage complex process landscapes with many process owners, the processes should be modeled in separate process modules and then integrated into larger entities. Those process modules should have defined interfaces, e.g. via work products or roles.
  
-Workspace collections support this effort by automatically proposing interfaces from other process modules. Similar to elements in the same workspace, elements from all workspaces in the collection are shown in the association dialog.+A **workspace collection** groups workspaces that belong together, e.g. all process modules of a standard process, or all workspaces of a program. Collections are used in several places in Stages:
  
-[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=d5faf4&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/assignfromcollection.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/assignfromcollection.png?direct&400x330  }}]]+  * [[#association_candidates|Association candidates]] – proposing interfaces to elements in other workspaces 
 +  * [[#impact_on_process_interfaces|Process interfaces]] – creating interfaces during import, module update and copy 
 +  * [[#impact_on_search|Search]] – search scope "Recommended Workspaces" 
 +  * [[#training_scope_of_the_stages_assistant|Stages Assistant]] – training scope of the chatbot 
 +  * [[#scope_for_the_mcp_interface|MCP interface]] – scope for AI agent governance
  
-It is then possible to create an interface with a single click.+===== Set up workspace collections =====
  
 Workspace collections can be set up by the administrator via ''Administration > Workspaces'' in the ''Collections'' tab. Workspace collections can be set up by the administrator via ''Administration > Workspaces'' in the ''Collections'' tab.
Line 13: Line 17:
 [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=6c5708&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/definecollections_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/definecollections_1.png?direct&800x526  }}]] [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=6c5708&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/definecollections_1.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/definecollections_1.png?direct&800x526  }}]]
  
-If a workspace is part of multiple collections, elements from all workspaces in these collections are shown as association candidates+A workspace can be part of multiple collections. 
 + 
 +===== Association candidates ===== 
 + 
 +Workspace collections support modeling by automatically proposing interfaces from other process modules. Similar to elements in the same workspace, elements from all workspaces in the collection are shown in the association dialog. 
 + 
 +[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=d5faf4&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/assignfromcollection.png|{{  https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/76/assignfromcollection.png?direct&400x330  }}]] 
 + 
 +It is then possible to create an interface with a single click. 
 + 
 +If a workspace is part of multiple collections, elements from all workspaces in these collections are shown as association candidates. 
 + 
 +===== Impact on process interfaces ===== 
 + 
 +When processes are imported, process modules are updated or processes are copied into a workspace, Stages automatically creates process interfaces. Interface targets are searched in **all workspaces of all collections** the current workspace belongs to. If a workspace is not part of any collection, no process interfaces are created. 
 + 
 +Since Stages 26.1, workspace collections replace the former workspace settings **Group** and **Common Elements**. See [[262:collectionmigration|Migrate process interface handling to workspace collections]] for details and examples.
  
 ===== Impact on Search ===== ===== Impact on Search =====
Line 21: Line 41:
 This can be used to optimize the experience for new users, by defining a collection with all workspaces that contain content for first-time users and adding the root workspace (or all other default user workspaces) to them. This can be used to optimize the experience for new users, by defining a collection with all workspaces that contain content for first-time users and adding the root workspace (or all other default user workspaces) to them.
  
 +===== Training scope of the Stages Assistant =====
 +
 +The [[262:chatbot|Stages Assistant]] answers questions based on clearly scoped //views// of the process landscape. Each view consists either of a single workspace or of a **workspace collection**.
 +
 +Use a workspace collection as training scope if the relevant process content is spread across several workspaces, e.g. the standard development process plus organizational processes. The Assistant is then trained on the valid versions of **all workspaces in the collection**.
 +
 +Please note:
 +  * Users need read permissions for **all workspaces in the collection** to use the view.
 +  * Process interfaces to elements **outside** of the collection are ignored during training. Make sure the collection contains all workspaces needed to answer the expected questions.
 +  * For collections, a delayed automatic training (8 or 24 hours) avoids duplicate training runs when several processes in the collection are released within a short time.
 +
 +See [[262:chatbot_config|Stages Assistant Configuration]] for details.
 +
 +===== Scope for the MCP interface =====
 +
 +The [[262:mcpserver|Stages MCP Server]] connects AI systems such as chatbots and AI agents with Stages. Its **AI Agent Governance** toolset (scope ''stages:mcp:agent'') operates on **workspace collections**: a collection represents e.g. a specific process instance, from which use-case-specific process instructions are provided to AI agents in Markdown format.
 +
 +For this toolset, the collection must contain all workspaces whose process content the agents should follow, and the use-case model must be defined within the collection. See [[262:prepareprocessforagenticai|Prepare your Process for Agentic AI]] for modeling details.
 +
 +Please note:
 +  * Access through MCP is always governed by the permissions of the authenticated user, including the "read" permission on the MCP domain for the respective workspaces.
 +  * The **Chatbot Process Data** toolset (scope ''stages:mcp:read'') works on individual workspaces and does not require a collection.
 +
 +See [[262:mcpserver|Stages MCP Server]] for configuration details.