Problem Definition

The Team Type Permission Delegation feature currently imposes a hard limit of 50 members per group or team assigned type-level permissions (Create, Manage, Delete teams).

When an organization admin attempts to delegate Team Type permissions to a group that exceeds 50 members, the configuration appears to save successfully in the UI, but the backend silently rejects the request. The group then disappears from the permissions list without any visible error in the interface, leading to confusion for administrators.

This limit is restrictive for enterprise customers who commonly manage permissions through large organizational groups (for example, 100–500+ members). These customers are forced to either:

• Split their existing groups into multiple sub-groups of 50 or fewer, creating administrative overhead

• Manually add individual users, which does not scale

• Abandon the feature entirely and continue relying on org admins for all team management

Suggested Solution

1. Increase or remove the 50-member group limit — Consider raising the threshold to at least 200–500 members, or implement a scalable membership expansion mechanism (for example, lazy evaluation, caching, or asynchronous resolution) that can handle larger groups without degrading performance.

1. Improve error messaging — If the limit can't be increased immediately, display a clear and actionable error message in the UI when an admin attempts to assign a group that exceeds the member threshold (for example, "This group has X members, which exceeds the maximum of 50. Please use a smaller group or assign individual users."). Currently, the failure is silent, which creates a confusing user experience.

1. Support nested or filtered group assignment — Allow admins to reference a group by role or subset, or support pagination-based group membership resolution so that larger groups can be accommodated.

Why This Is Important

Enterprise customers typically manage permissions at scale through centralized groups (often synced from identity providers such as Azure AD or Okta). These groups commonly exceed 50 members. The current limitation forces customers to create parallel, smaller groups specifically for this feature, which contradicts the principle of centralized identity management and increases admin burden.

The Team Type Permission Delegation feature was specifically designed to reduce overhead for org admins in large organizations. However, the 50-member limit significantly undermines its value for the very customers (large enterprises) who need it most.

Workaround

• Split the large group into multiple sub-groups of 50 or fewer members, and assign each sub-group individually (up to 5 groups/teams maximum per type).

• Alternatively, add individual users directly to the type-level permissions (up to 50 users maximum).

• Neither workaround scales well for organizations with 100+ users who need delegated permissions.

Customer Impact

• Enterprise customer with 50+ members in their management group is unable to use the feature as designed.

• The silent failure (group disappearing after save) creates a poor and confusing admin experience.

• Reference support ticket: CES-173469