The current Confluence permission model lacks definitive scopes for app access for trashed content. This creates a gap in granular control, where space-admin privileges are inferred rather than explicitly granted. As per API documentation, it requires only read:page:confluence however, it also depends on the user permissions calling the API and user without the admin permission would not be able to get the trashed pages so an admin or write+ permission require to read the trash content in a forge app.

As a developer, we would like to have a dedicated scope like read:space.trash:confluence would enable precise control over trash visibility without unintentionally granting broader permissions tied to other write+ scopes. Additionally, a specific write:space.trash:confluence scope would allow for controlled purging of pages. This would prevent implicit granting of space-admin privileges to Forge app users when only delete:page:confluence is specified, ensuring more secure and deliberate access management.