Organizations thrive on organization. But as the number of projects and contributors you organize within your organization grows, it becomes more and more difficult to organize your organizational permissions. That’s why we’ve introduced a new type of organizational layer that we’ve cleverly named Organizations.
Organizations allow your key contributors to manage your projects and billing, thus removing the bottleneck on the legacy project owner.
Organizations group all your projects and users together. When you set up an Organization, you can invite users and grant them specific permissions to manage plans, billing, users, and projects. For instance, when you invite billing users into your Organization, you can limit their access to your billing details and invoices. Or when you invite engineering leads, you can grant them permissions solely to create new projects or manage existing ones.
As an Organization owner, you can grant the users you invite the following permissions:
You can mix and match these permissions per user to create the most effective setup for your Organization.
We’ll be progressively rolling out Organizations in the coming weeks. Access to Organizations is automatic.
During the transition to Organizations, you will be automatically assigned to a new Organization as its owner. Your projects will transfer to that Organization, with the same per-project and environment access permissions. You can then start inviting users and editing basic Organization information, such as its name and URL.
At launch, some Organization actions might only be available from the Platform.sh CLI and the Platform.sh API. Support from the Platform.sh Console will be rolled out soon after the initial launch.
In the future, we’ll continue adding new features to your Organizations, like team permissions, access restrictions, and organization settings.