We have a power user profile that we use to purchase courses on behalf of other users when they are using a PO. (Long story short, we use a coupon to enroll them).
This power user profile has been assigned a branch and all descendants of this branch as a resource because, we want all of the users in this branch (regardless of when the profile was added, and who created it) to be visible to the power when purchasing a course for a user.
Well we ran into an issue where the power user could not purchase a course for any users who were recently created in that branch (they got an error message saying the user didn’t exist). I thought a Branch was a dynamic resource, so if it was assigned to a power user, they would be able to see all profiles that are added to that branch. Am I incorrect in this thought process? Or has there been a change to how the Branch resource works?
Question about assigning a branch to a PU as a resource
+7
+10I am under the same assumption. Any user appearing in the branch that is active should automatically be available to the PU when they have visibility to the branch the user resides in. Are the users active? No expiry date, etc.
+7Yep! All the users were active and were not expired.
The interesting part is the issue with not allowing to purchase on behalf of another user ended up getting resolved when I unassigned and reassigned the branch to the power user. Which is why it led me to question if I understood how the branch resource assignment worked.
+10Hmm, yes that is odd. I wonder if somehow it’s linked to another issue I saw with group ownership transfer? It’s a similar case where support is saying that the PU needed to login for a group they own to be updated. I wonder in your case, if the new users added to the branch are not being picked until the PU logs in - I under stand they would have to be logged to make the purchase but maybe this is related somehow. Support have advised the fix for the group issue was added today so maybe try it again to see if anything has improved. It’s a long shot but worth a try. Did you flag this to support?
Log in to Docebo Community
Enter your email address or username and password below to log in to Docebo Community. No account yet? Create an account
Docebo Employee Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.