PedroM
1
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://canada1.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!
That issue was fixed in use a custom plan of enterprise tier to fix limits by stefan0xC · Pull Request #4726 · dani-garcia/vaultwarden · GitHub (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.
PedroM
3
Thanks for the update!
I got a way to work around it by creating different vaults for each team, instead of collections.