In the last video, we restricted the Vehicles API to a specific role. In this video, we look at a newer, different kind of control — one that doesn't restrict an API at all. It restricts a user. We create a machine identity access control and see exactly what happens to an integration account once it's named in one. *You'll learn:* - How a machine identity access control differs from a regular role-based access control - Why naming a user in a machine identity access control restricts that account specifically, not the API it's aimed at - How to create a machine identity access control and confirm the restriction takes effect *Chapters:* - 0:00 Intro - 0:45 Concept - 2:43 Demo - 4:16 Testing - 5:28 Outro *GitHub:* https://github.com/jnichols-servicenow/SN2026-Vehicles-API *Links:* - ServiceNow docs – Machine identity access controls – https://www.servicenow.com/docs/r/platform-security/access-control/machine-identity-access-controls.html *Note:* This video covers a new Australia release capability. Behaviour is current as of recording — check the docs for the latest details. *Series navigation:* - Previous: 12 — Web Service ACLs - Next: 14 — Resource ACLs - Full playlist: https://www.youtube.com/playlist?list=PLrhqGp3sUzhvp1sfgP8OZjXRxKOP\_cyBU