I am not on the team but I have noticed this since 3.x.x versions. I never delete users. I unauthorized when they are to be retired. You will also find this holds true across child portals. This design seems to lean toward audit trail and user permanence. It does however generate management time in particular if you use child portals as I do. I may have one user hit fifteen child portals in the same DNN instance. When the user is to be retired, I have to unauthorized them in all portals they had access to. I also never delete child portals and do not reuse child portal names. This presents other issues. (Or at least it did in older revs)

This issue is back into DNN 6. I was able to manually add the user to a second portal by modifying the userportals table.

That makes more sense, looking through the database records I may have used their nickname instead of their full name. I thought it only went by the userID, but if any part of the criteria doesn't match, that would explain it. I didn't read through all 7 pages to see that. Thanks for responding.