Settings API - User Provisioning

Seats have been one of the most painful parts of running a portal, and the API never covered the whole lifecycle. You could do part of it programmatically, hit a wall, and finish by hand. This closes that gap: seat availability, assigning seats at user creation, and updating seats for existing users.

The near-term use is obvious once you see it. A new employee starts, and you work with AI on what permissions and seats that person actually needs, and it provisions them. The honest counterweight is that AI gets things wrong, and the failure mode here is people holding seats they do not need with nobody noticing.

The longer arc matters more. As seat management gets this flexible and opens up via API, the case for a separate seat per human starts to erode. An agentic customer platform ends up priced on usage at some point. If you are running a fairly industrial seat model today, this is worth thinking about now rather than when the pricing moves.