I don't know if this one is a mountain or a molehill, and hope someone cares to offer an opinion. The 3000 we are on is in a data center in another state. We use SECURITY / 3000, requiring unique session names, and configured so that to change a password, you have to supply the current password. But the operators don't seem scrupulous about signing on to the console under their own session name, or signing off at the end of their shifts. For instance, the current session was signed on Saturday at 11:39 PM; I sincerely hope that operator is not still at work now. Now, so far as I know, they are careful about their own passwords, and don't share. And I'm not sure that I want the operators to have to sign off the console at the end of their shifts, and don't remember if this affect console messages in any meaningful way, but don't think so. If we need this to happen, I would probably choose the configure SEC / 3K to either lockout or disconnect the session after some interval. The only problem that comes to mind is that "just anyone" can walk up to the unattended console, and, since this is a data center, I am not too terribly worried about unauthorized access, or someone 'playing around' on the console. The only benefit would be the ability to figure out which operator's watch something happened on, and that information can be had by other means. Should I be concerned, or is this really not a problem?