This message was deleted.

Are these scopes / policies that can be attached to these tokens?

@millions-furniture-75402 not yet, but this is something that is a priorirty and we’re actively exploring

Awesome! Great work! 🎉

Will this rollout to the Team plans at some point?

I would love to see this in the Team plan too!

Would love to see this on the Team plan too. Honestly I find it a bit of a disappointing choice to not have this in a team plan. I'm really struggling a bit how to run Pulumi in CI for my company without creating a token that has access to all my stacks across multiple organizations (incl. my personal projects).

We definitely hear the feedback on wanting this to be available for Team as well! We initially were motivated to add this in large part to support SAML-backed orgs where it was not even possible in many cases to add bot users. And so we initially designed this as something for Enterprise orgs. But ultimately, the feature does meet a need that many Team orgs have too - to have a simple organization scoped token to use in CI. So we're going to be re-visiting this question around where this is available. For now though, the workaround for non-SAML-backed orgs is typically to create a bot user, give that bot user access to the appropriate subset of your stacks, and use that bot users access tokens in CI. Not as smooth of an experience as the new Org Tokens feature, but in general should be an option for folks looking to set up automation.