Summary:

The current 50-scope limit on granular API tokens prevents customers from accessing the full Confluence Cloud REST API surface through a single token. Since Confluence v2 API endpoints exclusively require granular scopes (classic scopes are not accepted), and the full v1+v2 API surface requires approximately 57+ distinct granular scopes, it is impossible to achieve complete API coverage with a single scoped token.

Suggestion:

Allow tokens to carry enough scopes to cover the full Confluence (and ideally cross-product) API surface. A minimum of 100 scopes would address the immediate Confluence gap.

or

Eliminate the 50-scope limit completely.