User management ensures that every user always has the right information at his/her disposal,, thus guaranteeing security and user-friendliness at the same time.
Why can’t everybody have the same?
As soon as several users work with the same software or data, then it’s time to consider user management. Here, we have experienced that two aspects motivate our customers, in particular.
One very obvious motivation is data security. Nobody wants to run the risk of productive data being changed unintentionally (or perhaps even intentionally). Therefore, the users are given the access rights they require. No more, but no less either. Even in strategic planning it may also be necessary to keep data “secret” from others. For instance, when planning location expansion it is a good idea to run through possible scenarios in a small group without the entire staff learning of the impending changes and perhaps getting concerned. Here, too, it is also important to make sure that only those employees for whom the data is meant for, have access to it. Good user management offers the opprotunity to keep these risks as low as possible.
A further motivation is that each user is also provided with the views and data which he/she needs. In this way you can prevent users losing themselves in possibilities and features which hadn’t been created for their field of operation. It is great to have software that can do everything. But it is even better to use software that can do everything but only shows everybody the parts that they need.
The most obvious of these breakdowns is that of departments – why should the marketing department have the same views as production planning or logistics? And it also makes sense within the departments that the internee doesn’t have the same right of access to data as the project manager. Therefore, you can give the internee the rights to scenarios which he/she can experiment with but without being able to change the underlying master data. It may also make sense to give the standard user fewer rights to make changes than to an expert. With good user management you can also enhance the user-friendliness of the software and support the user in his/her work.
How user management works in OPTANO
In OPTANO our focus is on assigning permission based on roles. (the theoretical basis of this can be found under RBAC (Role Based Access Control). Here, first of all, the rights are stipulated which control access to modules, data, scenarios and views are stipulated. If somebody hasn’t been assigned access to the view of the “production plan”, then they cannot see it in the software. To avoid every right being assigned to every user individually, roles are allocated to which these rights are assigned – e.g. roles for the above-mentioned marketing, production planning and logistics departments. Each user is then assigned one or more roles. In this way, new users can also be assigned all the rights which they require easily.
Organizing user management in this way means combining two important requirements: That it is both low-maintenance for standard requirements and absolutely suited to individual requirements.
Just register and off you go!
In order to use OPTANO, each user needs a user name and a password for identification purposes. We have installed several options to remian as flexible as possible:
- User data can be stored directly in OPTANO. Here, a user profile with a name and password is set up in OPTANO which can also be processed by the user.
- Registering with OPTANO is directly linked to the currently active Windows user account. The current Windows user is therefore registered directly. This saves the employees time when registering
- OPTANO is connected to a current LDAPuser database. This appeals to customers who already use LDAP – they can simply use their current user data for OPTANO, too.
User management is truly an asset – it makes your software more secure and more user-friendly. Therefore it is a logical component of OPTANO – so that every user is provided with the right information and features at the right time.
: RBAC was first presented by David F. Ferraiolo und D. Richard Kuhn. The original article from 1992 can still be found at http://csrc.nist.gov/groups/SNS/rbac/documents/ferraiolo-kuhn-92.pdf
: Information on LDAP: https://msdn.microsoft.com/en-us/library/aa367008(v=vs.85).aspx
Autorin: Sabrina Geismann