%= [dotlrn_header "dotLRN Roles, Sections, and Permissions"] %>
dotLRN Permission API
by Ben Adida.
The dotLRN access control mechanism will rely on OpenACS's permissions
system, but will be completely layered. This means the underlying
permission scheme can change.
General Roles API
These are fairly straight-forward:
- dotlrn::user_add user_id
- dotlrn::user_remove user_id
- dotlrn::guest_add community_id user_id
- dotlrn::guest_remove community_id user_id
Access Control API
- dotlrn::user_can_browse_p ?user_id?
- dotlrn::require_user_browse ?user_id?
- dotlrn::user_can_read_sensitive_data ?user_id?
- dotlrn::require_user_read_sensitive_data ?user_id?
- dotlrn::user_can_read_community_type_p community_type ?user_id?
- dotlrn::require_user_read_community_type community_type
?user_id?
- dotlrn::user_can_read_community_p community_id ?user_id?
- dotlrn::require_user_read_community community_id
?user_id?
- dotlrn::user_community_member_p community_id ?user_id?
- dotlrn::require_user_community_member community_id
?user_id?
- dotlrn::user_can_admin_community_p community_id
?user_id?
- dotlrn::require_user_admin_community community_id ?user_id?
<%= [dotlrn_footer] %>