Automatically remove Paid Licenses from Removed or Deactivated Users + Mass Deactivate
HubSpot should remove paid seats from users if they are removed or deactivated. It make no sense to then lock that seat if the user was deactivated, meaning we would then have to reactivate, remove the paid seat, and then deactivate again.
To ensure an efficient setup with our IT dept. removing employees who leave the company, we are switching to Okta SCIM provisioning, and to do this effectively it would have to ensure the paid seat is removed at the same time or else there is zero time saved.
2ndly - please allow Deactivation to be done with multiple checkbox input instead of one user at a time.
+1. The paid licenses should be recalled for deactivated users. It's extremely manual and time-consuming to do that for each user. When deactivating user - just a check box (through a confirmation pop-up?) or a few checkboxes to remove their paid licenses, primary (and all secondary) team, and permission profile. (or licenses, team, or remove everything). Once checked and hit save, those steps can be done at the same time when they're being deactivated.
Yes. Yes. Yes. Deactivated should include at minimum the OPTION to immediately remove paid seat. It then being locked is just beyond frustrating. I know there is a warning, but honestly when removing team members, that's the last thing you want to have to think about.
Totally agree. Just ran into this. Seems a bit shady as other platforms I've used remove the seat upon deactivation. Learned the hard way on this and paid for a seat for months after the user's departure.
+1 I have to reactivate each deactivated user one by one, and that user will then recieve an invite to join. I then need to update their license and then deactivate again. When managing a large number of users, this becomes additional admin work and problematic in terms of reactivating a user who has left the team.
Recently installed the integration between Okta and HubSpot. We had our first round of deactivations and are experiencing this issue. The (obvious) thing here is that the Okta integration is designed to reduce admins' management of users in and out of multiple systems. With this integration, all we are doing is switching one admin set of processes for another set of processes for the same task.