Project Roles and Permissions
Release Feature (LPD-58677) Liferay DXP 2026.Q3+
The Content Marketing Platform (CMP) defines three project roles: Project Manager, Project Contributor, and Project Member. You hold roles on each project separately, so your permissions can differ from one project to the next. A fourth role, CMS Administrator, is a Regular Role and covers every project in every space.
Activate the Content Marketing Platform using the release feature flag and a CMP license. See Activating CMP.
Roles
Each role covers a distinct level of involvement in a project, from running it to reviewing it. Every member holds Project Member, which is applied on being added and can’t be removed, and can also hold Project Contributor or Project Manager. Role permissions are additive, so holding more than one doesn’t limit the others.
CMS Administrator: A Regular Role rather than a project role, so it covers every project in every space instead of one project at a time. It grants every permission on every CMP item, and it’s the only role that can create a project. To start a project, ask a CMS Administrator to create it and assign you as its Project Manager.
Project Manager: Grants every permission on a project and its tasks, including managing membership and deleting other users’ comments.
Project Contributor: Grants the permissions needed to carry out a project’s work. On tasks, it grants permission to create, edit, view, comment, and view task history. On the project itself, it grants permission to comment and view. It also grants permission to link and unlink assets.
Project Member: Grants permission to comment, view, and view task history. It grants nothing else. A Project Member assigned a task can still edit that task, as Task Ownership and Assignment explains.
Two other conditions grant permissions outside these roles. You’re the owner of any item you create, and an owner holds every permission on that item. In the members list, the person who created the project is labeled (Owner): their roles can’t be changed, and they can’t be removed. Naming a user as a project’s Manager or Sponsor also grants access, as Projects describes.
Permissions Matrix
This matrix maps each capability in a CMP project to the roles that grant it.
| Capability | CMS Administrator | Project Manager | Project Contributor | Project Member |
|---|---|---|---|---|
| Create a project | ✔ | |||
| View a project and its tasks | ✔ | ✔ | ✔ | ✔ |
| Edit project details | ✔ | ✔ | ||
| Delete a project | ✔ | ✔ | ||
| Create a task | ✔ | ✔ | ✔ | |
| Edit any task | ✔ | ✔ | ✔ | |
| Edit a task assigned to you | ✔ | ✔ | ✔ | ✔ |
| Delete a task | ✔ | ✔ | Tasks you created | |
| Link or unlink assets | ✔ | ✔ | ✔ | |
| Add or remove members and change roles | ✔ | ✔ | ||
| Post, reply to, and rate comments | ✔ | ✔ | ✔ | ✔ |
| Edit or delete your own comment | ✔ | ✔ | ✔ | ✔ |
| Delete another user’s comment | ✔ | ✔ | ||
| View task history | ✔ | ✔ | ✔ | ✔ |
| Watch a project or task | ✔ | ✔ |
Editing another user’s comment isn’t a permission any role grants, including CMS Administrator. Task Ownership and Assignment explains how creating a task or being assigned one changes what you can do with it.
Task Ownership and Assignment
Deleting a task and editing a task each depend on your relationship to the task, not only on your roles. Creating a task makes you its owner, and being assigned one grants permissions on that task alone.
Deleting a task you created: The Project Contributor role grants no delete permission on tasks. You can delete a task you created because you’re its owner, and an owner holds every permission on the item. You can’t delete a task another user created.
Editing a task assigned to you: If a task is assigned to you, you can edit it regardless of your other roles. A member whose only role is Project Member can edit a task assigned to them, even though that role grants no general edit permission.
What You See Without a Permission
CMP handles missing permissions in one of two ways, depending on the control. An item’s Actions menu lists only the actions your roles grant, so you never click an action that fails. Fields in the project and task details views remain visible but read-only, so you can view a task’s state, assignee, tags, and description without modifying them.
The same rules apply outside the interface. CMP refuses an action your role doesn’t grant, even when a script or an API call attempts it.
You see only the projects you belong to, and you can’t open a project you don’t belong to.
For steps on adding members and assigning them roles, see Projects.