Page Level Security - Power BI

Problem :
Developer can't natively set Page Level Security to the report pages/visuals unlike RLS, unless they do a work-around, which may take significant amount of time to build. Also, it may not be very reliable way to build this solution.

Temporary Solution (work-around) :
1. Hide the pages and provide navigation buttons (relatively simple and less development effort).

2. Creating seperate reports for different level users (secured but more development effort).

3. App Audiences but requires Pro license for the developer to group the audience (limited license issues) 

4. User access matrix, using RLS, navigation buttons, DAX access logic (security gap, if users somehow get to know the url etc. and reuqires high maintenance)

Permanent Solution :

Upgrade Object Level Security - As Microsoft supports OLS (Columns, Tables, DAX measures), adding another layer of Pages with it's MetaData can be really helpful. So, whenever a particular users lands on the landing page, with the OLS defined already the required pages only will be visible to the user.

Just we combine the meta data for, Power BI Service + AD Security Groups + Page Metadata, with this when a user logins and authenticates themselves the security will check the permissions and allow them and show the necessary pages which is defined by the developer by the relation/model they have set.

Benefits :

1. No complex workarounds.
2. More reliable solution.
3. Less development effort.
4. Saves Manhours.
5. Increases efficiency.