Re: UU: Access management

["Alexey Parshin" <alexeyp@gmail.com>]

We already have person_add_to_group() and person_remove_from_group() functions operating with group id.
I can add the versions of these functions taking umo id and group type instead. This would be just a combination of group_find_for_object() and person_{add_to,remove_from}_group().

The umo_register_editor() will not be needed at all if we add functions described above.

Class (as well as UMO) creation isn't limited anyhow at the moment. Currently, anyone can create a class or a UMO. If you can describe such limitations - we can add 'em.

2009/1/6 Ilya A. Volynets-Evenbakh <ilya@total-knowledge.com>

I'm going through available procedures,
trying to figure out proper way to imlement
UMO access management.

Here is what I've gathered so far:

- To add another editor to UMO I have to find ID of EDITORS group
 for given UMO, and then add person to it
- To add another admin, same thing, but for ADMINS group

Class and student administration is similar.


Question:

Why do we still need "umo_register_editor" function?
Are there wrapper functions to perform administrative tasks as one call?
How is access checking in class_create function performed?

-- 
Alexey Parshin,
http://www.sptk.net