Below are the end‑to‑end procedures to deploy Glob.AI OS for Version 2026-06.
Check also version updates for the main platform components.
Optional, depending on model availability.
Go to Console > System > System Modules and update the following LLM Provider modules to the latest available revision:
- OpenAI — Rev. 110
- openai/gpt-5.6-sol
- openai/gpt-5.6-terra
- openai/gpt-5.6-luna
- Google GenAI on Vertex AI — Rev. 157
- vertex_ai/gemini-3.7-flash
- xAI — Rev. 23
Follow this procedure only if the Analytics menu appears in the OS menu.
Disable Monitor → Analytics
- Go to Console > SuperAdmin Options > System > Parameters and filter by name GAM_MENU_SETTINGS.
-
Find the section where "id": "#Monitor" is located and, within its subMenu section, remove this object:
{
"id": "#Analytics",
"name": "Analytics",
"description": "Analytics",
"option": true,
"permissionName": "Analytics_Access",
"icon": "",
"linkTarget": "",
"link": "",
"optionAvailable": "",
"idExternal": "27",
"idMemberHub": "9"
}
Respect the JSON format. When you remove this object you may also need to delete a trailing comma — this only applies if it was the last element in the array.
- Go to Console > SuperAdmin Options > System > System Modules and look for Security Configuration. Reinstall it even if it appears already updated.
- QuotaLimit audit and migration process
- Get an Oauth Access Token with an Administrator role.
- Launch the Audit Quota Consumption routine via a worker job. Use the OAuth Access Token in the Authorization header.
curl --location 'https://$BASE_URL/v2/admin/job-queue' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer $Oauth_accesstoken' \
--data '{
"topic": "Default",
"process": "audit_organization_quota_consumption"
} '
The endpoint returns 200 OK and a JSON body with the created job id.
- In Console > SuperAdmin Options > System > Operation Logs confirm completion within one minute. Filter by Pgmname: "AuditOrganizationQuotaConsumption" and verify the Log Step FINISHED.
- Launch the Quota Maintenance Runbook via a worker job, using the OAuth Access Token in the Authorization header.
curl --location '$BASE_URL/v2/admin/job-queue' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer Oauth_accesstoken' \
--data '
{
"topic": "Default",
"process": "run_quota_maintenance_runbook"
}
'
The endpoint returns 200 OK and a JSON body with the created job id. This step must be run only once.
- In Console > SuperAdmin Options > System > Operation Logs confirm completion within one minute. Filter by Pgmname "RunQuotaMaintenanceRunbook" and verify the Log Step FINISHED.
- Export the audit records from the OperationLog table in the saia_prod schema (prefer CSV for compatibility with Excel). Use this SQL Statement (The report tracks all operations applied by the launched processes):
Select OperationLogTimestamp, OperationLogPgmName, OperationLogData from OperationLog
where (OperationLogPgmName = 'GBrain.Data.UsageLimits.ARunQuotaMaintenanceRunbook'
OR OperationLogPgmName = 'GBrain.Data.UsageLimits.AAuditOrganizationQuotaConsumption'
OR OperationLogPgmName = 'GBrain.Data.UsageLimits.AReconcileOrganizationQuotaConsumption'
OR OperationLogPgmName = 'GBrain.Data.UsageLimits.AMigrateQuotaReservationToRollup'
OR OperationLogPgmName = 'GBrain.Data.UsageLimits.AExpireSupersededActiveQuotas')
and OperationLogTimestamp >= '2026-08-18 00:00'
order by OperationLogTimestamp;
The report tracks all operations applied by the launched processes.
- Update the RAG module to the latest version (Rev: 18 or higher) under SuperAdmin Options > System > System Modules.
- Secrets Manager — re-encrypt legacy secrets onto the new primary KEK.
- Launch the Reencrypt Legacy Secrets routine via a worker job. Use the OAuth Access Token from step a in the Authorization header:
curl --request POST \
--url "$BASE_URL/v2/admin/job-queue" \
--header "Authorization: $Oauth_accesstoken" \
--header "Content-Type: application/json" \
--data '{
"topic": "Default",
"process": "reencrypt_legacy_secrets",
"Parameters": [
{
"name": "mode",
"value": "dry-run"
}
]
}'
The endpoint returns 200 OK and a JSON body with the created job id.
- In Console > SuperAdmin Options > System > Operation Logs, confirm completion within one minute. Filter by reencrypt_legacy_secrets and verify the Log Step FINISHED, then open View to review the logs.This response is not required for the runbook steps.
- In Console > SuperAdmin Options > System > Operation Logs confirm completion within one minute. Filter by "reencrypt_legacy_secrets" and verify the Log Step FINISHED. Then open View to review the logs.
- Launch the Reencrypt Legacy Secrets routine via a worker job. Use the OAuth Access token from step a in the Authorization header.
curl.exe --request POST \
--url "BASE_URL/v2/admin/job-queue" \
--header "Authorization: $env:Oauth_accesstoken" \
--header "Content-Type: application/json" \
--data '{
"topic": "Default",
"process": "reencrypt_legacy_secrets",
"Parameters": [
{
"name": "mode",
"value": "apply"
}
]
}'
The endpoint returns 200 OK and a JSON body with the created job id. This response is not required for the runbook steps.
- In Console > SuperAdmin Options > System > Operation Logs, confirm completion within one minute. Filter by "reencrypt_legacy_secrets" and verify the Log Step FINISHED, then open View to review the logs.
- Add the option to the menu.
- Navigate to Console > SuperAdmin Options > System > Parameters and filter by name GAM_MENU_SETTINGS.
- Open the parameter for editing (action Update) and the following section under “"id": "#Build"“ the “subMenu”.
- Find the section where "id": "#Monitor" is located and, within its subMenu, add the following option:
{
"id": "#Processes",
"name": "Processes",
"description": "Processes",
"option": true,
"permissionName": "Processes_Access",
"icon": "",
"linkTarget": "",
"link": "",
"optionAvailable": "",
"idExternal": "29",
"idMemberHub": "9"
}
- Note: Respect the JSON format — when adding this new section, add a comma at the end of the closing brace of the previous item's entry.
- Add the permissions to the menu roles.
- Reinstall the Security Configuration module (Rev: 48 or higher).
- Go to Console > SuperAdmin Options > System > System Modules and look for “Security Configuration”. Reinstall it even if it appears updated.
- Create the menu configuration parameter.
- Go to SuperAdmin Option > System > Parameters and use the action Create:
- Name: GAM_MENU_SETTINGS_CONF
- Scope: System
- Description: GAM_MENU_SETTINGS_CONF definition of hub items menu configuration.
- Value:
[
{
"id": "#HomeSetting",
"name": "Home",
"description": "Home (Setting)",
"option": true,
"permissionName": "SecurityHome_Access",
"icon": "",
"linkTarget": "",
"link": "",
"optionAvailable": "",
"idExternal": "70",
"idMemberHub": "69"
},
{
"id": "#AppearanceBranding",
"name": "AppearanceBranding",
"description": "Appearance & Branding",
"option": true,
"permissionName": "Appearance_Branding_Access",
"icon": "",
"linkTarget": "",
"link": "",
"optionAvailable": "",
"idExternal": "99",
"idMemberHub": "69"
}
]
- Add the permissions to the menu roles.
- Reinstall the Security Configuration module. Rev: 48 or higher (Console > SuperAdmin Options > System > System Modules). Reinstall it even if it appears as updated.
- Go to Console > System > System Modules and update the following LLM Provider modules to the latest available revision:
- OpenAI — Rev. 108
- Anthropic — Rev. 44
- Azure OpenAI — Rev. 49
- Azure AI Foundry — Rev. 31
- azure_ai_foundry/claude-opus-5
- Google GenAI on Vertex AI — Rev. 156
- vertex_ai/claude-opus-5
- vertex_ai/gemini-3.6-flash
- vertex_ai/gemini-3.5-flash-lite
- AWS Bedrock — Rev. 64
- XAI
- Go to Console > System > System Modules and update the following module to the latest available revision: