--- title: Assigned Access configuration kiosk XML reference (Windows 10) description: Learn about the assigned access configuration (kiosk) for XML and XSD for kiosk device configuration in Windows 10. ms.assetid: 14DDDC96-88C7-4181-8415-B371F25726C8 ms.reviewer: manager: dansimp keywords: ["lockdown", "app restrictions", "applocker"] ms.prod: w10 ms.mktglfcycl: manage ms.sitesec: library ms.pagetype: edu, security author: dansimp ms.localizationpriority: medium ms.date: 10/02/2018 ms.author: dansimp ms.topic: article --- # Assigned Access configuration (kiosk) XML reference **Applies to** - Windows 10 ## Full XML sample >[!NOTE] >Updated for Windows 10, version 1903, and Windows 10 Insider Preview (19H2, 20H1 builds). ```xml ]]> ]]> domain\account AzureAD\john@contoso.onmicrosoft.com localaccount ``` ## Kiosk only sample XML ```xml singleappuser ``` ## Auto Launch Sample XML This sample demonstrates that both UWP and Win32 apps can be configured to automatically launch, when assigned access account logs in. One profile can have at most one app configured for auto launch. AutoLaunchArguments are passed to the apps as is and the app needs to handle the arguments explicitly. ```xml ]]> ]]> aauser1 aauser2 ``` ## [Preview] Global Profile Sample XML Global Profile is currently supported in Windows 10 Insider Preview (20H1 builds). Global Profile is designed for scenarios where a user does not have a designated profile, yet IT Admin still wants the user to run in lock down mode, or used as mitigation when a profile cannot be determined for an user. This sample demonstrates that only a global profile is used, no active user configured. Global profile will be applied when every non-admin account logs in ```xml ]]> ``` Below sample shows dedicated profile and global profile mixed usage, aauser would use one profile, everyone else that's non-admin will use another profile. ```xml ]]> ]]> aauser ``` ## [Preview] Folder Access sample xml In Windows 10, version 1809, folder access is locked down so that when common file dialog is opened, IT Admin can specify if the user has access to the Downloads folder, or no access to any folder at all. This restriction has been redesigned for finer granulatity and easier use, and is available in Windows 10 Insider Preview (19H2, 20H1 builds). IT Admin now can specify user access to Downloads folder, Removable drives, or no restrictions at all. Note that Downloads and Removable Drives can be allowed at the same time. ```xml ]]> ]]> ]]> ]]> ]]> ]]> multi1 multi2 multi3 multi4 multi5 multi6 ``` ## XSD for AssignedAccess configuration XML >[!NOTE] >Updated for Windows 10, version 1903 and Windows 10 Insider Preview (19H2, 20H1 builds). Below schema is for AssignedAccess Configuration up to Windows 10 1803 release. ```xml ``` Here is the schema for new features introduced in Windows 10 1809 release ```xml ``` Schema for Windows 10 Insider Preview (19H2, 20H1 builds) ```xml ``` To authorize a compatible configuration XML that includes elements and attributes from Windows 10, version 1809 or newer, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. For example, to configure the auto-launch feature which is added in Windows 10, version 1809, use the following sample. Notice an alias r1809 is given to the 201810 namespace for Windows 10, version 1809, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline. ```xml ```