you are right Lisa, I think that settings permissions shouldn't be mandatory to view organizations. I'll create a ticket in the Organizations project to see if they can be separated.

Hi!

I retested this after the Edelweiss upgrade. The issue partly remains.

Assigned the following permissions to a user:

Log in as the user, get the following error message when opening Organizations:

I noticed that when you tried to reproduce the error, you had assigned your user a permission that - as you can see from the original ticket description and from my comment above - my user does not have.

Adding it solves the problem of the error message in the Chalmers tenant as well.

I'll close this issue as Done since all the permissions needed now seem to be visible (and thus easy to add), but with the caveat that I do not see why - and suspect it might bother libraries - that a user should need to permissions to edit the Organizations settings to see Organizations.

I couldn't reproduce it on bugfest 3.1, which is running same versions as Chalmers, Can we check if this can be reproduced on Chalmers?
I added a user with 3 Organization permissions from the screen shot

was able to access orgs app without any issue

Yes, thanks! I'll clone this as well so we can troubleshoot it.

you are the PO of Organizations, right? There seems to be a couple of permissions missing in the sets.