At the last working day of my job, I heard that someone requested to extend my accounts to login to some application servers and to my mailbox as well, and the reason given was to support for some coming system upgrade. It sounds not a good reason as to get the access to servers, the normal way is to submit request and get the authorization. The IT policy usually does not allow using other people’s accounts. I am not sure if there is an exception for the left employee. Just wondering whether this is common and I am too nervous?
This would be very weird.
As employee you had ane of more roles. This would be marked with accoringly with one of more roles assigned to your IT profile. Someone who takes over your work would get access to these roles. Not to your account, to the relevant roles
If there is any relevent information for that role I expect it to be stored on a shared drive, a mailbox extract (e.g. in an .pst) or forwarded to whomever needs access to replace you. This has probably been most of the work which you have been doing in the last week(s) of your job.
I would never expect someone to use your account unless it is a function account likle firstname.lastname@example.org. I regular account should be blocked the day after you left. Never extended (ecept for out of office email with an out of office message abnd most certainly never receive a password reset unless you failed to trainfer relevant work files.
Caveeat: I aam assumling a normal (aka good) leave of the job with a proper transfer of knowlege and data to a replacement. Not some weird USA style "you are fired. We walk you to the exit. Sucks if you have any coworkers" kind of situation.
Is it common for employers to keep email accounts open? Yes, it's quite common especially if you are in IT or customer service role where emails are vital. For customers, obviously they want to forward emails to other team members, and for IT, you might get important script or jobs that others might want to fix or change.
As far as using it to log in to something, that's where it is a bit concerning. For one, log into what? An internal test system? Why can't they just create a user for themselves? What makes your user so special that they have to log in with it? A good example might be if you ordered a service using your email and they can't change the login since its tied to an email. For me, in my last job we had a director leave and he had an AWS account that we had to use his email to log in with.
Overall though it doesn't matter. You don't work there anymore. I would only be concerned if it is logging into a financial or HR system and I would email with a follow up asking why your name is used and bring up some obvious concerns with that. Obviously if someone sees Ciao changed someone's HR information after his departure date, that might raise some concerns and it would be hard for you to prove that you didn't especially if the system can be accessed outside their network.