This post is going to cover some ideas around setting up users with read-only access in Dev for a Scoped Application. By read-only, we want them to have visibility to the platform but not make any changes to configuration within the scoped app. We're going to use the snc_read_only role of which there's lots of information available in Docs and Support.
What are the use cases for this? This was set up as we wanted to test the system for:
- Code reviews for story validation without making accidental changes
- Support of the development process by architects or project leads
- Training of new developers
So how to set something like this up? To start, I created a new scoped application that we would want to have the ability to lock down to a set group of people during development.
Next create a group. I chose to add a parent group and then include child groups to hold roles and users.
Then, within Studio I added these groups as Collaborators to my scoped application and set them up with Editor level permissions.
Finally, I updated my child groups by making sure all the roles associated with delegated development were present and then added the snc_ready_only role to the read-only group.
This set up could allow us to provide a pool of users a look at what's going in during the development phase of the scoped application without allowing them to make any changes.
