title: What use are 'Scopes' in Azure B2C Authentication?
body: <p>I don't understand how the 'Scopes' in Azure B2C are supposed to be used.  They are associated with an API, but not a user. I'm sure I'm missing something, but I see no practical use for something associated with an API. I've used and implemented Claims-based authentication based on a user's role in the database.  </p>
  
  <p>For example: ordinary users of an API <strong>should not</strong> have the authority to delete an object, but administrators <strong>should</strong> have the authority.  Does someone have a practical example of how these B2C 'Scopes' can be used to limit a users access to the API?</p>