Summary:

When delegating permissions via Team Settings → Team Types → Permissions → Type-level control, adding a group with more than 50 members fails silently. The API returns TeamTypePermissionEntityTooManyMembers but the UI briefly shows a misleading success toast ("AGP Managed Team controls updated — Permission access for this team type has been updated") before the row is deleted from the settings table.

https://support.atlassian.com/platform-experiences/docs/delegate-permissions-for-team-types/

Current Behavior:

• Groups added to Type-level controls are validated against a hard cap of 50 members.
• If the group exceeds 50 members, the UpdateTeamTypePermissionsMutation returns success: false with error TeamTypePermissionEntityTooManyMembers.
• The UI still shows a success message momentarily, then removes the entry — confusing admins.
• Large enterprise customers using SCIM-synced groups (e.g., 500+ members) cannot delegate team type permissions to those groups.

Expected Behavior:

• Either raise the member cap significantly (e.g., 500–1000+) to support enterprise-scale groups, or implement paginated membership expansion so the limit is no longer necessary.
• If the limit must remain, surface a clear, immediate error message in the UI explaining why the group cannot be added (e.g., "This group has X members, which exceeds the maximum of 50 for type-level delegation").

Customer Impact:

Enterprise customers with IdP-synced (SCIM) groups often have product-access groups with hundreds or thousands of members. These are the natural candidates for delegation since they already represent the correct set of people. The 50-member cap forces customers to create and maintain additional, smaller "delegation-only" groups — adding administrative overhead and drift risk.

Suggested Approach:

1. Short-term: Fix the UX to show an immediate, actionable error when a group exceeds the cap, rather than a false success toast.
2. Long-term: Implement paginated or async membership expansion in Legion so the cap can be raised to enterprise scale (500–1000+ members), or remove it entirely.

Workaround:

Create a dedicated smaller group (≤50 members) specifically for delegation, containing only the users who need team management permissions — rather than reusing large product-access groups. This is suboptimal for large orgs.