This page describes the built-in role templates used in Aleph2, and will also serve as a repository for commonly used "custom" roles

The permission string is comprised of the security asset name, an action and the security asset's id or name.

<security_asset>:<action>:<id>

A wildcard character "*" can be used for each one of the parts of the permission string and will allow for all specific values.

Please note that role names are just used as a simple value string.

• DataBucketBean:[read|write|read,write|*]:<_id field>
• DataBucketBean:[read|write|read,write|*]:<full_name - '/' is replaced with ':'>
• SharedLibraryBean:[read|write|read,write|*]:<_id field>
• SharedLibraryBean:[read|write|read,write|*]:<path - '/' is replaced with ':'>

• The principal name is added as a role (eg "social.person._id" for v1).
• The string "admin" is added as a role for admin users (eg currently based on v1 authentication)

• community:[read|write|read,write|*]:<community id>
• source:[read|write|read,write|*]:<source id>

• (as noted under core roles, "social.person._id" is used as the principal when v1 authentication is used)

(None yet)