Scheduled reports for Power Users contain incomplete data

​@Jon Hi, Jon.  One way that you could manage this situation is to require users to log into Docebo in order to receive their reports. This does actually provide some additional benefits, such as security of your data. 

Haven't seen this on reports but then we usually require that the PU be logged in to download the reports so that may be the reason why.

We did see something similar where a PU creates a user, adds them to a branch but the 2nd admin with the same access to the same branch cannot see the newly added user. We are opening a ticket so once I know more, I can   post back here.

Thank you for the idea ​@KMallette. We’ve tested this today by requiring Power Users to log in to download the scheduled reports. Unfortunately it doesn’t fix the issue as the report is actually run before the Power User logs in to download it, so it is incomplete.

After further testing, we’ve also found that this problem applies to users who use self-registration. That is...the Power User needs to log in after a user has been added to a branch they manage via self-registration in order to include data related to the user in a scheduled report.

I wonder how widespread this issue is, as I haven’t seen any other related conversations, and Docebo support are saying this is expected behavior (but can’t pinpoint which update caused this behavior change). 

Thanks ​@lrnlab. As explained above, requiring login for scheduled reports hasn’t helped.

Its possible the issue you’ve described is related. Let me know what you hear back. Thanks!

will do ​@Jon 

After further investigation, the issue occurs as follows:

• In Power User management, a Power User is assigned a parent branch with ‘decedents’ selected, and there is a sub-branch
• A Super Admin or other Power User creates a user account in the sub-branch, or a user self-registers in the sub-branch
• The Power User does not log into the system.
• Any scheduled report that the Power User receives will be missing this new user account. The issue is only resolved when the Power User logs in and a new report is generated.

The response from Support is:

“After further analysis, we confirmed that the In case of indirect resource assignments (e.g., a user being added to a group to which the Power User is already assigned), the Power User is not automatically logged out, but they will see their updated rights only after their next login, is related to a true log-in and the imporsonification will not update all the resources. We are going to update the Knowledge base, adding the details of the personification.”

This seems crazy to me, as this system change makes scheduled reports useless. The only way for a Power User to guarantee accurate report data is to log in and run a report manually.

Thx ​@Jon certainly sounds like the same type of issue we see with Groups ownership transfer. I am trying to escalate the groups issue since support says it’s working as designed. If I’m able to get the product owner’s attention, I’ll also note this report behaviour and she your results.

​@Jon that doesn't make much sense to me either.

​@lrnlab Here’s the full write-up in case its useful:

1. Scheduled Reports & Self-Registrations

Scheduled reports for Power Users are generated based on the branch and user permissions available at the time of report generation—not on real-time recalculations. While self-registrations and manual branch assignments both correctly trigger enrollments, those enrollments may not appear in scheduled reports if the branch permissions rely on dynamic propagation.
 
Importantly, Power Users do not need to log in for reports to update. However, when branch access is granted using 'Descendants = Yes', there can be delays or propagation issues, causing some enrollments (especially from newly added or self-enrolled users) to be missed in scheduled reports.
👉 Power User Permissions Overview
 
 

2. 'Descendants = Yes' vs. Manual Branch Assignment

Using 'Descendants = Yes' allows automatic access to current and future sub-branches, but in scheduled jobs, this dynamic permission model can sometimes fail to capture the latest user/enrollment data.
In contrast, manually assigning each relevant branch ensures a fixed, reliable list of accessible branches, so all enrollments are accurately pulled into scheduled reports.
👉 Organising Users with Branches
👉 Managing Power Users
 
I summarised this as a chart, please see below: 
 
 

 
Source:  Creating Custom Reports
 
 
 

To recap: 
 

While it’s not intended behaviour for scheduled reports to exclude enrollments due to 'Descendants = Yes', this is a known limitation stemming from how the platform dynamically calculates permissions for automated tasks.
 
Recommendation: For reliable, complete scheduled reporting, we strongly suggest manually assigning all relevant branches to Power Users, especially in scenarios involving self-enrollment or frequent user movements.
 

Thanks for the extra detail. Much appreciated