Corpora databases can be started without then being given permission to those same corpora

[MichaelGoodale]

Right now, even if here is a corpus running, the corpora dropdown does not show anything on Firefox, using the Docker install. Directly typing in the corpora URL still works however.

[MichaelGoodale]

Hmm, okay this might have just been a cacheing error on my part. It seems to be fixed after rebuilding the docker image and refreshing my firefox cache

[MichaelGoodale]

Nevermind! its a real issue, on roquefort, currently the SOTC corpora is not listed despite the database being running. It may be some sort of issue with how the corpora dropdown is saved or something

[MichaelGoodale]

So the issue just has to do with permission, for some reason when making the new database, despite being able to start and stop it, I wasn't able to have permission to the corpus using the Morgan account.

@mmcauliffe What's the intended behaviour here?

[mmcauliffe]

Ok right, so this is actually intended behavior, but needs to be documented better. So the update to the permissions issue has users by default as "Guest" which means they don't have access to any corpora that are "Restricted" and by default, all corpora are Restricted. However, the morgan account is marked as a superuser, which gives allows them to start/stop all databases, even if they don't have access to the corpora.

Maybe it makes more sense to bundle the unlimited database access with "Unlimited researcher" role, rather than the superuser role? Or have an additional "Admin" role that removes the need for any superuser checking (currently superuser allows database access and to change user permissions/add/delete users)?

[msonderegger]

@mmcauliffe Given time constraints I think we'll just have to leave the system as is, but this issue should be noted where the roles are described. Are the roles/the whole permissions system documented?