\documentclass{article}
\usepackage{ulem}
\usepackage{graphicx}
\usepackage{hyperref}
\pagestyle{headings}
\begin{document}
\part{Turba, the Horde Address Book}
Turba can be configured to provide multiple address books from multiple backends. This is done in \texttt{turba/config/sources.php}.

Supported backends are:

\begin{itemize}
\item SQL (i.e. localsql)


\item LDAP (see <a href="https://wiki.horde.org/ExistingLDAPHowTo">ExistingLDAPHowTo</a>, which includes address book configuration information, and <a href="https://wiki.horde.org/NewLDAPHowTo">NewLDAPHowTo</a> for general LDAP setup)


\item Kolab


\item IMSP (docs soon to follow at <a href="http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/[OtherCyrusSoftware](OtherCyrusSoftware)">http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/[OtherCyrusSoftware](OtherCyrusSoftware)</a> )


\end{itemize}
\section{Nomenclature and architecture}
\begin{itemize}
\item Turba can manage any number of different \textbf{sources}, each source can use a different backend driver like LDAP or SQL and utilize a different address book scheme. Administrators can set permissions for each source.


\item SQL sources can be used as a backend for \textbf{shares}. These are address books that each users can create and share with other users and groups.


\item The user can also create (shareable) \textbf{virtual address books}, which are basically saved searches.


\item All those, i.e. non-shared sources, the shares that the user has permissions for, and the user's virtual address books appear as \textbf{address books} in the user's interface.


\item The user can further create \textbf{distribution list} next to regular contacts in any address book that he has write access to. Distribution lists can contain contacts from any available address book, but other users can of course only see those contacts in the list that they also have permissions for.


\end{itemize}
\section{Arbitrary information}
\textbf{<a href="https://wiki.horde.org/Turba">2.1 and later</a>:} For shared address books add the following to the bottom stanza of the source declaration:

<pre><code>
    'use\_shares' => true,
</code></pre>
When using the shared address book functionality, user and group permissions are managed directly by the user who owns the address book using the My Address Books interface in Turba, \textbf{not} by an administrator using the Administration/Permissions panel.  Extended permissions (such as Maximum Number of Contacts) may still be set via the Administration/Permissions panel.

For sources not using the shared address book functionality, all permissions can be structured through the Administration/Permissions panel.

Hit the icon next to All Permissions to add the new top level permissions for Address Book (turba).

Select the key icon next to Address Book (turba) and add permissions for the Sources.

Select the key icon next to Sources and add the address book you want to establish permissions for.

Select the notepad icon to modify the permissions on the address book.  In order for the groups to work you must have the DataTree tied to a valid source (SQL or hooks) or LDAP.

\section{External Links}
Syncing the iPhone addressbook with Horde: <a href="http://edeca.net/wp/2010/01/syncing-the-iphone-addressbook-with-horde/">http://edeca.net/wp/2010/01/syncing-the-iphone-addressbook-with-horde/</a><br />
Modifying fields in the Turba addressbook: <a href="http://edeca.net/wp/2010/01/modifying-fields-in-the-turba-addressbook/">http://edeca.net/wp/2010/01/modifying-fields-in-the-turba-addressbook/</a><br />
Someone's !OpenLDAP/Turba howto: <a href="http://web.archive.org/web/20060708192705/http://ww2.redant.ca/consulting/ldap/turba.php">http://web.archive.org/web/20060708192705/http://ww2.redant.ca/consulting/ldap/turba.php</a>

\end{document}
