The real problem here is the difference between
Normally a systems account represents a person's identity. In this case it looks like the OP's company has failed in respecting the non-mentioned software's license clause which is bound to an individual by means of his (domain?) account. But accounts are still computer objects, they can be created and deleted at IT administrator's will
With this answer I would like to highlight that, in my understanding, the company provisioning software for a single licensed account and allowing others to use it, is willingly committing into software piracy. They may have had at least the smart thought to license the software to a fictional account. Technical/service accounts are widely used for any kind of purpose, including illegal/unethical ones. I am not to discuss about the goodness of this practice
Definitely, I see two options here.
One is to discuss with IT the opportunity to switch the license to a service account. This might not be done easily, as it could be impossible under the software's license. Another option, or better trick, is to make your current account (which is a software object) a shared account. Even if it carries your name, your company may establish that the
john.doe identity is a shared identity, and give you a new personal
j.doe account. A different object, but at least one that you can bound to your identity and use private information with. The old
john.doe must be detached from anything personal to you, or better any enterprise resource than the software you are licensed to.
The above fixes the privacy issue but not the piracy issue.
Since you know that multiple people can access your account, you must make constraints, better in written form, to prevent things turn against you. First, you have to establish with senior management and HR that your account can be used by different individuals. Then you must, if you can, purge any data that you can deem sensitive from your account. A lot of employees store personal information such as their Google account in their workstations. While not acceptable in large organizations and theoretically unacceptable in general (as a work computer can't be used for anything rather than work), it is an established practice of the kind "we don't ask, you don't tell".
Then if your account is enabled at accessing work data that is very personal to you, like payroll, and you have real concerns about people trying to abuse them, you have very little options:
- Supervise interactions (you type the password and overwatch coworker until logout)
- Demand audit logs, and regularly check them
- File a written complaint to HR or even escalate to labour authority in your jurisdiction (this one will turn really bad against you)
Eventually, if your employer insists in demanding others to know your system password you won't have a good time dealing with this.
A story about sharing passwords
One of my customers, either from past or current, was a well structured financial institution with severe policies. One day our IT representative helped us remoting into employees workstations on different branches by typing his administrator password and witnessing our work.
It happened that this individual was called by his manager for a meeting that could not be rescheduled, and no IT replacement was available. Rather than letting us go he gave us his password (he could change it priorly) and politely told his manager that he was about to report the event to Security management, just to notify them that a different individual was temporarily and exceptionally approved for administrative access.
That was a strong act of trust to us, which was well repaid with excellent professionalism.