Projects let you group resources into one entity. A common, shared environment makes it easy to manage your projects. The types of resources you can associate with a project are referred to in AEM as Tiles. Tiles may include project and team information, assets, workflows, and other types of information, as described in detail in Project Tiles.

Caution:

For users in projects to see other users/groups while using Projects functionality like creating projects, creating tasks/workflows, seeing and managing the team, those users need to have read access on /home/users and /home/groups. The easiest way to implement this is to give the projects-users group read access to /home/users and/home/groups.

Project Tiles

With Projects, you associate different types of information with your projects. These are called Tiles. Each of the tiles and what kind of information they contain is described in this section.

You can have the following tiles associated with your project. Each is described in the sections that follow:

Assets and asset collections

Experiences

Links

Project Information

Team

Landing Pages

Emails

Workflows

Launches

Tasks

Assets

In the Assets tile, you can gather all assets that you use for a particular project.

You upload assets directly in the tile. In addition you can create Image Sets, Spin Sets, or Mixed Media Sets if you have the Dynamic Media add-on.

Asset Collections

Similar to assets, you can add asset collections directly to your project. You define collections in Assets.

Add a collection by clicking Add Collection and selecting the appropriate collection from the list.

Experiences

The Experiences tile lets you add a Mobile app, web site, or publication to the project.

The icons indicate which kind of experience is represented: web site, mobile application or a publication. Add experiences by clicking the + sign or clicking Add Experience and selecting the type of experience.

Select the path for the thumbnails and if applicable, change the thumbnail for the experience. Experiences are grouped together in the Experiences tile.

Links

The Links tile lets you associate external links with your project.

You can name the link with an easy-to-recognize name as well as change the thumbnail.

Project Info

The Project Information tile provides general information on the project including a description, project status (inactive or active), a due date, and members. In addition, you can add a project thumbnail, which is displayed on the main Projects page.

Team members can be assigned and deleted from this tile (or have their roles changed) as well as the Team tile.

Translation Job

The Translation Job tile is where you start a translation and also where you see the status of your translations. To set up your translation, see Creating Translation Projects.

Click the ellipsis at the bottom of the Translation Job card to view the assets in the translation workflow. The translation job list also displays entries for asset metadata and tags. These entries indicate that the metadata and tags for the assets are also translated.

Team

In this tile, you can specify the members of the project team. When editing, you can enter the name of the team member and assign the user role.

You can add and delete team members from the team. In addition, you can edit the user role assigned to the team member.

Launches

Tasks

Tasks let you monitor the status of any project-related tasks, including workflows. Tasks are covered in detail at Working with Tasks.

Project Templates

AEM ships with three different templates out of the box:

A simple project - A reference sample for any projects that do not fit into other categories (a catch-all). It includes three basic roles (Owners, Editors, and Observers) and four workflows (Project Approval, Request Launch, Request Landing Page and Request Email).

A translation project - A reference sample for managing translation related activities. It includes three basic roles (Owners, Editors, and Observers). It includes two workflows that are accessed in the Workflows user interface.

Based on the template you select, you have different options available to you particularly around user roles and workflows.

User Roles in a Project

The different user roles are set in a Project template and are used for two primary reasons:

Permissions. The user roles fall into one of the three categories listed: Observer, Editor, Owner. For example, a Photographer or Copywriter will have the same privileges as an Editor. The permissions determine what a user can do to content in a project.

Workflows. The workflows determine who is assigned tasks in a project. The tasks can be associated with a project role. For example, a task can be assigned to Photographers so all team members that have the Photographer role will get the task.

All projects support the following default roles to let you administer security and control permissions:

Role

Description

Permissions

Group Membership

Observer

A user in this role can view project details, including the project status.

Read-only permissions on a project

workflow-users group

Editor

A user in this role can upload and edit the contents of a project.

Read and Write access on a project, associated metadata, and related assets.

Privileges to upload a shot list, photo shoot, and review and approve assets

Write permission on /etc/commerce

Have modify permision on a specific project

workflow-users group

Owner

A user in this role can initiate a project. An owner can create a project, intiate work in a project and also move approved assets to the Production folder. Although all other tasks in the project can also be viewed and performed by the owner.

Write permission on /etc/commerce

DAM-users group (to be able to create a project)

project-administrators group (to be able to move assets)

For creative projects, additional roles - for example, photographers - are also provided. You can use these roles to derive custom roles for a specific project.

Note:

When you create the project and add users to the various roles, groups associated with the project are automatically created to manage associated permissions. For example, a project called Myproject would have three groups Myproject Owners, Myproject Editors, Myproject Observers. However, if the project is deleted, those groups are not automatically deleted. An administrator needs to manually delete the groups in Tools > Security > Groups.