An option would be helpful for embedded content (layers included in maps, for example) to toggle between the existing behavior of requiring a user to log in whenever content is beyond the user's current access level, and a way of simply "ignoring" any content that does not match that user's access level.
Example ideal workflow:
An application exists, using a web map containing layers with multiple levels of sharing enabled. Some layers are acceptable for public sharing and some are restricted to the organization and/or group level. Enable a proposed option to ignore content for which the user does not have access and continue to load the application. The advantage is to be able to serve a single app and web map for multiple types of users; without having to expand maintenance complexity for the application where the theme remains constant.
For our specific workflow, this could be simplified to ignore all content that requires a login (not set to "public"). However, I imagine others might want to additionally leverage groups as a part of their strategy which is why I described it more broadly as the 'user not having the required access.'
Current (not ideal) workflow:
Create two web maps, one containing only public layers and another for privileged access. Create two Instant apps, one for each web map. Maintain all duplicate content in parallel.
