Legacy Knowledge Base
Published Jul. 2, 2025

Creating a Folder for a Specific Team

Written By

Liferay Support

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

With the advent of teams in Liferay Portal, the portal administrator now has greater flexibility in managing site membership. This article outlines a method for creating a set of documents for use by a specific team.

Resolution

Here is a quick demo on how to achieve this from a plain bundle:

  1. Create a Site "Site 1" and within that site, create a team, "Team 1"
  2. Within "Site 1", create a private page and add a Documents and Media Portlet to that page.
  3. Create the folder, "Team Folder" that is to have its contents restricted to a given team.
  4. Enable the permissions such that only team members may view it (disable permissions for Site Members)

teamFolderPermissions.png

Now, when team members upload documents to this folder, they can set them to be "Viewable by Site Member". The permissios on the folder that contains the file will prevent site members who are not a part of the team from seeing the files in the "Team Folder".

Note that for editing the file or its permissions is a separate permission that may be granted by the site administrator.

Did this article resolve your issue ?

Legacy Knowledge Base