anchor.diff:  So if there is a _Acme Corp Issue Tracker Application Token_ credentials type provided by the _Acme Corp Issue Tracker_ plugin, even though the application token is logically equivalent to a password, we should choose the specific credentials type.
   If the plugin doesn't provide a dedicated credentials type, then in that case we would fall back to Username and Password and we would likely have to leverage <<credentials-domains,Credentials Domains>> to try and recreate some of the contextual information that a service specific credentials can provide.
   
  +[NOTE]
  +====
  +The Jenkins Administrator can configure which credentials types are actually permitted to be used in a Jenkins instance using the menu:Jenkins[Manage Jenkins > Configure Credentials] screen
  +====
  +
   ==== Credentials scopes
   
   Each credentials instance in the Credentials API plugin has an associated scope.
  
positive.code: 
  ==== Credentials providers
  
  ==== Credentials stores
  
  === Managing credentials
  
  
negative.code: == User guide
  :experimental:
  
  This document provides guidelines for using the Credentials API.
  
  