GN4 name groups are configured in EdAdmin4 or in the Administrative Browser.

GN4 groups and domain groups

GN4 groups are independent of domain groups.

About reserved names

Default groups Administrators, Everyone and HR must always exist.

They should not be renamed.

Also, never rename anything in the s_objecttable, as doing so you will break the MD5Key, making the object “invalid”.

About GN4 users and GN4 groups

GN4 users are members of one or more GN4 groups. The order in which users become members of groups is important: joining to the group G1 and then to the group G2 is NOT the same thing as joining first to the group G2 and then G1. Groups that appear before in the list of someone's membership are said to have an higher ‘priority’ than groups appearing after, and so permission or privileges set in the higher-priority groups have precedence over the one set in the lower priority ones. The user itself has the highest priority – so permission and privileges set for the user override any group setting.

There are two predefined group objects called Administrators and Everyone. All the users should belong at least to the Everyone group. Both the Administrator and Guest predefined users belong to it. The Administrators group normally has full access and permission on the whole system; and the predefined user Administrator is the member of it.

Users and groups share certain attributes.

The security, user and group object types are defined in GN4Base.xsd; that must always be included (directly or indirectly) in the GN4 schema. The pre-defined user objects Administrator and Guest and the pre-defined group objects Administrators and Everyone are defined in the GN4Data.xml file that is usually imported into newly created GN4 databases.

It is possible to add more attributes to the user and group object type (e.g. phone numbers etc.) but the existing predefined attributes cannot be touched.

See also

User names