I’m experiencing an issue where dashboards shared with user groups are no longer appearing for users added to those groups.
Previously:
When a user was added to a user group, they could immediately view all dashboards shared with that group.
Current issue:
New users added to existing user groups cannot see the dashboards that are shared with those groups.
My hypothesis:
I suspect there might be a delay or issue in internal DHIS2 processes related to propagating dashboard sharing permissions via user groups. This seems to be affecting visibility inconsistently.
Steps I’ve taken so far:
Shared a dashboard with a test user group. Dashboards did not appear for users in that group.
Shared all user groups with my own account. Dashboards didn’t display until a few hours later.
Tried resharing the dashboards with the test group. Still no visibility.
Removed all user groups from my account. I could still see all dashboards.
I plan to recheck visibility after the weekend to see if delays in permission propagation are indeed the cause.
Has anyone experienced similar behavior with dashboards and user groups? Could this be a caching issue or something to do with the DHIS2 version we’re using?
I’d emphasize the point (Make sure that the cache is cleaned before the user accesses the dashboard: (1. Data Administration - Maintenance - reload apps, clear application cache, 2. Cache cleaner, 3. Clear Browser Data).)
I hope that works. If the issue persists, could you get more info as mentioned here.
Thanks Gassim!
I truly believe the issue might be cache. tried clearing app cache and reloading the apps from maintenance no improvements.
I noticed that the changes made by adding/removing user groups works, just very slowly, a few hours I believe. We can live with this for now but not very sustainable
Also recreation might be difficult in play given the huge volume of UGs present in our instances.
Okay, thanks for marking the solution and sharing what is happening in your instance. Sorry to hear that there’s still an issue.
If we could reproduce the issue with at least only one or two UGs, it would be very helpful. The point is to create an environment where this can be tested and triaged to the developers.