Currently, there is no reliable method to programmatically identify platform-managed default groups via the Confluence REST API. This limitation has several confirmed dimensions:

1. No distinguishing field in API responses The /wiki/rest/api/group endpoint retrieves all groups regardless of type, and the response contains no field  to indicate whether a group is a platform-managed default group or a custom group. All groups — default and custom alike — return identical usageType: "USERBASE_GROUP" and managedBy: "ADMINS" values. Refer default groups

2. accessType filter is incomplete and undifferentiated The accessType query parameter (admin, site-admin, user) does not reliably differentiate group types — admin and site-admin return identical results. Additionally, there is no accessType value covering User Access Admin or Guest roles, meaning groups with those elevated role assignments cannot be identified via this parameter at all.

3. Cross-product default groups are missing from Confluence API responses The Confluence group endpoint only returns Confluence-scoped groups. Default groups for other products on the same instance (Jira, JSM, Product Discovery, Assets, etc.) are not included, making it impossible to build a complete cross-product view of default groups from a Confluence-only context.

4. Security implication Because default groups carry elevated global role assignments (Site Admin, App Admin, User Access Admin), the inability to identify them programmatically means developers building group management tooling risk inadvertently including or exposing groups with elevated privileges in operations intended for non-privileged groups.

This gap affects any developer building group management or filtering logic in Forge or Connect apps, particularly those operating in multi-product Atlassian instances.