Global Settings (v1.6.27) - Monthly Release Notes
Release Details - Global Settings - v1.6.27 - July 29, 2026
This article is intended for Salesforce administrators and IT teams responsible for managing Flosum Cloud Apps tenant configuration, organizations, users, and roles.
Release Type
Monthly
Applies to Flosum-hosted and self-hosted
Prerequisites
A registered and configured Flosum Cloud Apps tenant
Appropriate Flosum user permissions (SystemAdministrator or equivalent)
Summary
This article documents the patch release for Global Settings (1.6.27). This monthly release introduces Topologies, a new way to organize and scope Salesforce orgs across Flosum Cloud Apps, along with a new Development organization type.
Multiple Topologies per Tenant
Before this release, the DevOps app worked from a single set of connected organizations, which gave the whole tenant one shared working context: one codebase, one set of branches, one set of pull requests. Topologies remove that restriction. A tenant can now hold as many Topologies as it needs, and each one is a self-contained working context with its own organizations, branches, pull requests, and pipelines.
Global Settings
A Topology groups a single Production organization with its related Development and Sandbox organizations. You manage Topologies on the new Topologies page in Global Settings, which lists every Topology in the tenant alongside its Production organization and organization counts.
Topology assignment is now part of the connection flow. When connecting a new organization, you select an existing Topology or create one on the fly. The Organizations table now includes a new Topology column.
DevOps
In the DevOps app, a Topology switcher lets you move between Topologies. Selecting a different Topology changes your entire working context, so work in one Topology never surfaces in another.
Production and Development Types
The organization Type field previously offered only Production and Sandbox, mirroring the two Salesforce org types. This release adds a third type, Development, so that a tenant can connect more than one Salesforce production org while still identifying a single Production organization within each Topology.
From Salesforce's perspective, there is no difference between the two types. A Production organization and a Development organization are both Salesforce production orgs, connected the same way. The distinction is a Flosum one, and it describes the role the org plays in your Topology:
Production: your main live production org, the one the business runs on.
Development: any other Salesforce production org used for development or testing rather than live business operations. A Topology can contain several.
Sandbox: a Salesforce sandbox. Sandbox organizations are unchanged by this release. A Topology can contain several.
Topology Migration
All tenants start with a Default Topology, and all existing organizations are migrated into it. Organizations previously marked as Production became Development, since a Topology can hold no more than one Production organization.
No action is required after this release
Backup & Archive and Data Migrator are unaffected.
DevOps continues to work as before, with every organization in the Default Topology.
You are not required to mark any organization as Production.
Act only if you want to take advantage of multiple Topologies, which means creating additional Topologies and assigning organizations to them. Mark as Production is available in the Organizations list if you want to designate a live production org, but it remains optional.
Topology Permissions
The Manage organization permissions section in the Create Role and Edit Role forms is now Topology permissions, and it applies across Backup & Archive, DevOps, and Data Migrator. Adding a Topology to a role lists all organizations within it. However, the individual permissions are still assigned per organization, and your existing permissions remain unchanged.
Last updated
Was this helpful?