AllMemberGroupController Limits MemberGroups to 100 results breaking usage where the number of groups is large

GeorgeM · February 17, 2026, 10:09am

On the AllMemberGroupController linked below the endpoint uses take 100 as the default which, when coming from Public Access protection setup, is a major problem for clients with more than 100 groups. Is there a simple way to change the behaviour or is a custom backoffice implementation the only solution?

github.com/umbraco/Umbraco-CMS

src/Umbraco.Cms.Api.Management/Controllers/MemberGroup/AllMemberGroupController.cs

48a431eee

using Asp.Versioning;
using Microsoft.AspNetCore.Http;
using Microsoft.AspNetCore.Mvc;
using Umbraco.Cms.Api.Common.ViewModels.Pagination;
using Umbraco.Cms.Api.Management.ViewModels.MemberGroup;
using Umbraco.Cms.Core.Mapping;
using Umbraco.Cms.Core.Models;
using Umbraco.Cms.Core.Services;

namespace Umbraco.Cms.Api.Management.Controllers.MemberGroup;

[ApiVersion("1.0")]
public class AllMemberGroupController : MemberGroupControllerBase
{
    private readonly IMemberGroupService _memberGroupService;
    private readonly IUmbracoMapper _mapper;

    public AllMemberGroupController(IMemberGroupService memberGroupService, IUmbracoMapper mapper)
    {
        _memberGroupService = memberGroupService;

This file has been truncated. show original

JasonElkin · February 17, 2026, 11:15am

Wow, 100 groups is a lot!

I ran a quick test and the public access picker doesn’t support search or pagination. This is almost certainly an oversight that needs fixing in the picker itself.

I’ve added this as an issue on GitHub:

github.com/umbraco/Umbraco-CMS

Public Access group picker can only pick the first 100 groups

opened 11:14AM - 17 Feb 26 UTC

JasonElkin

type/bug

### Which Umbraco version are you using? 17.1.0 ### Bug summary As [flagged i…n this forum post](https://forum.umbraco.com/t/allmembergroupcontroller-limits-membergroups-to-100-results-breaking-usage-where-the-number-of-groups-is-large/7492), when selecting groups for Public Access only the first 100 groups are available. ### Specifics Unlike the Members picker, there is no search feature. Though arguably groups are better served by pagination anyway, <img width="2090" height="1764" alt="Image" src="https://github.com/user-attachments/assets/4844ead2-3424-46f1-94da-be0820ecd2fe" /> ### Steps to reproduce 1. Add >100 member groups to Umbraco. 2. Go to assign public access to a node based on the group. 3. Only the first 100 groups are shown ### Expected result / actual result All members groups are discoverable, either by search or pagination.

GeorgeM · February 17, 2026, 4:01pm

Many thanks for that Jason!

Yes some clients using our systems have a large number of sub-clients which need to be sectioned into their own pages without being able to use the others due to differing set up, wording and branding on each. While that works even without the public access bit they would be able to manually view these pages sans protection which is a big issue even if it merely lets them interact with their own data in inappropriate contexts. Hopefully the Umbraco guys are able to help out here! As you say the endpoint is fully ready for paging just the Backoffice section that isn’t using it.

Cheers,

George

system · February 17, 2026, 4:01pm

Instead of “guys”, may we suggest, for example: “folks", “Umbracians”, “all”, or “everyone”? We use gender inclusive language in this forum (read more)