I was able to replicate this. However, when I logged in as Super Admin I was able to see the certificate created by PU. But PU cannot see the certificate in the certificate page. Strange! Look like it’s a bug.

Yes, you are right. We noticed the newly created certificate by the PU was displayed in Super Admin page but not in PU itself.

We have created a ticket but just want to check in here to see maybe there is a reason why Docebo has this feature in PU profile.

Will wait for Helpdesk response and update here.

Thanks @Chelsy Koshy. 

@haziehalim we had an issue with certificate visibility with a power user.  We were able to get the Power User to see the certificate as long as they were enrolled and marked as completed on a course that had the certificate assigned.

I know it is an extra annoying step, but I wonder if you create a course shell with that power user’s certificate, and enroll the PU, then mark them as Complete if the PU will be able to see the certificate they created?

Most definitely a bug issue.  Hopefully the work around helps!

Hi both,

Just received words from Helpdesk. Apparently this is an expected behavior for PUs when creating new certificate. They can create new certificate but they can’t view it. After creation, the certificate template will only be visible to Superadmins first. And if the superadmin associate the certificate to a course and this course is assigned to the PU, then only the PU would be able to see the certificate he created.

TBH, I don’t see the value in having the permission to create new certificate but not allowed to view it. Surely i want to see how the cert looks like before my superadmin assign it to courses. maybe making some adjustments first before giving it a greenlight?

This confused me and a PU this morning! Many thanks for this thread, it works but it such a weird work around!! 

I actually think this is tied to that permission for “View only the certificate issue for their assigned courses and learning plans”. If you take that off, it allows them to create (which I’m guessing is through the Edit permission) and successfully create a new certificate template, build it out and then apply it to courses.

An issue we are having here is that there does seem to be a glitch (which probably doesn’t apply to most people) but power users can see the certificate templates other power users outside of their branch create as well. We use the system where branches are actually different companies, so this is an issue for us. But, again - likely not an issue for others. 

@amanda.champion We actually have similar use case - we have Power Users from different organizations, and we are trying to reflect on the values and downsides of allowing PUs to create certificate templates.

This is what I figured out so far in terms of the process and here is a sample use case: so we grant the PU1 All permissions for Certificates, then PU1 creates a Certificate template then notifies the Superadmin since they can’t view and edit it after they created it. So Superadmin goes to assign the Certificate to the courses that PU1 wanted to attach the Certificate to and assign those courses to PU1. After these steps, PU1 can go view and edit the Certificate and also have the option to attach the Certificate to a Learning Plan. (If the other PUs are not assigned to those courses, then they shouldn’t be able to see the Certificate PU1 created?)

I want to know if this is the right process and if there’s better process and I appreciate if anyone can share their experiences or views of the values and/or downsides of allowing PUs to create Certificate templates, or will it be less confusing to just have Superadmins to create the Certificates? Thanks

@amanda.champion I’m resurfacing this since I just encountered the same issue. It seems that in this case using the All Permissions options is actually more restrictive than using Custom Permissions and choosing only “Edit” and “View” and excluding “View only the certificates issued for their assigned courses and learning plans”. It seems counterintuitive to me that assigning fewer permissions gives a user more control. I presumed that conflicting permissions would grant the user the higher level of permission, rather than the lower level. I think that this is what you found as well, right?