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.

Manage users and permissions across your organization

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:

• Manage Plans: Manage plans and options for your existing projects. Users with the Manage Plans permission can update the plan, the project storage, the number of development environments, and the number of user licenses.
• Manage Billing: Manage and access billing information. Users with the Manage Billing permission can edit the payment method and the billing address, download the invoices, and access the vouchers.
• Create Projects: Create new projects within the Organization.
• Manage Users: Manage users’ permissions within the Organization. Users with the Manage Users permission can edit other users’ permissions as well as their own.

You can mix and match these permissions per user to create the most effective setup for your Organization.

How do I get access to Organizations?

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.

What’s next?

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.