User with Manager role gets "401 Unauthorized" when accessing Organization Manage tab #4833

New Issue

GiteaMirror · 2026-03-07T20:02:55-06:00

GiteaMirror commented

2026-03-07 20:02:55 -06:00

Originally created by @Dimonina on GitHub (Jan 11, 2022).

Subject of the issue

The manager role does not to seem work well. As a manager, I can't manage Organization's collections.

Deployment environment

vaultwarden version: 1.23.1
Install method: docker
Clients used: web
Reverse proxy and version: no proxy

Steps to reproduce

Create first admin user "admin@test.com"
Create an organization under this user, e.g. "MyOrg"
Create a couple of collections "Col1", "Col2", "Col2/Col2-1"
Create a new user "manager@test.com"
Assign a manager role to manager@test.com under admin user and give rights to "Col2", "Col2/Col2-1" collection.
Under manager@test.com using web interface go to organization and click "Manage" tab.

Expected behaviour

User can see a page with an ability to manage collections

Actual behaviour

User is logged out

Originally created by @Dimonina on GitHub (Jan 11, 2022).   ### Subject of the issue The manager role does not to seem work well. As a manager, I can't manage Organization's collections. ### Deployment environment * vaultwarden version: 1.23.1 * Install method: docker * Clients used: web * Reverse proxy and version: no proxy ### Steps to reproduce 1. Create first admin user "admin@test.com" 2. Create an organization under this user, e.g. "MyOrg" 3. Create a couple of collections "Col1", "Col2", "Col2/Col2-1" 4. Create a new user "manager@test.com" 5. Assign a manager role to manager@test.com under admin user and give rights to "Col2", "Col2/Col2-1" collection. 6. Under manager@test.com using web interface go to organization and click "Manage" tab. ### Expected behaviour User can see a page with an ability to manage collections ### Actual behaviour User is logged out

GiteaMirror closed this issue

2026-03-07 20:02:55 -06:00

GiteaMirror commented

2026-03-07 20:02:56 -06:00

@BlackDex commented on GitHub (Jan 11, 2022):

Duplicate of #2151
And already fixed in #2169

@BlackDex commented on GitHub (Jan 11, 2022): Duplicate of #2151 And already fixed in #2169

GiteaMirror commented

2026-03-07 20:02:56 -06:00

@Dimonina commented on GitHub (Jan 11, 2022):

Duplicate of #2151 And already fixed in #2169

Mmm. If it is fixed, then why I can reproduce it in the latest container version?

@Dimonina commented on GitHub (Jan 11, 2022): > Duplicate of #2151 And already fixed in #2169 Mmm. If it is fixed, then why I can reproduce it in the latest container version?

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#4833