Today’s feature: RBAC for CostFormation Namespaces
CostFormation is how your organization models cost allocation. As more teams adopt it, protecting that logic matters. RBAC for CostFormation Namespaces lets you scope access at the namespace level, so the right people can view and edit Dimensions, and everyone else can’t.
Why it matters
As more teams touch CostFormation, the risk of someone editing a Dimension they shouldn’t grows quickly. Until now, there was no way to scope access. It was all-or-nothing.
As CostFormation use grows, teams need more than shared access. RBAC (rules-based access control) for CostFormation Namespaces solves that. Restrict sensitive allocation logic to specific teams, delegate ownership without exposing every definition org-wide, and support multiple teams working in parallel.
Image: The CloudZero Settings page showing four Dimension Namespaces, Defined, Research, Finance, and Engineering, alongside an open “Edit Namespace” panel for Finance, where administrators can toggle View and Edit permissions on or off for each role in the organization, giving teams precise control over who can access each namespace.
How it works
Teams can now control who views and edits CostFormation Dimension definitions at the namespace level across the platform, Public API, and VS Code Toolkit, so there’s no side door to worry about.
See it in the CloudZero platform.
