New Feature: Team Segmentation of Savings Hub

Cloudthread launched Team segmentation for the Savings Hub functionality. This gives admins the ability to create Teams, segment the infrastructure those Teams have visibility into, and assume the role of team members to test their visibility. This means users assigned to a team only see costs and savings associated to their segment of infrastructure.

Organizations want to create a culture of cloud cost accountability for their teams. Logging into Cloudthread and seeing Savings Opportunities from across the entire company is overwhelming and counterproductive. Organizations can use Teams to make sure that when users login they’re seeing Savings Opportunities, Savings, and Waste that they’re accountable for.

Teams have an assigned Global Filter that silos infrastructure available to them. This segmentation can be done by AWS Account, AWS Payer Account (if there’s multiple CUR files), Regions, Services, AWS Cost Allocation Tags, and AWS Organization Account Tags.

Frequently Asked Questions:

1. What can Team segmentation be segmented by?
   AWS Account, AWS Payer Account (if there’s multiple CUR files), Regions, Services, AWS Cost Allocation Tags, and AWS Organization Account Tags
2. Do all users have to be on a Team?
   No. Users can be assigned to no team and if they are on no team they can see the entire organization’s cost.
3. Can Team assignment be done during user creation?
   Yes. When users are created an Admin will be prompted to select a Team (or accept No Team).
4. Can a user be part of multiple teams?
   No. A user can only be a member of one Team. Admins can toggle between different Team visibility.
5. Is Team infrastructure segmentation mutually exclusive?
   Yes. Infrastructure attributed to one team can’t then be attributed to another.