You’d need to update the user in such a way that marks them as “inactive” in the Docebo platform. Using your analogy, if all Acme users need to be deactivated in Docebo we need to update their Docebo “Active” field or update the users’ expiration dates.

There should be some rule or logic or formula in place that marks Acme corporation as retired in your Salesforce. Utilize this as a trigger to update Acme user fields being mapping to Docebo users in the Salesforce|Docebo application. Let’s say Acme gets retired and then all contacts under Acme get an expiration date inline with the overall Acme retired date. As-long-as the expiration field at the contact-level is mapped to a Docebo user’s expiration date, the “retired” date of all Acme users will be the same date as the Docebo’s user’s expiration date.

Edit: I see you mentioned a use case where an external employee leaves, but the company is still active. You’ll need to discover a similar “triggering event” to see where the process starts in your Salesforce. What action in Salesforce updates a contact to be “inactive” with their company? The solution here is the same as the one above. The Docebo user profile will need to be updated with an expiration date or a value the Docebo “Active” field accepts. If you’d like to learn more about default Docebo fields, here’s an article: https://help.docebo.com/hc/en-us/articles/360020128839-Importing-and-managing-users-via-CSV-files. You can also reference the batch user import endpoint in Docebo’s API for user field information.