TeamDesk Knowledge Base & Support

Kirill Bondar  Staff  6/14/2007 10:49:01 AM

The reason for the idea is clear.

It's not clear, however, how TeamDesk should behave if the roles assigned to the user have conflicting settings.

For example the user have been assigned Role A and Role B.

Role A allows access to the object (column, view, record, etc), while Role B does not. Should the object be accessible?

Even worse... What version of the overview page to display to the user? What version of the display/edit form?

Alexander Sepe 6/14/2007 11:44:00 AM

That's right. Definetely it would be complicated.

John Elcik 3/27/2008 12:15:44 PM

Normally I prefer to keep everything simple. However, I really like the way this was recently done in the Open Source Application from Moode. By assigning a role to a user in a certain context, you grant them the permissions contained in that role for the current context and all lower contexts.

The list of contexts in hierarchical order is as follows:

System (no parent)
Site (parent = system) - Moodle 1.8 onwards
Course category (parent = system)
Course (parent = category or system)
Module (parent = course or system/site(1.8 onwards))
Block (parent = course or system/site(1.8 onwards))
User (parent = system)
Inheritance will kick in if a role is assigned at a higher level. For example if a user is assigned a Teacher role in a particular course category then the user will have this role in ALL courses within the category.