Why doesn't Authorization Core have the concept of groups, but Authorization Extension does？

Help
,
1
  1. Why doesn’t Authorization Core have the concept of groups, but Authorization Extension does？
  2. On the page Authorization Core vs. Authorization Extension, the Authorization Core and Authorization Extension are compared on the Enhanced performance and scalability feature, but I have a question about what the following sentence means: Limited to 500KB of data (1000 groups, 3000 users, where each user is a member of 3 groups; or 20 groups, 7000 users, where each user is a member of 3 groups)
    Is this saying that a user can only belong to a maximum of three groups?
4

Hi @Ada,

I have reached out internally to get more information on your questions. I’ll update you as soon as I hear back!

Thanks,

Mary Beth

5

Hi @Ada,

I have heard back from the team about your questions. Please see the below:

Regarding this statement Limited to 500KB of data (1000 groups, 3000 users, where each user is a member of 3 groups; or 20 groups, 7000 users, where each user is a member of 3 groups), that example is just to illustrate the limit as a combination of groups’ users and their membership of groups. If you have a higher number of users, you would have fewer groups (assuming it is the same membership per user).

Groups were initially introduced in our authorization extension, which came before the core authorization. When we launched the core authorization, we planned to introduce groups in a future iteration. However, we identified a significant opportunity with the Organizations feature and shifted our focus to prioritize its development. Currently, we are exploring groups within the core auth, but it is not officially on the roadmap. Please submit product feedback so that we can continue to gauge interest in this improvement.

Thanks,

Mary Beth