An organization is the primary grouping unit for stacks within the Pulumi Console. When you sign into the Pulumi Console, a personal account is automatically created for you and subscribed to the Pulumi Community plan.
You can however be a member of multiple Pulumi organizations, and collaborate with other developers.
If you’re a Pulumi organization admin, you have the ability to:
- Invite users
- Manage default stack permissions for the organization
- Create teams and manage their permissions
- Assign organization roles for role-based access control (RBAC) to your organization’s stacks
Creating a New Organization
You can create a new Pulumi organization directly from the Pulumi Console.
A Pulumi organization needs to be linked to a third-party identity provider, offering an additional layer of security for you and your team. While membership within the Pulumi organization is managed by an organization admin, you must be a member of the backing third-party identity provider in order to join a Pulumi organization.
For example, if a Pulumi organization,
https://app.pulumi.com/robot-co, is backed by
a GitHub organization,
https://github.com/robot-co, then only members of
https://github.com/robot-co may be
Similarly, as soon as someone loses access to the GitHub organization, they will no
longer have access to the Pulumi organization it is backing.
The following table shows the relationship between a Pulumi organization and third-party groupings.
In addition, a Pulumi organization may be backed by a SAML 2.0 identity provider.
To add a GitHub-backed organization to Pulumi, an admin of the GitHub organization
first grant the Pulumi OAuth app the
read:org scope. This can be done on GitHub’s
Pulumi requires the
in order to verify memberships within the GitHub organization. The Pulumi Console
will not have access to any of the organization’s source code, issues, or other data.
To add a GitLab-backed organization to Pulumi, an admin of the GitLab group may add the group to Pulumi, and invite its members to join Pulumi.
GitLab allows group admins to add members with a temporary membership, i.e., with an expiration value. In order to invite those members to Pulumi, their membership in the GitLab group must still be active. As soon as their GitLab group membership expires, those users will lose access to the GitLab-backed organization on Pulumi.
To add a Bitbucket-backed organization to Pulumi, an admin of the Atlassian Bitbucket workspace must first grant the Pulumi Oauth app read access to their Bitbucket account and workspace membership information.
Once the Pulumi organization has been created, the admin can see a list of Bitbucket workspace members that they can add or invite to the Pulumi organization. See Switching Organizations to learn more.
SAML Single Sign-on (SSO)
Pulumi Enterprise provides more options for identity and access, including support for any SAML 2.0-based identity provider.
Learn more about configuring a SAML-based organization on Pulumi. Or refer to one of our guides:
If you need help configuring or would like us to officially support another SAML identity provider, please contact us.
The Organization drop-down list displays all of the organizations your account is associated with, and lets you add a new organization backed by a third party identity provider. To switch to a different organization:
- Select the organization drop-down list in the upper left corner of the Console screen next to the Pulumi logo.
- Select your organization name. The organization page view is dependent on your role within the Pulumi organization.
Members. Pulumi organization members only see the Stacks and People tabs.
Admins. Pulumi organization admins see the Stacks, People, Teams, Webhooks, and Settings tabs.
|Dashboard||An overview of the organization including recently updated stacks, recent activity, and a resource count graph.|
|Projects||A searchable list of organization stacks that you can group by project and tag. For more information, see Project and Stack Management.|
|Members||A list of active members of the Pulumi organization.|
|Teams||A Team Pro feature that provides a way to assign stack permissions to groups of organization members.|
|Policies||Lists of organization policies and policy groups. Policies allow you to set guardrails to enforce best practices and compliance.|
|Settings||Organization settings including subscription and payment information and history, stack permissions, and links to Pulumi’s continuous delivery guides.|