This issue was resolved after updating to Discourse version 2.9.0.beta4. Not sure why, but glad it is now working for our staff member.
This issue was resolved after updating to Discourse version 2.9.0.beta4. Not sure why, but glad it is now working for our staff member.