You are looking at documentation for an older release. Not what you want? See the current release documentation.
Membership types are possible roles that can be assigned to users in groups.
<field name="membershipTypeURL"><string>ou=memberships,ou=portal,dc=exoplatform,dc=org</string></field>
<field name="membershipTypeLDAPClasses"><string>top,organizationalRole</string></field>
<field name="membershipTypeNameAttr"><string>cn</string></field>
membershipTypeURL: The base dn for membership types storage.
eXo stores membership types in a flat structure under membershipTypeURL.
For example, roles, including manager, user, admin and editor, could be defined by the subtree:
ou=roles,ou=portal,dc=exoplatform,dc=org … cn=manager,ou=roles,ou=portal,dc=exoplatform,dc=org … cn=user,ou=roles,ou=portal,dc=exoplatform,dc=org … cn=admin,ou=roles,ou=portal,dc=exoplatform,dc=org … cn=editor,ou=roles,ou=portal,dc=exoplatform,dc=org …
membershipTypeLDAPClasses: The comma separated list of classes for membership types creation.
When creating a new membership type, an entry will be created with the given objectClass attributes. The classes must define the required attributes: description and cn.
For example, adding membership type validator would produce:
cn=validator,ou=roles,ou=portal,dc=exoplatform,dc=org objectclass: top objectClass: organizationalRole …
membershipTypeNameAttr: Attribute that will be used as the role name.
For example, if membershipTypeNameAttr is 'cn', the role name is 'manager' for the following membership type entry:
cn=manager,ou=roles,ou=portal,dc=exoplatform,dc=org