Skip to lesson
Exit
Organizations, teams and groups1 / 2

1 min lesson

Practice Enterprise Organizations

Practice Enterprise Organizations on one real case. Check the result before moving on.

Step 1 of 2

Work through one real case and finish with this result: teams hold defaults, groups can cross teams, and the most permissive applicable model-access or spend setting wins. Check whether team and group membership are not conflated. Confirm effective permissions are calculated correctly. Make sure org-level settings do not erase team-level governance. Avoid calling Organizations just a renamed team. Keep the evidence with the result. Use teams for business units and groups for cross-team model, spend or agent permissions. When team and group settings overlap, the most permissive applicable model-access or spend setting wins: a stricter team setting does not erase a wider group grant, and a lower group limit does not reduce a wider team setting. Keep org-level identity and usage rollups separate from team-specific governance. Record the effective setting and the source that supplied it.

Learn more

Full explanation

Admin control plane

Enterprise Organizations, resolve effective settings for a cross-team pilot
Admin control plane
SayA large company keeps strict defaults on every team and wants a small 'Pilot Users' cohort, drawn from several teams, to try a new model with a higher spend ceiling. I keep the team defaults strict and widen for the cohort with an Organization Group, not by loosening a team.
DoIn the Organization, open Groups and create a manual 'Pilot Users' group, then add the pilot members from the Engineering, Data and Platform teams.
DoOn the group's Settings, use the Models tab to enable the new model, and set a per-user monthly spend limit higher than the teams carry.
SeeThe Engineering team still blocks that model for everyone else and keeps its lower cap. Only group members get the wider access.
SayNow I resolve the effective settings, because one person can sit in a team and a group at once.
SeeSpend limits take the most permissive applicable limit, so a pilot user gets the group's higher cap even though the team default is stricter. Model access combines the same way: a restrictive team default, widened by the group.
DoCheck a pilot user whose team and group carry different model access or spend settings.
SeeThe most permissive applicable setting wins across the user's team and groups: a wider group grant is not erased by a stricter team default, and a lower group limit does not reduce a wider team setting.
SeeThe proof point is the organization model drawn correctly: teams hold defaults, organization groups overlay members across teams, and overlapping settings resolve most-permissive-wins. Team and group membership were never conflated.