Each customer order is now mapped to a Team. The total capacity limits (e.g. RAM, CPU, storage, etc.), add-ons, features and expiration date are set per Team as part of the order on-boarding. At least one Team Manager will be assigned at that time. Team Managers can change the team name, add/remove other managers and update the primary POC info.
Projects remain the primary grouping of users and resources at the application level. The rules for seeing & sharing assets, and for managing users & permission remain the same for each Project. However, Projects are now managed by a Team. Each Team can have one or more projects; a default project of the same name is automatically created to get things started. Team Managers can create additional projects up to the limits of their package. They can also sub allocate the capacity limits to each project (not to exceed the team total) and set an optional expiration date.
Any user on the site can see the name & description of Projects and they can request to join unless the Project is set to private, then no one will see it.
There is a new workflow for users to request Project membership. Project Managers can block requests to prevent repeated attempts.
Teams can registers cloud resources they pay for directly (e.g. an AWS account). Some networks may have connectivity or firewall restriction so please contact support if you want to make one of these connections. Team Managers can create cloudspaces if they directly own the cloud; soon, they will be able to request new cloudspaces in clouds managed by others.
For the first time, Team Managers have control over their cloudspace resources. They are able to create and manage networks, enable remote access and adjust performance parameters. They can control which projects can access which cloudspaces and which templates should be made available. Additional networking and firewall management features will be rolling out over the next few releases.