Maybe create a "group" object, that is a team without the icing.
So a group would be the recommended boring object to use for managing group permissions, but teams would have branding etc. and recommended to model real life structures.
Technically, the distinction is pointless, but it might be needed to match the mental model of users.
Maybe create a "group" object, that is a team without the icing.
So a group would be the recommended boring object to use for managing group permissions, but teams would have branding etc. and recommended to model real life structures.
Technically, the distinction is pointless, but it might be needed to match the mental model of users.