Security groups

A security group is a collection of users who can see the same information or features. Instead of making individual changes, you set the security for multiple users at once.

Superior groups and subordinate groups

If you need to create a group, consider which groups are above and below it (superior and subordinate) in the hierarchy.
- A group automatically inherits all the rights of the groups below it.
- By using a hierarchy, you only have to add additional rights to each higher group, rather than having to assign the full security to every level.
The hierarchy of groups doesn't have to reflect your staff structure. For example, your Director is unlikely to need to delete records or manage the database, so they may be added to the Public group (view everything and can't modify), rather than the Supervisor group.

Built-in groups

Vernon CMS comes with three groups already set up.

Your organisation may have changed these groups, so you should view your group security setup before adding users to a group.

Public group

Users in the Public group can see everything in a record (including valuations and locations) but they can't edit, create, or delete records.
They can't access a range of processes including bulk tools, the System Administration menu, and some Object and Person windows.

Cataloguer group

The Cataloguer group is the next level above the Public group.
Users in this group can do everything that users in the Public group can do.
Additionally, they can view everything, create, and edit records.
They can't delete records.
They have more process rights than the Public group and can see all windows and use most bulk tools.
They can't access the System Administration menu.

Supervisor group

The Supervisor group can access all features of Vernon CMS and view, create, edit, and delete records.
You should have at least two users from your organisation in this group.
The built-in users (COLLECT, INDEXING, UPGRADE) are part of this group. Don't remove them.