Capabilities (Windows 10)

Declares the access to protected user resources that the package requires.

Element hierarchy

<Package>

    <Capabilities>

Syntax

<Capabilities>

  <!-- Child elements -->
  Capability{0,100},
  uap:Capability{0,100},
  DeviceCapability{0,100},
  mobile:Capability{0,100},
  rescap:Capability{0,100},
  uap:Capability{0,100},
  uap2:Capability{0,100},
  uap3:Capability{0,100},
  uap4:Capability{0,100},
  uap4:CustomCapability{0,100},
  uap7:Capability{0,100},
  uap11:Capability{0,100}
  
</Capabilities>

Key

{}   specific range of occurrences

Attributes and elements

Attributes

None.

Child elements

Parent elements

Remarks

If you don't explicitly declare the capabilities required for your app to access user resources, your app can't access that resource. However, even if you declare a capability, your app still won't have access to the user resource if it doesn't exist on the system or there are other security policies in place that limit access to the resource.

Examples

Here's an example of the Capabilities node.

<Capabilities>
    <Capability Name="internetClient"/>
    <Capability Name="internetClientServer"/>
    <Capability Name="privateNetworkClientServer"/>
    <Capability Name="allJoyn"/>
    <uap:Capability Name="documentsLibrary"/>
    <uap:Capability Name="picturesLibrary"/>
    <uap:Capability Name="videosLibrary"/>
    <uap:Capability Name="musicLibrary"/>
    <uap:Capability Name="enterpriseAuthentication"/>
    <uap:Capability Name="sharedUserCertificates"/>
    <uap:Capability Name="userAccountInformation"/>
    <uap:Capability Name="removableStorage"/>
    <uap:Capability Name="appointments"/>
    <uap:Capability Name="contacts"/>
    <uap:Capability Name="phoneCall"/>
    <uap:Capability Name="blockedChatMessages"/>
    <uap:Capability Name="objects3D"/>
    <mobile:Capability Name="recordedCallsFolder"/>
</Capabilities>

See also

App capability declarations

Requirements