Teams Public API

Team structure is one of those things that is trivial at ten users and genuinely painful at two hundred. Until now, every change meant clicking through the UI one team at a time, which is exactly the kind of work that quietly does not get done.

The practical shape of this: you have a spreadsheet of users and their responsibilities. Hand that to an AI session with full context, let it reason about the structure, then call the API. That is a real reduction in stitched-together manual work, and it holds up when the structure changes six months later.

Permissions are the obvious next step, and you can see the whole picture forming. Build teams, build permission sets, assign permissions, add and remove users, all programmatic.

While you are in here, go look at the user object again. If you have not checked in a while you probably will not recognize it. You can manage associations on users now, and under any user's setup there is a management hierarchy where you set a manager and reports, which means your org chart can live in HubSpot instead of a slide deck. That said, this only starts to matter once you actually have multiple teams and user types. If you are a single-team portal, note that it exists and move on.