free busy in Kolab 2.2.2

Gunnar Wrobel wrobel at pardus.de
Thu Jul 16 10:34:49 CEST 2009


Quoting Liutauras Adomaitis <liutauras.adomaitis at gmail.com>:

> Thanks a lot for quick answer, one more thing
>
> 2009/7/15 Gunnar Wrobel <wrobel at pardus.de>:
>> Quoting Liutauras Adomaitis <liutauras.adomaitis at gmail.com>:
>>
>>> Hello Kolab users,
>>>
>>> I have several questions regarding free/busy in KOLAB (2.2.2)
>>> +Outlook+Bynari? I would appreciate if someone would give me any hints
>>> to these questions:
>
> Web admin allows to create resource account, also to manage invitation
> policy, but how to manage ACL rights to resource calendar? There is a
> note next to invitation policy in webadmin saying "For regular
> accounts to use this feature, give the 'calendar' user access to the
> Calendar folder" - but I understand this note is for regular user
> accounts, not for resource accounts, and this has nothing to do with
> user access rights?

Correct. For the resource account this is done automatically. That is  
the main difference between a resource and a standard user account.

>
> I also found this posting
> http://edbsilon.intevation.org/pipermail/kolab-users/2008-February/007423.html
> which says that when user is created, by default no calendar for him
> is added until he log-ins. Does this mean that to arrange a resource
> available for use:
> 1) I have to create resource account

Yes.

> 2) I have to login into it so that calendar would be created (or
> calendar is created by default for resource accounts?)

No. This happens automatically once you send the first invitation to  
this account.

> 3) I have to set (for example) access rights for resource account for
> employee (who will be responsible for that resource account) via
> cyradm?

If an employee should be able to manage and edit events that have are  
present in a resource account then you need to provide the employee  
with access to the calendar folder of the resource. You can do that  
via cyradm but you can usually use any client that supports ACL. You  
could for example use the web client to log into the resource account  
and set the ACLs.

> Do I understand everything correctly:) And can this resource account
> management be done through webadmin, so that I can train users to
> manage resources, access rights etc by themselves?

If an employee should manage a resource you can create the resource  
through the webadmin and you can give the account name and the  
password to the employee so that he may login to that account to  
manage the folder rights. If you want to enable users to create new  
resources they would need to do that in the web admin. You would have  
to provide them with a maintainer or domain-maintainer account though.

Cheers,

Gunnar

>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------





More information about the users mailing list