[turba] Turba 2.1.2 - admin rights

Michael Rubinsky mike at theupstairsroom.com
Thu Aug 10 17:45:36 PDT 2006


Quoting tom burkart <turba at aussec.com>:

> I'm not sure that I fully understand the documentation.  From what I  
>  see in the public_to_horde_share.php I am not convinced it will  
> work  for me.

You don't have to use the share system, it's just another option.  You  
should be able to assign permissions on your existing address books  
through the administration->permissions interface. From there you  
assign show, read, edit and delete permissions to your sources by  
user/group etc... You'll first need to create a new permission for  
Address Book (Turba), then create one under that for sources, then  
create one for each source desired...

>
> I have several turba address books that are managed by "adress book   
> admins" (per addressbook 'admin' => array( ... ) ) who are allowed   
> to enter and delete entries, yet the addressbook is visible to all.

This should work fine using the share system if that's what you choose  
to do.  The advantage of using the share system is that it gives end  
users the ability to create address books on the fly and assign/edit  
permissions on them.

You would run the public_to_horde_share script on each sql source you  
currently have as 'public', during the script you assign an owner for  
the address book.  That owner than has the ability to modify  
permissions on that address book from the 'My Address Books' screen.


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org



More information about the turba mailing list