Yes, I usually put guards in Core Module too, under a separated /guards folder :) I see guards as “app-scoped puppeteers” so I wouldn’t confine them in a View Module, the only reason to do so is that you’re sure that those guards will be only tied to that specific module, but it never was the case for me. I’ve always worked with guards such as “is he logged in”, “has his subscription expired”, “is he an administrator” etc, app-scoped guards which could be reused here and there in the future!