====== User Classes ======

Different users of VT can have different permissions which will impact which operations they can perform. 

===== General Classes =====

**User** - general user of VT. Can add and update most data, meeting logs etc. Can run reports, manage meetings and more. Generally cannot delete data from VT. 

**Manager** - can access all areas, but cannot delete critical records.  Will usually be able to effect the same through either enabled or active flags on records.

**Viewer** - readonly user - can see data within VT but cannot make any edits

**External** - mail access user - can submit logs to VT via the secure interface but cannot log in to VT itself. 

**Other fields **

There are a couple of additional fields for each user and they are used within BRP functionality as follows:

  * **Notify** - this user will get automated emails whenever a BRP changes status
  * **Prime EiR** - this user can be assigned as the EiR, or primary (staff) contact for a company. This user will also be included in the list of potential Chairs for BRPs

===== Special Classes =====

**API user** - special user class used for integrations to third party systems only

**Admin** - root access. Not normally enabled for a client. Used by the Parkview VT Team to set up VT for each client and subdomain. 

===== Please note =====

It is highly recommended that most of your team are set to **User** level. This permits almost all common operations within VT to be performed. **Manager** level users can add new users to VT, but they can also delete data from the system. Therefore using **User** level may prevent accidental data loss especially as your team become familiar with VT usage