Tickets :: [#11595] selective rw access to addressbooks : Edit "my" contact but make all other contacts readonly

6.0.0-alpha10

5/14/25

Search Results: 7 of 27 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

Summary	selective rw access to addressbooks : Edit "my" contact but make all other contacts readonly
Queue	Turba
Queue Version	Git master
Type	Enhancement
State	Feedback
Priority	1. Low
Owners	ralf.lang (at) ralf-lang (dot) de
Requester	ralf.lang (at) ralf-lang (dot) de
Created	10/30/2012 (4579 days ago)
Due
Updated	01/18/2016 (3404 days ago)
Assigned
Resolved
Milestone
Patch	No

01/18/2016 03:55:16 PM	Jan Schneider	Comment #2 State ⇒ Feedback Milestone ⇒	Reply to this comment
This could be simplified a lot by adding an option to only (or always) allow editing the own_contact preference. Of course this also requires the admin to lock that pref and provide a hook for it, but that's just documentation.

10/30/2012 01:59:27 PM	Ralf Lang	Assigned to Ralf Lang

10/30/2012 01:59:11 PM	Ralf Lang	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ 5.1 Queue ⇒ Turba Summary ⇒ selective rw access to addressbooks : Edit "my" contact but make all other contacts readonly Type ⇒ Enhancement State ⇒ New	Reply to this comment
Currently, we use a shared readonly addressbook as an organisation-wide GAL. To allow users to edit their own entry, we provide an RW accessible second addressbook "me" which contains only one entry (by filter). This makes the user experience a little bit confusing but I found no better configuration in existing code. I'd like to either implement a backend option or an ACL/permission to allow filtering which entries a user/group has write access to. Another option would be to make the UI recognize which ACLs are granted to the LDAP bind user but this is probably too much introspection and too slow.