Permission scope answers a practical question: what exactly can this agent read, edit, delete, or send? Scope is the useful middle between full access and none: read a Slack channel without private messages, draft an email without sending it, read a folder without deleting files. When you authorize a connector, the verbs matter: read differs from write, write from delete, draft from send. Every host grants its own specific scope, so check it every time.
Office keys are the everyday version. One opens the lobby, another the file room, another the room where the checks are stored. A new employee may need the lobby key on day one; they probably don’t need every key in the building.
Why you care
Good scope makes the work easy to reason about. If an agent can only read one client’s folder, you never wonder whether it pulled the wrong client’s files. If it can draft but not send, you review before anything reaches another person. Scope and identity travel together, so see OAuth and agent identity too. The best scope is boring: the agent does exactly what the work requires, and nothing more.