Read-only permission set for back-office users
As both a training tool and for wider understanding of the primo product, we would like to have a read-only permission profile where heads of public service or others could look up configuration/normalization settings, but not commit permission changes. As it stands now, each permission set has the ability to write to at least one area of back office. We would like a 'do-no-harm' account that senior or technically abled library staff could review/suggest changes without having the ability to make the change.
Manu Schwendener commented