how many times can you spot the letter i in:
q: best practice: how to restrict access to communities in sandbox environments? we have this scenario: we have multiple sandbox environments that are used to develop and customize communities. some communities include a public section.
some of these sandbox communities are functionally equal to production (incl. self-registration, etc.) and used by our business users for functional, ux or uat testing.
we used to restrict access to these sandbox communities via ip ranges, limited to various company/service provider ip ranges.
however during the current corona pandemic most people switched to working from home. many of these people (especially from smaller companies) do not work in the sandboxes using a company vpn connection but using their personal internet provider. this needs to be possible in the future too.
unfortunately this removes the ip criterium as an option to restrict access to the sandbox communities.
so, my question is: how do others handle this? can you point me into some directions?
what ive considered so far but all determined as not workable:

*

*disable self-registration in some environments to at least protect the non-public parts

*set all pages to non-public (in combination with item 1)

*disable community during adaption and re-enable when testing


user
The total number of "i"s in that passage is ninety.
assistant