# Remove new organisation

**URL:** https://vaultwarden.discourse.group/t/remove-new-organisation/1185
**Category:** Help
**Created:** [October 10, 2021, 8:49pm UTC](https://vaultwarden.discourse.group/t/remove-new-organisation/1185 "2021-10-10T20:49:58Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![JPZone](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@JPZone](https://vaultwarden.discourse.group/u/JPZone)
#### Post date: [October 10, 2021, 8:49pm UTC](https://vaultwarden.discourse.group/t/remove-new-organisation/1185/1 "2021-10-10T20:49:58Z")

</div>

Is there a way where a user can not click “new organisation” and only admins can do that?

---

<div class="post-metadata">

### Author: ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)
#### Post date: [October 10, 2021, 9:08pm UTC](https://vaultwarden.discourse.group/t/remove-new-organisation/1185/2 "2021-10-10T21:08:18Z")

</div>

That is a bit difficult since when there are no orgs, everybody is a user.

You could do two things. Create a list of users who are allowed to create orgs.

> <https://github.com/dani-garcia/vaultwarden/blob/44da9e6ca7b42fa6c02bc5e80e9dda83240004e7/.env.template>

Or with the latest testing image based upon the main branch contains single org option [feature: Support single organization policy by domdomegg · Pull Request #1991 · dani-garcia/vaultwarden · GitHub](https://github.com/dani-garcia/vaultwarden/pull/1991) (though, maybe not yet fully visible within the web-vault - [Stop hiding single organization policy by domdomegg · Pull Request #50 · dani-garcia/bw\_web\_builds · GitHub](https://github.com/dani-garcia/bw_web_builds/pull/50) )

---

<div class="post-metadata">

### Author: ![JPZone](https://avatars.discourse-cdn.com/v4/letter/j/8c91f0/32.png) [@JPZone](https://vaultwarden.discourse.group/u/JPZone)
#### Post date: [October 12, 2021, 7:20pm UTC](https://vaultwarden.discourse.group/t/remove-new-organisation/1185/3 "2021-10-12T19:20:38Z")

</div>

> [@BlackDex](#):
>
> Create a list of users who are allowed to create orgs

Yeah, that’s what I want to have a list of users who can create an organisations.  
I’m not very code savvy how can i implement this?

---

<div class="post-metadata">

### Author: ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)
#### Post date: [October 12, 2021, 8:16pm UTC](https://vaultwarden.discourse.group/t/remove-new-organisation/1185/4 "2021-10-12T20:16:15Z")

</div>

How are you deploying Vaultwarden? If you use docker or docker-compose you can set the environment variable

```auto
ORG_CREATION_USERS=admin1@example.com,admin2@example.com

```

As described in

> <https://github.com/dani-garcia/vaultwarden/blob/44da9e6ca7b42fa6c02bc5e80e9dda83240004e7/.env.template#L189>

If you have the [admin page enabled](https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page) with the environment variable

```auto
ADMIN_TOKEN=some_random_token_as_per_above_explanation

```

You can also set the list of users allowed to create organizations in the admin page with a comma separated list of emails, and save the config within the admin page.
