A Group is a collection of Users who can see the same information or features. Instead of making changes for each individual, you set the security for multiple users at once.
Before creating or editing Groups, organise your groups into a hierarchy. Start at the lowest Group and figure out what is the next higher group. A Group automatically inherits all the rights of the Groups below it. So if you allow Public users to view records, the next group up, Cataloguers, can view records automatically. By creating 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 does not need 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 Public (view everything and can't modify) not Supervisor.
Built-in Groups
Your organisation may have changed these Groups so it is always important to view your Groups Security Setup before adding Users to a Group.
•PUBLIC: Users in this Group can see everything in a record (including valuations, locations, etc.) but cannot edit, create, or delete records. They are unable to access a range of Processes including Bulk Tools, the System Administration menu options, and some Object and Person windows.
•CATALOGUER: This Group is the next level above Public. Users in this Group can do everything that Users in the Public Group can do. Additionally, this Group can view everything, create, and edit records. They are unable to delete records. They have more Process rights than Public and can see all windows and use most Bulk Tools. They are unable to access the System Administration menu.
•SUPERVISOR: This Group can access all features of Vernon CMS and view, create, edit, and delete records. You should have at least 2 users from your organisation linked to this Security Group. The Users shipped out by Vernon CMS are also part of this group. Do not remove them.
