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

Different users of Meeting Booker can have different permissions which will impact which operations they can perform.  The main difference, though, is that a 'user' will either be someone who is providing meeting slots to offer advice, and someone who is booking those slots to receive advice.

Hence, the principal user classes will be **Advisors** and **Bookers** (Standard Users).   Multiple Advisors may exist on the system who all work for a common company, and can potentially be interchanged.  Advisors are therefore linked to a parent Provider - generally a company.  One or more of the Advisors associated with that Provider may have manager permissions.  This gives extra permissions to assign and switch advisors for meetings etc.

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

**User** - general user of MB - also referred to as a **Booker**. Can view future schedules and book meetings with advisors, subject to certain limitations. 

**Advisor** - The individual a booker will usually book a meeting with. This person will set their own schedule of availability and be notified when slots are booked.  They can also set various parameters to fit in to their standard way of working.

**Manager** - A special class of advisor, nominated by a Provider to have the ability to assign different advisors (including themselves) to a specific meeting.  For example, a legal firm may have several lawyers providing advice, but only upon understanding what topics are to be raised in a meeting, can they decide upon the most appropriate lawyer to attend the meeting.

**Admin** - Power user of MB. Has control over user privileges, can set up schedules for others, and much more.  Will generally be people within the main organisation who have licensed Meeting Booker. 

**Other fields **

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

  * **Trusted To Book** - this user will normally get a confirmation on booking. If this flag is false, they will make a request for a booking which must then be confirmed by the advisor or central team.  This is often set false for new users to the system for an initial period.
  * **Email** - this is critical as the email address will be used by the calendar notification system.  Each user must ensure the email address they specify is one that will update in their daily calendar system.

Note that key functionality is also set by [[Tags]]. You can learn more about the [[booking logic]] too

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

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

===== Add a new user =====

With Meeting Booker, a user will normally add themselves to the system by registering for a new account on the main login page.  Before they will be able to access the system, the site administration team must approve the registration and set them to active status.

At this time, the admin team can also set up various permissions and user access levels for the new user.

However, under certain circumstances, the admin team may also wish to directly add a user to the system:  

Use the menu **Users**, then **+ Create New User** (top right button).