I’ve seen many times in my experience where a user tries to logon to their account into Tulip and they feel they know what their Badge ID is but they cannot get in because the Badge ID entry requirements are case sensitive.
I’m sure there is a rational reason for this as many organizations could need to prioritize case specific entries on Badge ID entry. However, often I have users trying to log on with something like “user01” but because of how their Badge ID is attached to their specific user ID it’s set at something like “USER01” or worse it could be “UsEr01”. So now the user needs to remember the specific case sizing for their Badge ID.
For our specific instance we often pull in Badge ID automatically thorugh SAML. This takes in the inherted user ID and stores it as a Badge ID in UPPERCASE format. So, for us I often have users who are adapted to not having to enter uppercase for every other system they log onto (again they would enter “user01” everywhere) then they come to Tulip and are forced to remember to enter “USER01”
I’m not certain on the specific solution here, but it seems some combination of account configurations, fuzzy searching on the badge entry on tulip’s side, and right sizing the case entries of Badge IDs.