No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

To give more details here, if instead of an organization token I use a personal access token, I'm able to create the stack 'pippo' without issues (I'm an admin for my organization). Apparently the problem is create a stack using an organization token (even if admin).

are you logged into the service in the locatiin you’re using automation API?

If I run the `pulumi whoami -v`  command I actually see the details I'm expecting,
```User: &lt;organization-name&gt;
Organization: &lt;organization-name&gt;
BackendURL: &lt;my-organization-backend-url&gt;```


I can destroy an existing stack with the organization token, I can't create a new stack

in your org setting:

<https://app.pulumi.com/>&lt;orgname&gt;/settings/access-management

CleanShot 2023-08-04 at 09.44.30@2x.png

Stack permission for all members: None
False
False
True
(Sorry, can't upload image)

if you set the top one to true instead of false it’ll fix it

but that would give permission to all users with write permissions to create stacks am I right? We only want admin users to have such permission

&gt; To give more details here, if instead of an organization token
Organization tokens only have member access. There is an upcoming change to allow org tokens with admin access, but not sure of its ETA

I think this is available on the frontend at least

But even if I activate the "Admin Access" the token doesn't have the rights to perform admin operations like create a stack

I've opened a ticket on github for reference <https://github.com/pulumi/pulumi-cloud-requests/issues/287>