Permissions and restrictions in catalogs

It is possible to set permission levels and restriction of access to items from catalogs of training/tracks and subjects/classes available.

The permissions and restrictions are defined by the user administrator or by users who have permission to change the items in the catalog. They can be assigned to specific users, groups of users and the class and subjects. The user platform administrator has all available permissions, including to ignore permissions and/or restrictions in catalogs of subjects and courses, tracks and training and topics and issues.

Permissions

The following are permission levels, from lowest to highest, which can be defined for each item of the catalogs of training/tracks, subjects/classes and topics/issues:

• Reading: when setting that kind of permission, the user or group of users can only visualize the item in the catalog, not being able to take any action over it;
• Execution: when setting that kind of permission, the user or group of users can view and enroll in the catalog item and may run all content. This level of permission is applied only to items in the catalog that allow users to enroll them, i.e., tracks, trainings and classes;
• Writing: when setting that kind of permission, the user or group of users can create new items in the catalog items that allow the creation of child items. This permission applies to folders, subjects and classes not being applied to topics that, even allowing for the creation of child items, do not receive permission or specific restriction, because assumes those defined for the class;
• Editing: when that kind of permission is set, the user or the group of users can modify the item, such as properties, contents and reviews as well as permissions and restrictions, in addition to creating new items if child items are allowed.
• Deleting: when setting that kind of permission, the user or group of users can, in addition to all the other previous actions, delete the item from the catalog;
• Complete: when setting that kind of permission, the user or group of users can perform all the previous actions in the item from the catalog.

Restrictions

The following are permission levels, from the lowest to the highest, which can be defined for each item of the catalogs of training/tracks, subjects/classes and topics/issues: The restrictions follow the reverse path of the permissions, i.e. the user may perform all actions of lower level (earlier) instead of the restriction level, that is if he/she has permissions to previous levels.

Example: if a user has a Complete type permission and a Modification type restriction on a particular item, he/she can perform all actions prior to the modification (of lower level), i.e. can view, execute and write in the item, however, cannot modify it or delete it.

• Reading: when setting this type of restriction, the user or group of users cannot view the item in the catalog;
• Execution: when setting this type of restriction, the user or group of users cannot enroll in the item of the catalog;
• Writing: when setting this type of restriction, the user or group of users can not add new items in items that allow children;
• Editing: when setting this type of restriction, the user or group of users can modify the item from the catalog;
• Deleting: when setting this type of restriction, the user or group of users cannot delete the item of the catalog;
• Complete: when setting this type of restriction, the user or group of users cannot perform any action on the item from the catalog.

It is also possible to use the concept of inheritance of permissions on items from catalogs of training/tracks, subjects/classes and topics/issues. When you set an item should inherit the permissions, all permissions and restrictions applied to its parent item will be applied to it.