|
| Personalised access: definition | |
In principle, your intranet contains confidential data, which are accessible only to authorized persons. Defining personalised access goes beyond that simple barrier: you set for each user (or for each group of users) entries that may be accessed. Practical application: for example, you can create in your intranet a range of pages to which access is limited to people of the Steering Committee of the project, other users will have access to other sections of the Intranet, but not to that ones.
| |
|
| Why it is important to personalise access | |
Without personalized access, your Intranet is a protected set of information, but where each user, when allowed to enter, has access to everything. Result: you are then untitled to publish in your intranet only information that is distributed to all; you are restricted to publish banal information; the important information use other channels. Without access personalized your Intranet loses interest.
| |
|
| Conditions for implementation | |
Two simple conditions are necessary for the implementation of customized access. - for the user: it is necessary to avoid the frustration of viewing all parts of the Intranet where access is denied to him - hide links, hide the menus; keep the principle of a unique identification
- to the administrator: the solution must be simple and reliable, allow the administrator to deal with all cases that may arise, but not force him to set up a complete profile for each user
| |
|
Kheper's features Kheper offers a simple and effective solution for the implementation of customized access, using the concept of user groups. For more information: > Kheper - personalised access | |
|
|
   
|
|