This is necessary so we can use the templates to show tickets assoaciated
with user as well as organization by simply switching the context.

Initial concept for user directory

Now it looks more like the email templates management page.

This will be triggered if the client follows a link from an email And the
help desk administrator has enabled the setting to require a login to create
a  ticket.

Client accounts now that the user is verified either via staff or the
client's email mailbox, there's a much lower risk to showing a verified user
other tickets and virtually no reason that an administrator should have to
turn the feature on.

This is the mode of the system if account registration is disabled

Add client registration methods and login required checkbox

  * Administrator can disable the new activity alert
  * Administrator can disable automatic collaborators from email headers

It was also the last-modified date of the category -- not the actual FAQ
article itself

It was also the last-modified date of the category -- not the actual FAQ
article itself

This is necessary to allow for creative department based access control and
alerts.

This happens when upgrading from 1.6, the company information does not yet
exist (neither do the form tables)

Properly escape company name for display

Background: osTicket allows access to assigned open tickets (both personal
and team assignments) regardless of the assigned department or group. This
is necessary to allow staff to work on tickets in an otherwise restricted
department.

When a staff member closes a ticket, they're credited (ticket.staff_id is
set to staff's id) for the purpose of showing who closed the ticket.
osTicket mistakenly allowed continued access to closed tickets even when the
staff doesn't have access to the ticket based on departmental access.

Join to staff/user tables to get current name when fetching thread entries.