Additional info: It looks like with our initial SYNC with GoogleSSO, suspended users did not come over. However, if a user was in the database in IQ and suspended after, they remain in IQ with their asset history.

@DNatalie 730c952 pasd Thank you for submitting your question to our community!

I am going to have your implementation specialist follow up with you to double-check this, but what is your suspended users mapped to? Are they set to have no access? 

Correct. They are set to no access.

@DNatalie 730c952 pasd I suggest adjusting the status of these users to bring them into iiQ. After they are imported, bulk assigns these users no access. Once they are imported, they should still have the asset record attached to them, and once they change to no access, the asset history will be kept on the user profile. I hope this helps 

Hi @DNatalie 730c952 pasd Kathryn is correct that you cannot bulk assign devices to users who are “guests” or in the role of “no access”. Please note that if they are assigned a device as a faculty/staff and they move to no access they will retain their asset assignment. We just don’t assign any new ones to those people. I would suggest turning off the feature in the SSO to “set to ‘no access’”. I would then make sure the suspended OU is syncing to either faculty/staff. This will allow you to make that asset assignment. Then you can put them in whatever role they belong. Hope this helps!

 @Kathryn Carter 

Thank you for your response. I want to make sure I understand. It sounds like Kathryn is suggesting on the google side to change their status, bring them into IQ, and then change their status back. We definitely need to continue to have the ability to suspend users in Google.

@arosenbaum_iiQ I tried those steps and it is still not bringing in currently-suspended users from google.

Going into the “User history” inside managing the GoogleSSO app, I can find suspended users, and IQ skipped importing them because Suspended in google reads as “disabled” in IQ.

I don’t think this is something that needs to be fixed necessarily. But it’s useful to know that on an initial import for new IQ organizations, if we’re relying solely on google SSO, currently-suspended users will not be pulled in.

I am doing a CSV import of my suspended users. I really love that I can custom-add field mappings, and even slap it within the “GoogleSSO” category within the users! e.g. “last login date.”

Sorry, I will add the screenshot of what I saw with the skipped users:

@DNatalie 730c952 pasd I am going to let your implementation specialist work with you on this until y’all have gone live.  I have reached out and they will be following up.

We were able to remedy this by temporarily changing some of the “No Access” and disabled users to student or staff/faculty. We then could bulk assign the assets and move the users correctly back to “No Access”. This way the disabled users will retain the asset assignment until they are reassigned to someone else.

Thank you for following up @arosenbaum_iiQ I have updated the Best Answer for this question