starred/vaultwarden

Fork 0

mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-04-26 01:35:54 +03:00

[GH-ISSUE #5853] Owner see wrong access message in collection #2263

New issue

Closed

opened 2026-03-03 02:16:44 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:16:44 +03:00

Owner

Originally created by @p2-genetics6570 on GitHub (May 14, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5853

Vaultwarden Support String

Hey together,

I am writing to bring to your attention an issue we have encountered regarding the permissions display for organization owners within Vaultwarden collections on GitHub.

It appears that when organization owners view the permissions for collections, they are incorrectly shown as having "No Access." This seems to be a display error, as organization owners should inherently have access to all collections within their organization.

Could you please investigate this matter and let us know if there is a possibility of fixing this display issue? It would greatly enhance the user experience and ensure clarity in permissions management.

Thank you for your attention to this matter. I look forward to your response.

Best regards

Vaultwarden Build Version

1.33.2

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

apache

Host/Server Operating System

Linux

Operating System Version

Ubuntu Server 24

Clients

Web Vault

Client Version

No response

Steps To Reproduce

Create Admin in organization
Open your vault

Expected Result

Fullaccess has to be shown in collection

Actual Result

No access to view in collection, but access is working

Logs

Screenshots or Videos

No response

Additional Context

No response

Originally created by @p2-genetics6570 on GitHub (May 14, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5853 ### Vaultwarden Support String Hey together, I am writing to bring to your attention an issue we have encountered regarding the permissions display for organization owners within Vaultwarden collections on GitHub. It appears that when organization owners view the permissions for collections, they are incorrectly shown as having "No Access." This seems to be a display error, as organization owners should inherently have access to all collections within their organization. ![Image](https://github.com/user-attachments/assets/a5bc3d35-cec4-4bbe-add3-889e2c327d05) Could you please investigate this matter and let us know if there is a possibility of fixing this display issue? It would greatly enhance the user experience and ensure clarity in permissions management. Thank you for your attention to this matter. I look forward to your response. Best regards ### Vaultwarden Build Version 1.33.2 ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy apache ### Host/Server Operating System Linux ### Operating System Version Ubuntu Server 24 ### Clients Web Vault ### Client Version _No response_ ### Steps To Reproduce 1. Create Admin in organization 2. Open your vault ### Expected Result Fullaccess has to be shown in collection ### Actual Result No access to view in collection, but access is working ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_

kerem

2026-03-03 02:16:44 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 02:16:45 +03:00

Author

Owner

@BlackDex commented on GitHub (May 14, 2025):

This works as it should.
There is a PR in the works wich kinda solves displaying it a bit better.

It will show other access rights if a collection is specially assigned, though, Vaultwarden does not support that (yet).

Nothing we can currently do about this.

@BlackDex commented on GitHub (May 14, 2025): This works as it should. There is a PR in the works wich kinda solves displaying it a bit better. It will show other access rights if a collection is specially assigned, though, Vaultwarden does not support that (yet). Nothing we can currently do about this.