Permission scope
The boundary around what a person or a system may see and do, set by role, by team and by type of action.
Use this definition in team training or when clarifying a sales note.
Definition
Permission scope answers three questions: who can see which customers, who can act on them, and what kinds of action are allowed. In a company with several teams or offices it usually starts with the team, so a manager on one team does not browse another team’s customers. Inside a team it separates viewing a recording from deleting one, and reading a record from writing to it.
Scope applies to software the same way it applies to people. Anything that can send a message or change a record needs its own boundary, written down, with someone accountable for it.
Why it matters
Recordings and customer records carry real obligations, and the people asking for wider access are usually asking for good reasons. Scope lets you say yes without handing over everything: a sales manager sees their own team, a regional director sees the teams they run, and nobody has to remember an informal rule about what they are supposed to look at.