I am working on a project and I need to create a new Homepage. There are restrictions. For example, the new Homepage uses Profile A. Those in Profile A has roles AA, AB, and AC. The users with AA or AB roles can view the new Homepage. Users with AC still view the old homepage.
How can this be done?
I would prefer to use the old Homepage and its "Set Component Visibility" features based on Roles but my manager wants a new Homepage.
My manager also do not want a new profile just for the users with AC role due to Profile A having many features implemented for it.
With these requirements, I was thinking if it was possible to embed the old Homepage into a Visualforce or Aura Component in the new Homepage then render it if user has AC role. That or when user logs into new Homepage, a method will call and redirect to old Homepage if user has AC role. But I have not found if this was feasible.
Does anyone have any ideas how I can implement a new Homepage while preventing a user with a specific role from view new homepage so they can view the old?
