\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\tableofcontents

HowTo\footnote{http://example.com/index.php?page=HowTo} Permission

In the horde system are 5 types of permissions:

\begin{itemize}
\item{Show }
\item{Read}
\item{Edit}
\item{Delete}
\item{Delegate}
\end{itemize}
\section{Roles:}
\begin{itemize}
\item{Owner}
\item{All Authenticated Users}
\item{Guest Permissions}
\item{Individual Users}
\item{Object Creator}
\item{Groups}
\end{itemize}
\section{Admin section:}
The admin panel "permissions" allow you to set the overall permission for each modul like kronolith, nag, turba, etc\ldots

Effects:

\section{User section:}
User permissons for each modul can be modified through authentificated user by horde for sharing created objects like calendars, tasks, notes etc\ldots

Effects: \newline
  show:\newline
   *no effects\newline
  read:

\section{FAQ:}
\subsection{What is a Object?}
\subsection{How can I set permissions/shares for a single adressbook entry}
\subsection{How to embed Calendar into a webpage }
See the kronolith help file and Using Horde from a custom website or application\footnote{http://example.com/index.php?page=Doc/Dev/LegacyApps} and especially the section entitled "Using the calendar widgets to embed calendars"

\subsection{ I'd like to know what the various permissions mean for the Horde  application.  What do Show, Read, Edit, and Delete mean in the Horde context?}
In the Horde context, the only meaningful permission is READ or the  \newline
lack of it. READ means the user has access, lack of it means they don't.

It goes for any application, not just Horde, except that if for some reason you want to let users know that an application exists, but not let them use it (maybe a premium upgrade?), you can give them SHOW permissions.

\subsection{Apparently I also need to set some of those permissions for Authenticated Users, because the "Horde" link on the sidebar disappears if I only have permissions set for Guests. What about the Edit and Delete permissions? Are those needed for authenticated Users?   }
They are not.

If there are no permissions set on an application, or on Horde itself, the default is to allow authenticated users and disallow guests (unless the app is disabled or set to admin-only in the registry).

If you set any permissions on an application, however, those defaults go away since now there is a permission for the app and it needs to be honored. So when you start adding guest permissions, you need to set appropriate authenticated user permissions as well.

\subsection{Howto give access to a guest for any module:}
\begin{itemize}
\item{Choose Administration --> Permissions}
\item{Click on the All Permissions "keys" icon }
\item{When the "Add a child Permission" pane appears, choose the your module}
\item{Click the Add button}
\item{On the Guest Permissions tab check, Show and Read.}
\item{Checking Edit allows a guest to Edit existing entries.}
\item{Checking Delete allows a guest to Delete entries.}
\item{Go to your module and set the permissionon on user base.}
\end{itemize}
to be continued\ldots

\end{document}
