| ===perm_id=== - integer - Numerical ID of the permission, assigned when package is added
|
| ===perm_name=== - varchar - Actual name of the permission
|
| ===perm_desc=== - varchar - Full description
|
| -===level==== - varchar - This is might have been better if it was called "permission type". It specifies appropriate control level needed to use this permission, typical values are "admin", "editors", "basic". This closely corresponds to what group is typically this permission assigned to.
|
| +===level==== - varchar - This is might have been better if it was called "permission type". It specifies appropriate control level needed to use this permission, typical values are "admin", "editors", "basic". This closely corresponds to what group is typically this permission assigned to. |
| ===package=== - varchar - Name of the package which uses this permission
|
| -===maintainer_url=== - varchar - This is used to point to whoever supports use of this permission. Normally this would be "tikipro.org", but for custom permissions the value would be something else
|
| +===maintainer_url=== - varchar - This is used to point to whoever supports use of this permission. Normally this would be "bitweaver.org", but for custom permissions the value would be something else |
|
|
| __users_groups__ (primary key is group_id):
|
|
|
| -This holds information about each group
|
| +This table holds information about each group |
|
|
| ===group_id=== - ingeger - Numeric id of the group
|
| ===user_id=== - integer - This is an id of the user that added the group and can change it
|
| -===is_default=== varchar(1) - not 100% sure but it seems to be a pointer to which group new users are added to. NOTE: If this is so, it has no place in users_group table as you might expect only one group to have this property, the actual default group_id should instead be entered in some general tikipro config table like tiki_defaults.
|
| +===is_default=== varchar(1) - not 100% sure but it seems to be a pointer to which group new users are added to. NOTE: If this is so, it has no place in users_group table as you might expect only one group to have this property, the actual default group_id should instead be entered in some general bitweaver config table like tiki_defaults. |
| ===group_name=== - varchar - This is the actual name of the group as seen by end-users
|
| ===group_desc=== - varchar - Longer description of what kind of users are going to be in the group
|
| ===access_question=== - varchar - Additional question to ask before granting user access as member of this group
|
| ===access_answer=== - varchar - Expected answer to access question (i.e. password). Note that it might be good idea to have this be MD5 hash of actual answer
|
| + |
| +__users_group_permissions___ (primary key is combination of group_id and perm_id) |
| + |
| +This table has information on what kind of permissions does a group member has by default |
| + |
| +===group_id=== - integer - Which user |
| +===perm_id=== - integer - Which permission |
| +===value=== - varchar(1) - Unsure what this is for.... |
|
|
| __tiki_access_permissions__
|
|
|
| -This table has information about each specific access type. Access is a grouping of one or more permissions as it applies to the content.
|
| +This table has information about each specific access type. Access is a grouping of one or more permissions as it applies to the content that certain group can use |
|
|
| ===perm_id=== - integer - what permission is in this access
|
| ===group_id=== - integer -
|
| ===content_id=== - integer -
|
|
|
| -__users_group_permissions___ (primary key is combination of group_id and perm_id)
|
| +!Thoughts regarding "hidden" access. |
| +Its been thought that it would be good idea to have special way to designate some page as hidden so that it does not show up on pages and that should be property of the access_type (is_hidden tag in access table). After thingking about it more, I believe this actually more closely corresponds to permission. In fact the permission should be "tiki_p_searchable_content" and represents that given user/group can in fact do searches for particular object and view it as part of the list of objects of its type. Normally this would be standard permission that is enabled (like tiki_p_view) but it might be disabled for some content or for some groups of users |
|
|
| -This table has information on what kind of permissions does a group has by default
|
| +--- |
|
|
| -===group_id=== - integer - Which user
|
| -===perm_id=== - integer - Which permission
|
| -===value=== - varchar(1) - Unsure what this is for....
|
| +Statements to be supported: |
|
|
| -!Thoughts regarding "hidden" access.
|
| -Its been thought that it would be good idea to have special way to designate some page as hidden so that it does not show up on pages and that should be property of the access_type (is_hidden tag in access table). After thingking about it more, I believe this actually more closely corresponds to permission. In fact the permission should be "tiki_p_searchable" and represents that given user/group can in fact do searches for particular object and view it as part of the list of objects of its type. Normally this would be standard permission that is enabled (like tiki_p_view) but it might be disabled for some content or for some groups of users. |
| +GROUP A has default View access on ALL Tiki Pages |
| +GROUP B has View access on Tiki Page2 but not on Tiki Page 3 |
| +GROUP C has View and Search Access for Tiki Page2 and View only access on Tiki Page3 and password-protected View Access on Tiki Page 4 |