I have a Sitecore site that has a section of region pages. I need to create roles for sites that will allow a user to only see their assigned region in the shell. This role should not keep the user from being able to see other regions on the front end though. Is there a way to separate read access in the shell vs read access on the front end of the site? The site is going to be accessible to anonymous users. The goal of this is to allow a content editor that only has permission to edit a region to still be able to look at the front end of any other region on the site without needing to log out of the shell. I have discussed just not allowing write access to other regions however a requirement is that regions cannot see unpublished data another region has.

I have a Sitecore site that has a section of region pages. I need to create roles for sites that will allow a user to only see their assigned region in the shell. This role should not keep the user from being able to see other regions on the front end though. 

Is there a way to separate read access in the shell vs read access on the front end of the site? The site is going to be accessible to anonymous users. The goal of this is to allow a content editor that only has permission to edit a region to still be able to look at the front end of any other region on the site without needing to log out of the shell. I have discussed just not allowing write access to other regions however a requirement is that regions cannot see unpublished data another region has.

I have a Sitecore site that has a section of region pages. I need to create roles for sites that will allow a user to only see their assigned region in the shell. This role should not keep the user from being able to see other regions on the front end though. Is there a way to separate read access in the shell vs read access on the front end of the site?

I have a Sitecore site that has a section of region pages. I need to create roles for sites that will allow a user to only see their assigned region in the shell. This role should not keep the user from being able to see other regions on the front end though. Is there a way to separate read access in the shell vs read access on the front end of the site? The site is going to be accessible to anonymous users. The goal of this is to allow a content editor that only has permission to edit a region to still be able to look at the front end of any other region on the site without needing to log out of the shell. I have discussed just not allowing write access to other regions however a requirement is that regions cannot see unpublished data another region has.