Administering phpGroupware: The Admin Module

dcp's picture

We previously installed phpGroupware, and now we need to configure it so our users can do their work. This will be more of an overview to help you get up and running, than an in-depth tutorial.

The first thing is to understand the difference between the Administration tool, and Preferences. Preferences affect the user experience more directly, while Administration settings determine who can do what. While you can set default preferences for all applications in phpGroupware, the users can change these, unless you choose to force certain settings. So let's first head over to the Administration area and change some initial settings. BTW, I'll understand if you run over to Preferences and change the default theme first. But hurry back!

In the Administration area, you will find the Admin section with a fairly long list of settings to play with. Check out the Site Configuration module first. You'll find 3 sections - Site Configuration, Appearance and Security. Most of the settings are fairly easy to understand, and you can probably accept the defaults for most. However, there is no information on whether and when to cache the phpgw info array. Also, I haven't figured out yet how to tell the system to grab a logo image from outside of the default directory: /phpgwapi/templates/default/images/.

The Peer Servers module apparently lets you connect to other phpGroupware servers. You will need the link to the other server(s), along with the admin user login and password to make the connection. You can control which way the relationship between servers flows. Thus, if you have a server that other servers connect to for information, you can set the relationship on it to "outbound", so that it does not accept inbound information from other servers. Or you can setup a 2-way relationship. More options are available, should you need that, so be sure to check into them.

I have no idea what the Adddress Masters setting is all about, but apparently, you must have at least one. Until I get a response from the phpGroupware crew, I can only assume that this is probably a sort of template used for the address book. Alternatively, these are special users with superpowers where the address book is concerned. I also don't know what the Sync-Account Contact link is - it doesn't seem to do anything.

The user and group account settings modules should be fairly obvious. I suggest creating groups and assigning appropriate permissions to each, and then create users to put in the groups. Some of the permissions settings have an ACL box next to them. Go ahead and set the ACL permissions as well. If you don't give users appropriate permissions to access an application, they won't be able to use it.

Next comes the applications settings. You can delete applications, hide them from the Navigation Bar, or change their location on it. Having set the appropriate permissions is fine in most cases, but you may not need to use SOAP, if you are a management consulting firm. In any case, hiding them from the navbar is sufficient in most cases to clear the clutter for users.

In Global Categories, you will want to establish the top-level categories, such as "Work" and "Personal", along with other major categories (accounting, sales, etc.). It's a good idea to establish these, so you can let your users create their own sub-categories. You may need global sub-categories, but otherwise, save yourself a bit of time and trouble.

Finally, you can change the Main message (welcome message) the users see in the Home page after logging in. You can make it a slogan, a special welcome message, or tell your workforce they're all fired. If you go with that last option, I'd recommend changing the permissions on any apps containing critical data first.

The rest of the Admin configuration section is geared toward letting you view logs and the PHP information for your site. You should click the Find and Register all Application Hooks. It doesn't appear to do anything, but is probably just a script to run. Finally, Asynchronous timed services let's you setup Cron jobs, such as calendar alarms.

Keep following along. I'll be posting updates to this article with answers to the issues I wasn't able to explain. Next, time, we'll work on Administering some of the applications.


Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Answers to PHPGW Questions

I got answers to my initial questions. Thanks to Chris Weiss, of the phpGroupware project:

How do you change the site logo without going down into the default theme images folder? Or is it possible? The logo settings in Site Configuration only allow you to change the name of the file, not its location - at least in my installation.
Due to the dynamic nature of the template system the new logo has to fall into one of the template folders. if you are making your own custom template, the new logo can go in your template folder. We have the option to change the name and use standard templates because a "cvs update" will ignore extra files that you've added and thus an update won't be destructive to the logo change.

There is a setting to allow one to cache the phpgw info array. What does that do and when should(n't) I use that option?
This adds all the config items that are stored in the database to be cached in the session object. Enabling this can reduce the load on the database server and in many cases will speed up a site. You don't want to enable it until your site is fully configured as change detection is non-existent since the site config rarely changes in a
production system.

What are these users and what is their purpose? Are these simply template users for the contacts application? Why would or wouldn't I setup a given user as an Address Master?
When you enable the contacts-account sync, the address master is the "owner" of the contacts that represent the account. It's like this for legacy reasons, accounts and contacts used to be completely separate in every way and contacts had to be "owned" by an account.

You need an address master if you want your phpgw accounts to be accessible in the Address book. The address master can manage the data in the accounts (think Exchange admin or Active Directory admin who can manage users metadata but the users can't).

D.C. Parris
Publisher, Blue Gnu
http://www.linkedin.com/in/dcparris
https://www.xing.com/profile/Don_Parris