Groups inside groups, and managers who keep a team's group current
A company you sell to can now put its groups inside one another, so Engineering is Backend plus Frontend, and name managers who add and remove a group's people without holding a company role.
Added
3- AuthenticationGroups inside groups. A company's group can include up to ten of its other groups, three deep at most, and what the outer group gives, its workspaces with their roles and its company role, reaches the people of every group inside it, while what an inner group gives stays with its own people. A group can sit inside several. A cycle or a chain of four is refused with the groups named, and one change to a company's groups is saved at a time. Including a group in one that gives a company role is for whoever holds Company roles, and in your app asks them to confirm it's them first. The console shows what each group includes, what it is inside and what it gets through it, and Everyone in it lists each person with how they are in the group and through which group. The company API sets includes and reads a group's people.
- AuthenticationGroup managers. Whoever manages a company's groups can name up to ten managers for a group, such as a team lead, who then add and remove the people named in it by hand and nothing else: not its workspaces, role, links or nesting, not themselves and not another manager. A manager holds no company access, and while their group gives a company role, by itself or through a group that includes it, every change of theirs is refused, so managing a group can never be used to climb. In your app, a manager sees Groups you manage on the Single sign-on screen (from @buildbase/sdk 1.0.0), with Add people and Remove. Your team names managers in the console, and the company API names them too. Deprovisioning someone ends their place as a manager at once.
- Webhooksenterprise.group_members_changed whenever the people named in a group change, by a manager, a company admin, your team or a key, with who was added and removed and who acted, and a workflow trigger for it. enterprise.group_updated now says which groups were included or taken out, how many people that reached, and which managers were named or removed. All of it is in the company's trail, where someone joined to a workspace through a group inside a group reads as group Engineering, through Backend.