Local groups can now be created directly in Tosca Cloud, giving release owners a platform-managed way to assign roles and workspace access when identity-provider synchronization is not the right operating path.
The September 2026 release also replaces manual entry of playlist characteristics with selectable values in a new Configurations tab. For enterprise test organizations, these are focused workflow changes: one improves access administration, while the other reduces configuration ambiguity before execution.
Create groups directly in Tosca Cloud
Administrators can now create groups in Tosca Cloud rather than relying only on groups synchronized from an identity provider. Local groups support the same core assignment model as synchronized groups:
- Assign Tosca Cloud roles to a group.
- Grant workspace access to a group.
- Manage group-based access without individual user-by-user assignment.
This matters when delivery teams need access structures that do not map cleanly to enterprise directory groups. Examples include time-bound program teams, external delivery partners, pilot workspaces, and specialized quality engineering functions.
The capability does not remove the need for centralized identity governance. It adds a second control path, so operating discipline matters more. Each locally created group should have a named owner, a documented business purpose, defined membership rules, and a periodic access review.
What access governance teams should decide
Local groups can shorten access provisioning lead time, but unmanaged local administration can create audit gaps. Security and platform leaders should set clear policy before broad adoption.
