Glob.AI OS Deployment Guide - 2026-04

Below are the end-to-end procedures required to deploy Glob.AI OS for Version 2026-04.

See also the version updates for the main platform components.

Version: 2026-04 Hot Fix 7 (July 8)

No manual steps required for this Hot Fix.

Version: 2026-04 Hot Fix 6 (July 2)

No manual steps required for this Hot Fix.

Version 2026-04 Hot Fix 5 (June 29)

No manual steps required for this Hot Fix.

Version 2026-04 Hot Fix 4 (June 25)

Additional manual steps

Apply this migration to the MySQL database in order to speed up some application features:

CREATE INDEX UWORKITEMREQUEST_BYREQUESTID ON WorkitemRequest (WorkitemRequestId );
DROP INDEX UREQUEST_AIMODEL ON Request;
CREATE INDEX UREQUEST_AIMODEL ON Request (RequestAIModelName ,RequestStatus ,RequestTimestamp ,RequestId );
CREATE INDEX UREQUEST_RECALC ON Request (RequestStatus ,RequestSource ,RequestTimestamp ,RequestId );

Iris

1. Logged in with the SuperAdmin role, go to Console > System > System Modules.
2. Locate the module The Lab: Iris and install.

Version 2026-04 Hot Fix 3 (June 19)

No manual steps required for this Hot Fix.

Version 2026-04 Hot Fix 2 (June 18)

Console - Change Value for Parameter REMOTE_MODULE_CATALOG_URL

1. Go to Glob.AI OS Console > Superadmin Options > System > Parameters
2. Search parameter REMOTE_MODULE_CATALOG_URL > Update
3. Set new Value S as: https://qa-saia-remote-modules.s3.amazonaws.com/main-modules-catalog.json
4. Confirm.

Version 2026-04 Hot Fix 1 (June 11)

Install and configure Teramot Integration

Logged in with the SuperAdmin role, follow these steps:

A. Install the module

1. Go to Console > System > System modules.
2. Look for the module called The Lab Tools: Teramot.
3. Choose the Install option on its card.

B. (Optional) Set up a global configuration

If you want to configure a global clientId for the entire installation:
1. Go to System > Parameters.
2. Create a new parameter with the following values:
Key
$(toolplugin_98578536-b5a9-4524-9f61-f5f6de728857_securityScheme.flows.authorizationCode.clientId)
Value
<your-client-id>
3. Replace <your-client-id> with the client ID you want to use across the whole installation.
4. Click Advanced and set the scope to System.
5. Save the parameter.

Version 2026-04 (June 8)

Post-Deployment Manual Steps

Complete the following manual steps after the deployment finishes successfully.

1. Go to SuperAdmin Options > System > Parameters and filter by name: GAM_MENU_SETTINGS
   Then, update it (Update action) and replace the “Value S” by copying the content of the following file: GAM_MENU_SETTINGS
   This step enables the new menu entries introduced in the release, including:
   • Build > Reasoning Strategies
   • Monitor > Session Activity
2. Go to SuperAdmin Options > System > Parameters and filter by name GAM_PERMISSION_ROL_SETTINGS
   Then, update it (Update action) and replace the “Value S” by copying the content of the following file: GAM_PERMISSION_ROL_SETTINGS.
   This step is required to update the role-permission’s schema to handle the new menu options. "Strategies_Access", "Monitor_Access" and "Session_Activity_Access".
3. Reinstall the module Security Configuration (rev: 43 or higher):
   Go to SuperAdmin Options > System > System Modules and look for “Security Configuration”. Reinstall it even if it appears updated.
4. Install Agent Hub Process Components
   Go to SuperAdmin Options > System > System Modules and look for “Agent Hub Process Components”. Install it.
5. Install module The Lab Tools: OneDrive Tools (rev: 1).
   Go to SuperAdmin Options > System > System Modules and look for “The Lab Tools: OneDrive Tools (rev: 1)”. Install it.

For Iris configuration

1. Get the API Token.
2. Go to SuperAdmin Options > System > Parameters
3. Create a new parameter named:
   $(toolplugin_17f3c003-85f3-4a10-8176-524ecf94a99c_Authorization)
4. In Value, paste the API Token.
5. Ensure that this is a System parameter in advance options.
6. Go to SuperAdmin Options > System > System Modules
7. Look for “The Lab Public Components” and click on Update.

My Creations Module Visibility Fix

Follow these steps:
1. Update the GAM Menu Parameter
2. Reinstall the Security Configuration Module

1. Update the GAM Menu Parameter

Navigate to Systems > Parameters and select the GAM_MENU_SETTINGS parameter for editing.
Locate the #MyCreations entry in the JSON and update the permissionName field as follows:

The resulting JSON block should look like this:

{
  "id": "#MyCreations",
  "name": "My Creations",
  "description": "My Creations",
  "option": true,
  "permissionName": "Basic_Access",
  "icon": "",
  "linkTarget": "",
  "link": "",
  "optionAvailable": "",
  "idExternal": "14",
  "idMemberHub": "9"
}

2. Reinstall the Security Configuration Module

Navigate to Systems > System Modules and reinstall the Security Configuration module.
This step is required — reinstalling this module regenerates the menu and applies the permission changes.

Validation After completing the steps above, verify that:
- Consumer-role users (Frontend role) can see the My Creations module in the Discover navigation.
- Builder-specific controls (edit, publish, etc.) are not visible to consumer-role users.

External Solutions, parameters correct values

Navigate to System > Parameters and verify the following parameters are set to the correct values. If any value differs, update it accordingly.

URL Parameters

Email Subject / Template Parameters

Optional Configurations

Vertex AI Models

1. In Console, go to SuperAdmin Options > System > System Modules
2. Install the Google GenAI on Vertex AI Rev. 147 of the remote module if needed.
3. Go to SuperAdmin Options > AI Settings > AI Models
4. In Contains, search for: vertex_ai/gemini-3.5-flash
5. Update.
6. Set Status to "Active".
7. Confirm.
8. Repeat steps 3 to 7 with: vertex_ai/gemini-3.1-flash-lite
9. Test the models creating an Agent in the Agentic Hub.