# Sort vault list

**URL:** <https://vaultwarden.discourse.group/t/sort-vault-list/2534>\
**Category:** Feature Requests\
**Created:** [March 28, 2023, 7:42pm UTC](https://vaultwarden.discourse.group/t/sort-vault-list/2534 "2023-03-28T19:42:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexgeraweb](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@alexgeraweb](https://vaultwarden.discourse.group/u/alexgeraweb)\
**Post date:** [March 28, 2023, 7:42pm UTC](https://vaultwarden.discourse.group/t/sort-vault-list/2534/1 "2023-03-28T19:42:33Z")

</div>

On the Vaultwarden main page, all vaults are displayed on the left side. If you work with a lot of organizations and vaults like we do, it becomes very confusing, because the vault list is not sorted.  
It would be nice to have a sorting option A-Z. Your own vault can still be displayed at the top.

 ![Tresore](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/2X/f/f63caca4166b3d97a0a2d36c0d8ca20b300a74f2.png)

---

<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:** [March 28, 2023, 7:50pm UTC](https://vaultwarden.discourse.group/t/sort-vault-list/2534/2 "2023-03-28T19:50:33Z")

</div>

See the [comment](https://vaultwarden.discourse.group/t/organization-woes-with-bitwarden-browser-extensions/2528/4) made by @BlackDex in another post

> [@Organization Woes with Bitwarden Browser Extensions](https://vaultwarden.discourse.group/t/organization-woes-with-bitwarden-browser-extensions/2528/4):
>
> See here [Wrong vault sorting · dani-garcia/vaultwarden · Discussion #3005 · GitHub](https://github.com/dani-garcia/vaultwarden/discussions/3005)
> 
> And here for Upstream [Organization sort order is not alphabetical · Issue #4263 · bitwarden/clients · GitHub](https://github.com/bitwarden/clients/issues/4263)
> 
> Where we already mentioned it still is broken.  
> But it probably doesn’t hurt to bump it again.

As mentioned, this is an already reported upstream issue.
