The report displays data for the developer but remains blank for other users.

Building on Sameburn's point — the POV is exactly where to look, and this isn't a security issue.

In the Cube View POV most of your dimensions are left empty. When a dimension isn't set on the Cube View POV (or pinned on the rows/columns), it falls back to each user's Cube POV — and that's different from one user to the next. So the report resolves against your Cube POV and returns data for you, but lands on a different intersection with no data for everyone else.

Quick way to confirm: have another user set their Cube POV to exactly match yours, then open the report. If the data shows up, that's the cause.

To fix it for everyone, fill in the Cube View POV dimensions with explicit default members instead of leaving them to inherit each user's Cube POV. Once the dimensions resolve to the same members for any user, it'll populate consistently.

If that still doesn't do it, it'd help to see the setup of the parameters and the XFBR rule from your screenshots.