Admin control over Platform Builder access per workspace
C
Christian Schroer
As a Cloud Foundation Team admin, I want to control which workspaces are allowed to use the Platform Builder (to create Building Block Definitions, platforms, etc.), so that I can govern who is contributing to the internal platform service ecosystem — not just who can publish.
Current situation
Today, workspaces can self-enable the Platform Builder via a toggle in their workspace settings. While admins can control publishing approval (i.e., whether a built service becomes available to others), they cannot prevent a workspace from accessing the Platform Builder in the first place.
This means any workspace can start building and operating their own BBDs and platform instances without admin awareness or approval.
Requested capability
Admins should be able to decide — from the Admin Area — which workspaces are allowed to use the Platform Builder. This should be controllable per workspace.
J
Johannes Rudolph
As an initial idea, I see two options to implement this and consider further. Happy to hear your feedback:
- Quota-based approach:Introduce quotas for owned BBDs and Platform Instances (similar to existing workspace quotas for number of Projects and API keys). Setting a quota to zero would effectively disable the relevant Platform Builder capability for that workspace.
- Dedicated workspace setting:Add an explicit on/off toggle in the Admin Area per workspace that enables or disables Platform Builder access.
Both approaches should be manageable from the Admin Area and accessible via API for automation.
If you are also looking for this capability, please vote and share your use case in the comments!
For questions or help, reach out to support@meshcloud.io.