|
|
|
|
|
1. Introduction
|
|
|
The administration console of the NAITS can be accessed only by the NAITS user who is belonging to the
ADMIN group.
After signing into the system, in the bottom right corner, there is a button which leads to the
administration console.
|
|
|
After the user opens the ADMIN CONSOLE, the following screen appears:
|
| 2. User groups management
|
User groups are firstly listed in the left side menu. This option represents the groups, which are
dedicated to organize and unify usage of the NAITS system for multiple users.
|
|
|
2.1 Preview of existing user groups
First there is a list of pre-defined user groups for the NAITS system. They are:
- Administrators
- Users
- CVIRO
- FVIRO
- LABORANT
- DATA ENTRY CLERK
- HOLDING REGISTRATORS
- ANIMAL REGISTRATORS
- HOLDING ADMINISTRATORS
- AHSM (Area Health Status Management Tool) ADMINS
- QUARANTINE ADMINISTRATORS
- DIM_ADMINISTRATORS
- SLAUGHTERHOUSE ADMINISTRATORS
- RISK ANALYZE ADMINISTRATORS
- PET_VETERINARIANS
|
|
|
2.2 Create a new user group
Each admin user can add a new user group, if needed, via the ADD option placed at the top-right corner
at the grid.
|
|
|
2.3 Filtering existing user groups
The administrator user also is able to filter along the list of user groups via the option FILTER which is
placed at the top-right corner at the grid, next to the ADD option.
|
|
|
2.4 Manage user group permissions
The pre-defined user groups already have pre-installed the appropriate package of permissions via the
Apply permission tool, place at the center above the grid.
After selected a user group on which you want to assign/unassign permission, you should select the
permission package via the dropdown placed centrally above the grid, and then click APPLY permission.
Then the system is giving both option for assign/unassign permission package.
It is not recommended to change the preinstalled permission packages for the group, if you do not
have enough knowledge for the database structure represented in the ER diagram for NAITS.
If you click on some user group, listed in the grid the new screen opens with details about that group.
At the left side menu, firstly you can see the user group detail (same are represented at the grid).
It is not recommended to edit preinstalled user groups.
Also the next button at the left side menu is Member users (list of all users that belongs to that group).
Each user, besides his own inherits the use group permissions.
|
| 3. Users management
|
|
|
|
Users are next in the list placed at the left side menu. This option represents all users installed in the
system, and their details.
|
|
|
3.1 User details
When the admin user, wants to see the user details, he needs to click on some of the users listed in the
grid. After this is done, the new user details screen is shown:
At the left side menu, the following options exist:
- EDIT USER’S PROPERTIES – Preview and edit user info
- MEMBER OF GROUPS – See list of groups that the user is related to
- ORGANIZATION UNIT – See with which organizational units the user is related to
- LABORATORY – See if the user is related with some laboratory
- HOLDING – See if the user is related with some holdings
Above the grid, there exist more features applicable for the user.
|
|
|
3.2 Manage with user permission packages
Similar as for the user groups, the admin user from the user screen can manage directly the user
permission packages via the package selector and assign/unassign of the appropriate package.
|
|
|
3.3 Permission packages description
There are different permission packages, each one appropriate per some of the sub-modules in the
NAITS.
| PERMISSION
PACKAGE NAME
|
OBJECT ACCESS LEVEL
|
| PERSON_REGIST
RATOR_PCK
|
HOLDING_RESPONSIBLE.FULL
|
| HOLDING_REGIS
TRATOR_PCK
|
HOLDING.FULL
|
| ANIMAL_REGIST
RATOR_PCK
|
HOLDING.READ,HOLDING_RESPONSIBLE.READ,ANIMAL.FULL,FLOCK.READ
EAR_TAG_REPLC.FULL
|
| FLOCK_REGISTR
ATOR_PCK
|
HOLDING.READ HOLDING_RESPONSIBLE.READ FLOCK.READ FLOCK.FULL
|
| ANIMAL_MOVE
MENT_REGISTR
ATOR_PCK
|
HOLDING.FULL,HOLDING_RESPONSIBLE.FULL,ANIMAL.FULL,EAR_TAG_REPLC.READ,
MOVEMENT_DOC.FULL,ANIMAL_MOVEMENT.FULL,VACCINATION_EVENT.FULL,VAC
CINATION_BOOK.FULL,VACCINATION_RESULTS.FULL,MOVEMENT_DOC_BLOCK.FULL,
LAB_SAMPLE.READ
|
| FLOCK_MOVEM
ENT_REGISTRAT
OR
|
HOLDING.FULL,HOLDING_RESPONSIBLE.FULL,FLOCK_MOVEMENT.FULL,QUARANTINE
.READ,VACCINATION_BOOK.FULL,VACCINATION_RESULTS.FULL,MOVEMENT_DOC_B
LOCK.FULL,LAB_SAMPLE.READ
|
| SPOT_CHECK_RE
GISTRATOR_PCK
|
SPOT_CHECK.FULL,ANIMAL.READ,FLOCK.READ
|
| FULL_HOLDING_
ADMINISTRATO
R_PCK
|
HOLDING.FULL,HOLDING_RESPONSIBLE.FULL,ANIMAL.FULL,FLOCK.FULL,EAR_TAG_R
EPLC.FULL,MOVEMENT_DOC.FULL,FLOCK_MOVEMENT.FULL,
ANIMAL_MOVEMENT.FULL, QUARANTINE.READ,VACCINATION_EVENT.FULL
VACCINATION_BOOK.FULL,VACCINATION_RESULTS.FULL,MOVEMENT_DOC_BLOCK.F
ULL,SPOT_CHECK.FULL,LAB_SAMPLE.READ
|
| QUARANTINE_
WATCHER_PCK
|
QUARANTINE.READ, EXPORT_CERT.READ, ANIMAL_ORIGIN.READ ,
ANIMAL_ACTIVITY.READ, HOLDING.READ, HOLDING_RESPONSIBLE.READ ,
ANIMAL.READ, FLOCK.READ,MOVEMENT_DOC.READ, FLOCK_MOVEMENT.READ ,
ANIMAL_MOVEMENT.READ, MOVEMENT_DOC_BLOCK.READ
|
| SLAUGHTERHOU
SE_ADMINISTRA
TOR_PCK
|
HOLDING.FULL,HOLDING_RESPONSIBLE.FULL, ANIMAL.FULL,FLOCK.FULL
EAR_TAG_REPLC.FULL,MOVEMENT_DOC.FULL,FLOCK_MOVEMENT.FULL,
ANIMAL_MOVEMENT.FULL, QUARANTINE.READ,VACCINATION_EVENT.FULL,
VACCINATION_BOOK.FULL,VACCINATION_RESULTS.FULL,MOVEMENT_DOC_BLOCK.F
ULL, SPOT_CHECK.FULL, LAB_SAMPLE.READ
|
| QUARANTINE_A
DMINISTRATOR
_PCK
|
QUARANTINE.FULL,EXPORT_CERT.FULL,ANIMAL_ORIGIN.FULL,ANIMAL_ACTIVITY.FU
LL,HOLDING.READ,HOLDING_RESPONSIBLE.READ,ANIMAL.READ,
FLOCK.READ,MOVEMENT_DOC.READ, FLOCK_MOVEMENT.READ
ANIMAL_MOVEMENT.READ, MOVEMENT_DOC_BLOCK.READ
|
| INVENTOPRY_W
ATCHER_PCK
|
INVENTORY_ITEM.READ, TRANSFER.READ, ORDER.READ, SUPPLIER.READ ,
RANGE.READ, ANIMAL.READ
|
| INVENTOPRY_A
DMINISTRATOR
_PCK
|
INVENTORY_ITEM.FULL, TRANSFER.FULL, ORDER.FULL,SUPPLIER.FULL
RANGE.FULL, ANIMAL.FULL
|
| AHSMT_WATCH
ER
|
AREA.READ, AREA_HEALTH.READ
|
| AHSMT_ADMIN
STRATOR_PCK
|
AREA.FULL, AREA_HEALTH.FULL
|
| RYSK_ANALYZE_
ADMINISTRATO
R_PCK
|
HOLDING.READ,ANIMAL.READ,HOLDING_RESPONSIBLE.READ,
SELECTION_RESULT.FULL, POPULATION.FULL, SAMPLE.FULL, CRITERIA.FULL
CRITERIA_TYPE.FULL, STRAT_FILTER.FULL
|
| FVIRO_PCK
|
HOLDING.READ ANIMAL.READ, HOLDING_RESPONSIBLE.READ, LAB_SAMPLE.FULL,
LAB_TEST_RESULT.READ, LABORATORY.READ, VACCINATION_BOOK.FULL ,
VACCINATION_RESULTS.FULL
|
| CVIRO_PCK
|
HOLDING.READ, ANIMAL.READ, HOLDING_RESPONSIBLE.READ,LAB_SAMPLE.FULL,
LAB_TEST_RESULT.FULL,LABORATORY.READ,VACCINATION_BOOK.FULL,
VACCINATION_RESULTS.FULL
|
| LABORANT_PCK
|
LABORATORY.READ,LAB_SAMPLE.FULL,LAB_TEST_RESULT.FULL,VACCINATION_RESU
LTS.FULL
|
|
|
|
3.4 Manage with user <-> user group relation
|
|
|
3.5 Attach a user to user group
Each user, during the first installation is being assigned to his user group. But if there is a need to add
the user in another group or groups, this is how the admin user can do it. First select a user, then choose
a user group from the dropdown with user groups, and then click Add users to selected group.
|
|
|
3.6 Detach a user from user group
Each user can be removed/detached from a user group. The admin user first should select the user,
choose the appropriate group, and then click Remove users from selected group.
|
| FVIRO
|
CVIRO
|
| 1. ANIMAL.READ
2. AREA.FULL
3. AREA_HEALTH.READ
4. CRITERIA_TYPE.FULL
5. DISEASE.FULL
6. HOLDING.READ
7. HOLDING_RESPONSIBLE.READ
8. LABORATORY.READ
9. LAB_SAMPLE.FULL
10. LAB_TEST_RESULT.READ
11. QUARANTINE.READ
12. VACCINATION_BOOK.FULL
13. VACCINATION_RESULTS.FULL
14. VILLAGE.FULL
|
1. ANIMAL.FULL
2. ANIMAL.READ
3. ANIMAL_MOVEMENT.FULL
4. AREA.FULL
5. AREA_HEALTH.READ
6. CRITERIA_TYPE.FULL
7. DISEASE.FULL
8. EAR_TAG_REPLC.FULL
9. FLOCK.FULL
10. FLOCK_MOVEMENT.FULL
11. HOLDING.FULL
12. HOLDING.READ
13. HOLDING_RESPONSIBLE.FULL
14. HOLDING_RESPONSIBLE.READ
15. LABORATORY.READ
16. LAB_SAMPLE.FULL
17. LAB_SAMPLE.READ
18. LAB_TEST_RESULT.FULL
19. MOVEMENT_DOC.FULL
20. MOVEMENT_DOC_BLOCK.FULL
21. QUARANTINE.READ
22. SPOT_CHECK.FULL
23. VACCINATION_BOOK.FULL
24. VACCINATION_EVENT.FULL
25. VACCINATION_RESULTS.FULL
26. VILLAGE.FULL
|
|
3.7 What happens when a user is attached/detached to some user group
After the user has been attached to some user group, he directly inherits its permission. When he will be
detached from the same user group, he will not be able to inherits/posses the user group permissions
any more.
The administrative console management system also is taking care for potential overlaps, since it’s not
limited the object access only per one group. So, if there is a permission per same object with same
access level in two different groups, the user will inherits it as one; but if there is a permission per same
object but with different access level, then the use will inherits both of them, but the one with higher
access level will be superior.
For example if we have an user which is linked to FVIRO and CVIRO user groups. Here we must now that
these use groups have the following permission:
The potential overlap here may reach for LAB_TEST_RESULT object. According this if we suddenly decide
to:
- Detach the user from CVIRO – the user will have only FVIRO and according this the access level
to a object LAB_TEST_RESULT will be inherited from FVIRO - LAB_TEST_RESULT.READ
- Detach the user from FVIRO – the user will have only LAB_TEST_RESULT.FULL, but this will not
affect nothing because the remover permission LAB_TEST_RESULT.READ is with lower access
level than the LAB_TEST_RESULT.FULL
|
|
|
3.8 Assign a user to a organizational unit
Each user can be allowed or not to work with some organizational unit and its items. This is used for:
- distribution the users on different organizational or territorial units,
- working with appropriate holding and other relevant items in that unit,
- manage inventory items via the Device Inventory Management Tool,
- manage area health statuses via the Area Health Status Management Tool
|
|
|
3.9 Reset user password
In case of need, the system is allowing to reset the user password to the default one via the RESET
PASSWORD option.
|
|
|
(3.10) Manage the user status
In order to manage the user status, you first need to select the user on which you want to change the
status, and then according the need you can:
Invalidate user
Validate user
Suspend user
|
|
|
(3.11) Assign a user to a laboratory
Linking the user to laboratory is from essential meaning for the LABORANT group, in order to link which
user from the LABORANT group on which data should have access.
|
| 4. Labels
|
|
|
|
In the Labels section you can search for any label by entering the label code or label text in the search
part placed above the grid. At least one should be entered in order to search the labels. Also you can
choose the locale.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|