The administration of this application should be fairly simple. You can administer:
There is no ability to view and / or maintain calendars or events from within this administrative interface.
To do that you will need to use a CalDAV capable calendaring application such as Evolution, Sunbird, Thunderbird (with the Lightning extension) or Mulberry.
These are the things which may have collections of calendar resources (i.e. calendars).
In the list of users you can click on any user to see the full detail for that person (or group or resource - but from now we'll just call them users).
The primary differences between them are as follows:
These define the structure of the relationships between users.
A manager might want to grant full access to their calendar to an assistant, for example, so there should be an "Is assisted by" relationship between the manager and the assistant.
Relationships themselves are maintained on the User maintenance screen.
It can also be useful to have several people having the same kind of access to a particular set of resources. The "Is a member of group" relationship is used to link users to the group, and then the group is linked to each resource with the "Administers Resource" relationship.
You can also define other relationship types beyond the basic ones just described.
Relationship links work in three ways, as follows:
Suppose you have some resources, R1, R2 and R3 and you want to centralise the booking of the resources through an administrative assistant, A1. When A1 is away you want to have a backup person, so you also want A2 to be able to do that.
In a case like this you should create an intermediate group "G" and set up relationships ("Administers Resource") from "G" to each of the resources to be administered. For each of the people able to administer those resources you should create relationships ("Administers Group") to the group. Other people who may view the resources, but not change them, can be related to the group as "is a member of" which will grant them read only privileges to all of the group's resources.
A1 ==>> Administers Group ==> G A2 ==>> Administers Group ==> G G ==>> Administers Resource ==> R1 G ==>> Administers Resource ==> R2 G ==>> Administers Resource ==> R3 P1 ==>> is a member of ==> G P2 ==>> is a member of ==> G
P1 will be able to see all of the scheduled events for R1, R2 and R3, but will not be able to create, delete or modify them. A1 and A2 will be able to see, create and modify all the events.
In this case you set a relationship from the administrative assistant to the manager of "is Assistant to"
A1 ==>> is Assistant to ==> Manager
(Actually I see there is a bug there in 0.4.0, in that the relationship type is named the wrong way around as "Is Assisted by", so I'll rename that in 0.4.1 :-)
In this case you should create a group "G", which all team members are linked to as "is a member of".
P1 ==>> is a member of ==> G P2 ==>> is a member of ==> G P3 ==>> is a member of ==> G P4 ==>> is a member of ==> G
In this case you should create a group "G", which all team members are linked to as "Administers Group".
P1 ==>> Administers Group ==> G P2 ==>> Administers Group ==> G P3 ==>> Administers Group ==> G P4 ==>> Administers Group ==> G
The DAViCal client setup page on sourceforge has information on how to configure Evolution, Mozilla Calendar (Sunbird & Lightning) and Mulberry to use remotely hosted calendars.
The administrative interface has no facility for viewing or modifying calendar data.
If you can read this then things must be mostly working already.
The DAViCal installation page on sourceforge has some further information on how to install and configure this application.