# New Confluence V2 Content Permissions REST APIs

**URL:** <https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298>\
**Category:** Confluence Cloud\
**Created:** [October 15, 2026, 8:21pm UTC](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298 "2026-10-15T20:21:19Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![VladymyrPostnov](https://avatars.discourse-cdn.com/v4/letter/v/439d5e/32.png) [@VladymyrPostnov](https://community.developer.atlassian.com/u/VladymyrPostnov)\
**Post date:** [October 31, 2026, 11:24am UTC](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298/21 "2026-10-31T11:24:47Z")

</div>

> Thanks Simon, that corrects what I told andreas1 earlier: adding update without read still goes through, and the 400 only comes when read is removed while update stays. So an app that pushes edit permissions down the tree should be unaffected unless it ever strips read. Good to know about November 3rd for FedRAMP.

---

<div class="post-metadata">

**Author:** ![SimonKliewer](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/simonkliewer/32/42734_2.png) [@SimonKliewer](https://community.developer.atlassian.com/u/SimonKliewer)\
**Post date:** [November 2, 2026, 6:27pm UTC](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298/22 "2026-11-02T18:27:22Z")

</div>

Hey @marc - This is a correct interpretation.

Although one angle to highlight here is that the state is really what makes the permissions “effective”.

In the 2 call example - let’s say the content starts as “OPEN” - the first call to add the “edit” permissions has no “effective” change in access. The second call to move from “OPEN” to “EDIT\_RESTRICTED” is what changes the “effective” access, since now only the users with “edit” permissions can edit the page.

Happy to discuss further though..

And agreed @VladymyrPostnov with your understanding as well!

---

<div class="post-metadata">

**Author:** ![DEW](https://avatars.discourse-cdn.com/v4/letter/d/f9ae1b/32.png) [@DEW](https://community.developer.atlassian.com/u/DEW)\
**Post date:** [November 5, 2026, 8:09am UTC](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298/23 "2026-11-05T08:09:03Z")

</div>

Hi @SimonKliewer ,

Is there a way to use /wiki/rest/api/search endpoint to list all the user’s content to which some specific accountId has acccess to?  
I’m aware of the endpoint /wiki/rest/api/content/{id}/permission/check but this would require to loop through the results which is quite ineffective.

Thank you. For your response.

---

<div class="post-metadata">

**Author:** ![SimonKliewer](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/simonkliewer/32/42734_2.png) [@SimonKliewer](https://community.developer.atlassian.com/u/SimonKliewer)\
**Post date:** [November 5, 2026, 6:14pm UTC](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298/24 "2026-11-05T18:14:40Z")

</div>

Hey @DEW!

The recommended way to list content only a particular user has access to would be to to make the calls as the user.

See [Confluence API requests](https://developer.atlassian.com/platform/forge/apis-reference/fetch-api-product.requestconfluence/) for details on how to do this from Forge functions, and [Calling Atlassian app APIs from a remote](https://developer.atlassian.com/platform/forge/remote/calling-product-apis/) for details on how to do this from a remote backend.

---

<div class="post-metadata">

**Author:** ![DEW](https://avatars.discourse-cdn.com/v4/letter/d/f9ae1b/32.png) [@DEW](https://community.developer.atlassian.com/u/DEW)\
**Post date:** [November 6, 2026, 7:08am UTC](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298/25 "2026-11-06T07:08:13Z")

</div>

@SimonKliewer Thank you for your answer.  
Unfortunatelly, this is not an option to me as the use case we need to cover does not allow this.  
The forge app needs to be in a mode asApp or asUser(admin) and we need to select the objects via accountId.

[Previous page](https://community.developer.atlassian.com/t/new-confluence-v2-content-permissions-rest-apis/103298.md?page=1)
