User details of ex-Plusnet employees

[#1]

When someone who regularly posts on these forums leaves I see that their Plusnet credentials are removed from their profile. This leaves a large number of posts which were official statements on behalf of the company which now don't look as if they were made by a Plusnet employee - and given the elevated position of the last person to leave that isn't good.
Surely the best think to do would be to lock the account leaving it's status (perhaps modifying the signature to say when they left the company), and if they are still using Plusnet as a user give them a new user name to participate in the forums from then on.

[#2]

Let me have a think about that Jelv, the issue with creating a new username is that the account in our CRM only has 1 community username tied to it, so it won't actually allow another to be created.

[#3]

Should PN employee user names be tied to an account? if you can't do that could you create a dial-up account (which would never be used) and switch the ex-employee's username to that account?

[#4]

Could we just identify them as ex-staff members by setting up a new group?

[#5]

It's an idea and better than what we have currently; but that wouldn't readily identify the posts they made in their official capacity and any comments they'd posted since leaving.

[#6]

I don't really think there is a workaround for that without their signing up for a second account (which they can't do).

[#7]

Why not, reply #2 and don't some 2nd accounts exist already?

[#8]

Quote from: Anotherone

and don't some 2nd accounts exist already?

Yes!

[#9]

Only if they have 2 separate Plusnet accounts.

[#10]

So why can't you do this?

Quote from: jelv

could you create a dial-up account (which would never be used) and switch the ex-employee's username to that account?

That would then allow them to sign up again with a new forum user name for their personal use.

[#11]

Because it's not possible without database access to move the community site component between accounts. I'm looking at how we do this, although I don't really see it as a huge problem.