These are examples of recommended system groups. It?s up to the DBA/client to define
the system groups and the level of permission the system group needs to have.
|
System Group Name |
Sub-system Name |
What permission the group should have? |
|
Wheat Agronomy Admins |
Wheat Agronomy |
The system group should have administrative access to perform ?DEAR? (DELETE, EDIT,
ADD and READ) operation in all the Wheat resources only! |
|
Wheat Agronomy GenotypeAdmins |
Wheat Agronomy |
The system group should have administrative access to perform ?DEAR? operation in
the Genotype table for the Wheat genotypes only! |
|
Wheat Agronomy Breeders |
Wheat Agronomy |
The system group should full (?DEAR? operation) access on ?Wheat Agronomy? sub-system
except they will have read-only permission on Genotype table for the Wheat Genotype. |
|
Wheat Agronomy TrialManagers |
Wheat Agronomy |
The system group should have complete (?EAR? operation) access on ?Wheat Agronomy?
sub-system except they will have read-only permission on Genotype table for the
Wheat Genotype. |
|
Wheat Agronomy Biometricians |
Wheat Agronomy |
The system group should have Guest (ie read-only) access to all the tables but will
have Owner (ie Edit which includes edit/add/read access) to the tables that are
used to store AOV and MET data. |
|
Wheat Agronomy Users |
Wheat Agronomy |
The system group should have Guest (read-only) access to all the Wheat resources. |
Important Note: It is strongly recommended not to use a single system group to grant
permission for all the System Resources of a Sub-system.