[UserCap BE]: Adding Members

Why are we doing this work

In &4315 (closed), we introduced a User Cap setting for self-managed admins to prevent accidental user overages, now we are doing the same for SaaS group owners.

This work will be broken down into the following backend steps:

• Add user cap setting
• Adding/inviting members 👈 we are here
• Notifications
• Member management
• Auto approval
• Approval Modal
• Group access modifications
• Group sharing
• UserCap availability

This issue is to handle the changes to Members to support the use of a user cap at the Group level.

We'll need to support various states for new Members, so that they can be in a pending state when the user cap has been reached.

Relevant links

• Epic: &5803 (closed)
• Designs: #321934[V4.png]

Implementation plan

• Add a new column to Members for their state
• Add a state machine for Members (User state machine for inspiration)
• Apply correct state on Member creation depending on User Cap for root namespace when being added or invited
• Apply correct state on Member creation depending on User Cap for root namespace when requesting access

Additional notes

Requesting access may not need to be handled separately, but is a use-case we need to be aware of