Similar question to the above… if I’m kicking tires and trying things out using my personal login, what is required to move this stuff over to a Team account? And… my project is a tool that other departments might use (they’d just need to use their own AWS credentials and modify the project config to suit their needs)… there’s nothing that would prevent them from doing that, right? They’d be able to sign up for a Pulumi plan and work with their own clone of our git repo, right?

You can move stacks between orgs.

I guess I’m not following how my local code sitting on my laptop is associated with a login? There’s nothing in the code itself that makes that association is there? Re stacks… I was only thinking in terms of the usual prod/staging stuff.

Doing the usual prod/staging/dev stacks for each project is fine and a typical setup for many pulumi users. We would advise 1 pulumi team account for everyone in your org (even if a different department) because it will make managing your stacks simpler. If you have two pulumi cloud accounts working on the same stack, than neither cloud account would have full update history and one would have drift whenever the other was updated

@crooked-ram-3551 Your Pulumi token is associated with a Pulumi Cloud user. Your Pulumi Cloud user can be a member of any number of Pulumi organizations. You can set the default organization with

pulumi org set-default

.