Skip to main content

Hello,

I’m looking for guidance concerning a quirk when uploading users via a csv file. When a user’s Active Status changes from 1 (Active) to 0 (Inactive) on our csv feed, the user is expired in the system vs being deactivated. Docebo generates a date in the Expiration field in the General Information tab. When Deactivating users as an admin by clicking off their green check mark, this does not occur. The issue is that when an employee comes back to work for us and their email is reactivated, even though the Active column on the csv shows a 1 for active, Docebo does not reactivate them. The expiration date prevents that. Chat support said that we had to manually remove the expiration date in order for the employee to be reactivated, and that works. But I can’t help that think there is a better way for this, like a setting I can’t find somewhere. People are rehired by companies constantly and we have no communication with any of the teams that handle hires and their email creds. Please tell me it’s a setting somewhere that I’m missing.

I totally understand...we stopped using the Expire option for just that reason...except where we know the account will not be used again.

I did notice an “Expire on” field in the CSV upload...Not sure if you left it blank whether it would blank out that field but if it does not, you could set it far in the future, like 2999-12-31 and that would allow you users to get back in without you having to remove it manually for each user...


Hello,

How did you stop using the Expire option? To me it just seems like something Docebo does in the background since the Active field is a binary 1 or 0. We do have the Expire On field blank in our csv upload, so sadly that won’t stop it from occurring.


We do not have it in our CSV uploads and it never adds it automatically...Are you perhaps using the Automation app to expire users? 


Hi. No I have no automation rules set. And although we have a column for Expire On in our CSV, there is no value mapped to it. I would then think mapping the field with a blank value might override what Docebo puts there when an inactivation is triggered, but if you don’t even have the field and it never occurs upon your inactivations, that would seem to disprove the theory.


Read thru this

https://help.docebo.com/hc/en-us/articles/20923512163602-User-account-statuses

but there is no mention that an expire date is /would be added to user profile that you inactivate (0/1)...They are completely different things...There must be something in your processes that is setting this date. Otherwise I would treat this as a bug and open a ticket with support. I have never seen the behaviour you describe.


Thanks. I did open a support ticket so we’ll see what advice I get.


Would love to hear their response...😉


Hello,

We did solve this mystery. After speaking with tech support and researching the Expiration dates it turned out, as always, that the issue was on our end. Earlier this year, we stopped using Docebo Connect to provision users. The API was expiring users, whereas the csv feed just deactivates them. Expired users could not be unexpired without manually deleting the expiration date, so the csv feed could not make them active again. 


Thanks for posting the update...


Reply