We
are working with User Profile Administration, and we are looking at when and
how we can make a User inactive. |
One
of the situations where we would want to make the User inactive is when a
User leaves the employ of the Company and one of the Options that we can use
is actually to Remove the User from the System. |
|
We do of course have a
separate tutorial about the procedures for Removing a User from the System. We are just pointing out
here, that it would be one of the Options that we could use. There are also other
ways of doing it. |
|
|
|
|
|
Now bearing in mind of
course, that if we Remove a User completely from the System, then the
original User Code that we are removing, can be embedded in a lot of
historical Data in the System. So when we look at the
historical Data, if that User has been removed, then we will only see the
User Code that was used before and no longer the name. So therefore it is
sometimes actually better not to Remove the User entirely from the System,
but simply to make the User completely inactive, so that the User Logon is no
longer used. But for historical
purposes the Record of this prior User Code is still present in the
System. |
|
So what we do in this
case is for this User Master, we simply choose “Suspended From Logon”, and we
also choose “Profile Only, Not a Real User”. In other words,
previously this User was a real User and used to Logon, but now we are no
longer going to allow this User to Log On. Now if we only choose
“Suspended from Logon”, and we do not check “Profile Only”, then if we ever
use the Option to “Suspend All Users”, then this User Code is marked as a
“Profile Only” and also “Suspended”. Then if we use a “Global
Unsuspend”, then this User will not be “Unsuspended” because Profile Only
Users are not Unsuspended by the Unsuspend Action. Another reason that we
could have for temporarily Suspending the User, in which case we will only
choose “Suspended From Logon”, and not check the “Profile Only”, is when we
temporarily want to Suspend a User, but we still do expect this User to use
the System again in some point in time. |
There is another
optional measure that we can apply, i.e. we can simply also give a new
Password to this User Code, so that the original User Code that this User
used will no longer work. Therefore whenever
anybody wants to use this User Code, they will not be able to because there
is a new and unknown Password on this particular User Code. So that is an extra
measure that we can take in addition, if we want to. |