[OGo-Users] after editing appt. as ogoadmin, it is marked private in webui, and not possible to reset it

[Adam Tauno Williams]

>> > argh, but when I just recognize the problem, it is ten times faster
>> > for me to login to the ogo webui as ogo admin, and just correct the
>> > appointment.
>> > I'd prefer the way, making the ogo admin user able to change that
>> > field too.
>> > Instead of having to figure out, who else is able to change the
>> > appointment, and bug that person.
>> Its really the decision of the person. If you want to have edit-access
>> to all their appointments, and they agree, they can simply put you in
>> their edit-access-list (scheduler preferences). In fact, as the admin,
>> you can do this in the template user (and the person can choose to
>> change the setting when creating and apt).
>> Real 'delegate' functionality would be better of course (you could
>> configure yourself as the delegate for all others and have all
>> permissions they have).
> yes, would be great to have.

http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=3D99
- and sort of -
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=3D1660

>> Doing stuff as root also destroys 'accountability', since the actor
>> doesn't show up in the logs, but just root.
> what is fully ok on my side, but right, accountability is "away".

Yep.

>> (again, a bit unfortunate legacy that 'root' is tied to the special
>> UID 10000, all accounts should be able to join a 'root' role).
> yes, that is is.
>> > And as the admin can change it in the database also, so I cannot see
>> > the
>> > point to not allow such things via the webinterface.
>> The database/host admin is NOT necessarily the same person as the OGo
>> admin.
> yes, I'm aware of it, then the ogo admin has to contact the db admin, to d=
o
> the job.
> however, right now, I just think the behaviour is  inconsistent, the ogo
> admin is able to edit anything of an appointment, even delete it, but not
> change the access rights.