Confluence roles permissions feature, unable to create page with user that have create content permi

[Shahriman Mohammad]

Hi,

As part of the new feature confluence roles permission for confluence cloud there is something that we would like to highlight and get some input in regards to scenario when user that have create content permission but no edit content permissions was unable to create page but can create other content type like database, whiteboard, smart link and folder.

 

May us know why this is different for page content type, because base on our understanding, if user have create content permission there can be able to create any type of content but in this case user can only create content type database, whiteboard, smartlink and folder but not page. 

Thank You,

Shahriman

[ashu patel]

Hi @Shahriman Mohammad,

Thanks for raising this—your observation highlights a subtle but important distinction in how the new Confluence roles and permissions model handles content creation.

In the current implementation of Confluence Cloud's updated permissions model, the "Create Content" permission allows users to create various types of content based on the specific combination of page-level permissions and space permissions. However, creating a page still requires both "Create" and "Edit" permissions on pages, because a new page must be editable by the user at the time of creation (e.g., to enter and save initial content).

This differs from content types like databases, whiteboards, folders, and smart links, which are treated differently in terms of permissions—they often fall under separate app or module-based access models that don't always require edit-level page permissions at the time of creation.

So in your scenario:

• The user has "Create content" permission.

• But lacks "Edit content" permission on pages.

• Therefore, they can initiate the creation of non-page content types, but cannot create standard Confluence pages, since page creation implies immediate editing capability.

This behavior aligns with current Confluence Cloud permission logic, although it may not be immediately intuitive.

I’d recommend submitting feedback to Atlassian via this form if you believe the permission behavior could be clarified or improved, especially for consistency across content types.

Let me know if you'd like help drafting a formal feature request or if you need a workaround for this case.

Best regards,
Ashu Patel
Atlassian Community Contributor

[Shahriman Mohammad]

Hi @ashu patel 

Thank you for the response, it's seem align with my early expectation, my concern is this could be miss interpret by user since the permission create content was apply towards all contents type not only specific to any content type base on the permission settings and there is no specific permission for create content for specific content type.

I believe it could be better to make this consistent across all content type, may i know the form link you mention to submit the feedback ?

The reason is we have an existing confluence app that allow user to initiate/create bulk contents types on the legacy permission, we did't have this issue because there are no edit content permissions on legacy permission. We just need to check either user have add permission or not in order to allow user to create various contents types.

May i know what is the reason atlassian introduce the new edit content permission? User can create  content but user can't edit is something weird since create without able to edit are not really align with the definition of create content permission.

I could be wrong but my point of view, the correct meaning of edit content could be -> edit content that belongs to others owner of the content with in the space, because by default if user has create content permission it should also be able to edit their own content, create without able to edit the content is useless in my point of view.

May i know what are the reason that we introduce the new edit content permissions, if some one can explain any scenario that leads towards introduce this new edit permissions is highly appreciate.

@Marie Casabonne  for your information

Thank You,

Shahriman

Senior Software Engineer

Kolekti (Part of Adaptavist Group)

[Shahriman Mohammad]

Hi @ashu patel 

I had raised eco ticket and there is a bugs ticket here have been created by the support team.

Thanks,

Shahriman

Senior Software Engineer

Kolekti (Part of Adaptavist Group)