As an org admin, assigning myself (or other admin) to a collection results in an error #80

New Issue

GiteaMirror · 2025-11-07T06:21:47-06:00

GiteaMirror commented

2025-11-07 06:21:47 -06:00

Originally created by @janost on GitHub (Aug 30, 2018).

Reproduction steps:

Using the latest docker container.
Log in to the web UI as user who is an organization admin.
Select organization, click on the Manage tab, select People.
Click on yourself or another organization admin.
Under "Access Control" assign the user to any collection or select "This user can access and modify all items".
Click "Save".

Expected result:
The request succeeds and the edited user gains access to the selected collections.

Actual result:
Red error message pops up saying "Only Owners can grant Admin or Owner type".

Background:
Failing request is:
PUT https:///api/organizations/<ORG_ID>/users/<USER_ID>

Originally created by @janost on GitHub (Aug 30, 2018). Reproduction steps: - Using the latest docker container. - Log in to the web UI as user who is an organization admin. - Select organization, click on the Manage tab, select People. - Click on yourself or another organization admin. - Under "Access Control" assign the user to any collection or select "This user can access and modify all items". - Click "Save". Expected result: The request succeeds and the edited user gains access to the selected collections. Actual result: Red error message pops up saying "Only Owners can grant Admin or Owner type". Background: Failing request is: PUT https://<HOSTNAME>/api/organizations/<ORG_ID>/users/<USER_ID>

GiteaMirror added the bug label 2025-11-07 06:21:47 -06:00

GiteaMirror closed this issue

2025-11-07 06:21:48 -06:00

GiteaMirror commented

2025-11-07 06:21:48 -06:00

@mprasil commented on GitHub (Aug 30, 2018):

Thanks for reporting this. Have you tested this in upstream to see how that works there? I'm not sure how to handle this as granting admin ability to edit himself and other admins essentially gives him owner-level privileges.

@mprasil commented on GitHub (Aug 30, 2018): Thanks for reporting this. Have you tested this in upstream to see how that works there? I'm not sure how to handle this as granting admin ability to edit himself and other admins essentially gives him owner-level privileges.

GiteaMirror commented

2025-11-07 06:21:48 -06:00

@janost commented on GitHub (Aug 30, 2018):

I just tested this upstream.
As an organization admin, I was able to edit my own access to collections using the procedure I described in the issue. Unfortunately I can't test if I can edit other admins, because I only have a free account on upstream.

@janost commented on GitHub (Aug 30, 2018): I just tested this upstream. As an organization admin, I was able to edit my own access to collections using the procedure I described in the issue. Unfortunately I can't test if I can edit other admins, because I only have a free account on upstream.

GiteaMirror commented

2025-11-07 06:21:49 -06:00

@mprasil commented on GitHub (Aug 30, 2018):

Thanks for that. I guess it's safe to assume, that it would work for other admin accounts.

@mprasil commented on GitHub (Aug 30, 2018): Thanks for that. I guess it's safe to assume, that it would work for other admin accounts.

GiteaMirror commented

2025-11-07 06:21:49 -06:00

@mprasil commented on GitHub (Sep 4, 2018):

Submitted PR #170 that should also resolve this issue.

@mprasil commented on GitHub (Sep 4, 2018): Submitted PR #170 that should also resolve this issue.

GiteaMirror referenced this issue

2025-11-07 07:44:26 -06:00