# Vault collection limit

**URL:** <https://vaultwarden.discourse.group/t/vault-collection-limit/3832>\
**Category:** Help\
**Created:** [July 19, 2024, 3:15pm UTC](https://vaultwarden.discourse.group/t/vault-collection-limit/3832 "2024-07-19T15:15:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![PedroM](https://avatars.discourse-cdn.com/v4/letter/p/a87d85/32.png) [@PedroM](https://vaultwarden.discourse.group/u/PedroM)\
**Post date:** [July 19, 2024, 3:15pm UTC](https://vaultwarden.discourse.group/t/vault-collection-limit/3832/1 "2024-07-19T15:15:57Z")

</div>

Hi everyone,

I’m setting up a local instance of Vaultwarden and I want to create a series of collections, to separate users.  
However, I’m finding this problem:

![Screenshot 2024-07-19 at 16.14.16](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/2/2efcdcd728b6207384e59b25f3ab2f97160d872c.png)

From my understanding, this should not be limited in Vaultwarden, from what I could find. Is this correct?

Thanks!

---

<div class="post-metadata">

**Author:** ![stefan0xC](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/stefan0xc/32/1765_2.png) [@stefan0xC](https://vaultwarden.discourse.group/u/stefan0xC)\
**Post date:** [July 19, 2024, 3:44pm UTC](https://vaultwarden.discourse.group/t/vault-collection-limit/3832/2 "2024-07-19T15:44:35Z")

</div>

That issue was fixed in [use a custom plan of enterprise tier to fix limits by stefan0xC · Pull Request #4726 · dani-garcia/vaultwarden · GitHub](https://github.com/dani-garcia/vaultwarden/pull/4726) (which is available in the `testing` image and should be in the next release). Unlike the invitation limitation I’m not sure there’s an easy workaround if you rather decide to wait for the next release.

---

<div class="post-metadata">

**Author:** ![PedroM](https://avatars.discourse-cdn.com/v4/letter/p/a87d85/32.png) [@PedroM](https://vaultwarden.discourse.group/u/PedroM)\
**Post date:** [July 23, 2024, 10:37am UTC](https://vaultwarden.discourse.group/t/vault-collection-limit/3832/3 "2024-07-23T10:37:46Z")

</div>

Thanks for the update!  
I got a way to work around it by creating different vaults for each team, instead of collections.