• Portlet Guide
  • Quick tutorial: deploying the portlet test suite
  • Deployment
    • What is a portlet preparation? Why do I need it?
    • Deploying through the administration user interface
    • Deploying directly through the file system
  • Using in a Jahia page
    • Portlet instances
    • Portlet roles and Jahia permissions
  • Hello world portlet
    • Requirements
    • Project structure
    • Maven project descriptor
    • Portlet Java code
    • Portlet descriptor
    • Web application descriptor
    • The Tomcat deployment descriptor
    • Building and deploying
    • Redeployment
    • Troubleshooting deployment
    • Learning more
  • Support for Bridges
  • How to share portlet objects?
    • Public Render Parameters
    • Portlet Events
    • Jahia Shared Map
      • How to share a simple object?
      • How to read a simple object?
      • How to share a bean?
  • Performance
  • Using portlets on other application servers
  • Additional resources

Portlet roles and Jahia permissions

Roles defined in a portlet web application will be mapped upon deployment as Jahia permissions. You can see them appear in the “Manage roles” administration screen. Here is an screenshot example of the permissions related to a portlet:

As you can see there are more than the simple roles defined by a portlet. Jahia has also automatically created permissions for the various portlet modes, as well as a “createInstance” permission for each portlet definition. This last permission allows administrators to specify which roles may create portlet instances and therefore limit the feature to a subset of users. The list of roles mapped as permissions may be seen in the example below: