...
Code Block | ||||
---|---|---|---|---|
| ||||
<!-- Adminisrative role mapping. This mapping is required if you want to use the administrative features. --> <security-role-ref> <role-name>calendarAdmin</role-name> <role-link>local.2</role-link> </security-role-ref> |
Option 1: Mapping to the existin Liferay portal administrator role for administering the calendar portlet
The simplest solution is probably is to map to the existing Liferay administrator role.
Code Block | ||||
---|---|---|---|---|
| ||||
<!--
Adminisrative role mapping. This mapping is required if you
want to use the administrative features.
-->
<security-role-ref>
<role-name>calendarAdmin</role-name>
<role-link>Administrator</role-link>
</security-role-ref>
|
Option 2: Creating and mapping to a new Liferay role for administering the calendar portlet
Another solution is to create a role explicitly for this privilege of administering the calendar portlet. You'd take this route if the set of users who should be able to administer the calendar portlet is different from the set of users who should have administration capabilities over the entire portal.
This mapping tells the portlet and Liferay that the relevant Liferay role will be called "calendarAdmin":
...